-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Feature request]: Batch CLI Action #440
Comments
Relevant PR that contains infrastructure for implementing this issue: #394. Merging PR will be a blocker for starting this issue. |
Per zoom discussion: may want to pivot the user-facing bit of #394 in this direction. Currently, that PR proposed interface is roughly: $ flepimop submit -c config.yml ... to create + submit an emcee job. When this issue is ultimately resolved, we'll want to stop supporting that syntax, and instead have users write: $ flepimop batch calibrate ... If its minimally invasive in #394 to use the expected future syntax now, let's jump to that so people have less future revision to do. We should be able to leave everything basically as-is on @saraloo / @jcblemai as principle beneficiaries of #394 does that make sense? we're basically looking to tweak that PR slightly, so that the interface matches where we expect to go, but not implement any of the clever / complex / generalized capabilities entailed here. pending user input, @TimothyWillard your call re tweaks to #394, as you best understand if "minimally invasive" is achievable. |
|
acknowledged - agree that we can't be perfect here, but we can tweak a bit to avoid some future edits. Deprecating / adjusting arguments seems easier than deprecating commands, imo. |
Label
batch, enhancement
Priority Label
medium priority
Is your feature request related to a problem? Please describe.
Submitting jobs related to flepiMoP to HPC environments is challenging. Currently inference jobs can be submitted via:
Submitting any other kind of job is either manual or not possible.
Is your feature request related to a new application, scenario round, pathogen? Please describe.
No response
Describe the solution you'd like
A CLI tool that can be used like so:
where
...
correspond to further arguments passed to the given CLI action.The text was updated successfully, but these errors were encountered: