Add entries for ebi-gxa anndata_ops and scanpy #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@pavanvidem ping |
|
I don't have much experience with ebi-gxa tool suite except that I used some from training materials. Maybe @pcm32 has a better understanding. |
|
Input size is on which units? |
|
GB |
|
I suspect then that the multipliers might be too big and very quickly leave you with no choice of node to run. I had some memory usage stats that I left as supplementary material in a paper, let me try to dig that. In our pipeline, for AnnDatas of around 5 GB you rarely need more than 20 GBs of ram. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add scaling rules for some ebi-gxa tools.
Add a general fallback for ebi-gxa/scanpy* as well as specific ones for anndata_ops, scanpy_multiplet_scrublet, scanpy_scale_data and scanpy_run_pca.