Skip to content
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

Describe global and per-rule requirements #70

Open
tbooth opened this issue Aug 29, 2024 · 1 comment
Open

Describe global and per-rule requirements #70

tbooth opened this issue Aug 29, 2024 · 1 comment
Labels
reviewer Issues arising from comments on https://github.com/carpentries-lab/reviews/issues/17

Comments

@tbooth
Copy link
Collaborator

tbooth commented Aug 29, 2024

Suggestion from @cmeesters to add to Chapter 9:

describe the difference between global and per-rule requirements.
A global requirement might be snakemake, the executor plugin, the file system plugin
(as a remedy to I/O contention and perhaps some remote file plugin for data management).

@tbooth tbooth added the reviewer Issues arising from comments on https://github.com/carpentries-lab/reviews/issues/17 label Aug 29, 2024
@tbooth
Copy link
Collaborator Author

tbooth commented Aug 29, 2024

I'm not convinced this topic fits into Episode 9 which is concerned with the basics of workflow performance. The text in the episode does try to make it clear that this here is just an introduction, and we have a very brief mention of the topic of cluster execution but there's no way we can actually cover this in any depth within the course.

I think if we were to cover requirements (and the resources: fields) this would warrant a separate topic, and would have to be done in conjunction with really getting into the details of cluster (and cloud?) execution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reviewer Issues arising from comments on https://github.com/carpentries-lab/reviews/issues/17
Projects
None yet
Development

No branches or pull requests

1 participant