-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process_high->64GB ram/process_high_memory->128GB #91
Merged
johandahlberg
merged 2 commits into
nf-core:dev
from
PixelgenTechnologies:feature/change-process-high-to-use-64gb-ram
May 28, 2024
Merged
process_high->64GB ram/process_high_memory->128GB #91
johandahlberg
merged 2 commits into
nf-core:dev
from
PixelgenTechnologies:feature/change-process-high-to-use-64gb-ram
May 28, 2024
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
|
johandahlberg
force-pushed
the
feature/change-process-high-to-use-64gb-ram
branch
from
May 27, 2024 14:59
433a867
to
c41065b
Compare
fbdtemme
reviewed
May 27, 2024
CHANGELOG.md
Outdated
@@ -10,6 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
- [[PR #90](https://github.com/nf-core/pixelator/pull/90)] - Update pixelator to 0.17.1 | |||
- [[PR #90](https://github.com/nf-core/pixelator/pull/90)] - Add `pixelator single-cell layout` command | |||
- [[PR #90](https://github.com/nf-core/pixelator/pull/90)] - The `graph` and `annotate` steps are now using `process_high` as their resource tags | |||
- [[PR #91](https://github.com/nf-core/pixelator/pull/91)] - Set `process_medium` to use 64GB of RAM and `process_high_memory` to use 128GB of RAM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be process_high
right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. 🤦
johandahlberg
force-pushed
the
feature/change-process-high-to-use-64gb-ram
branch
from
May 27, 2024 15:26
da7c814
to
71b413c
Compare
fbdtemme
approved these changes
May 27, 2024
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.
Adjust the resource requirement so that
process_high
used 64GB of RAM andprocess_high_memory
used 128GB of RAM.PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).