-
-
Notifications
You must be signed in to change notification settings - Fork 67
Software Requirements Lesson #28
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
Conversation
|
||
Depending on your CWL runner, these hints may be used to check | ||
that required software is installed and available before the job is run (note | ||
that currently the reference implementation does not do this). |
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.
It does if you turn on the beta dependency-resolvers-configuration
tool as a `SoftwareRequirement`, search for the tool on SciCrunch and use the | ||
RRID that it has been assigned in the registry. You can use this RRID to refer | ||
to the tool (via [identifiers.org][identifiers]) in the `specs` field of your | ||
requirement description. |
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.
Other good choices in order of preference: DOI for the main tool citation, URL to the tool
We should also mention how to add a software tool to scicrunch: https://scicrunch.org/page/tutorials/336
ready |
Waiting for #27 because I reference
custom-types.cwl
as the example.A first draft of a lesson on
SoftwareRequirement
. Similarly to #27, this may have holes/things that need correcting, so input is very welcome.