-
Notifications
You must be signed in to change notification settings - Fork 4
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
Singularity compatibility update #2079
Draft
ckirkman-IDM
wants to merge
1
commit into
dev
Choose a base branch
from
singularity-compatibility
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
@ckirkman-IDM , here are some comments for your reference:
-B $(pwd) is not necessary as it was done by default in Singularity
--pwd $(pwd) is not necessary as script ran under $pwd already and Singularity takes current working directory already by default
for -B $(pwd)/../Assets
SlurmPlatform support all kind of tasks (not just EMODTask), in certain case there may not have Assets folder (remark: we may have with current code due to code defect). You may consider the following instead
This PR only solves NYU's one special case, like Sharon pointed out the NU case, it doesn't solve the general binding cases. Instead of fixing a special case with PR, you may use the same work around like Sharon's case:
or simply
Default: idmtool has experiment folder binded in _run.sh file
Then we separate binding from sif_path in workaround above.
Approach 1:
Since we alrady did
we may add one more variable for binding, like
Notes
singularity exec may have many other optional parameter in addition to --bind. If needed, other options can be built/constructed into
For example,
(a) with default experiment folder binded, it solves Clark's case automatically
(b) for Sharon't case, we can do
Approach 2:
Instead of doing (adding variables to task)
we can instroduce two input parameters in suite.run(...) and experiment.run(...),
Let's take suite as an example, same for experiment:
if user needs more extra path binding, we can do
Notes
singularity exec may have many other optional parameter in addition to --bind. If needed, other options can be built/constructed into
For example,
(a) with default experiment folder binded, it solves Clark's case automatically
(b) for Sharon't case, we can do
Remark: with appraoch #2, we need to consider code back compatibility.
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.
Thanks for the reply, working on digesting it all :)