-
Notifications
You must be signed in to change notification settings - Fork 1
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
Order of the scripts to run #5
Comments
Hi @rohitfarmer, thank you for the interest. Does #3 by chance meet your needs? |
It looks like it would be helpful. Have you merged the pull request? |
Not yet, I would like to evaluate it locally first and unfortunately cannot until Friday due to responsibilities at a conference. Is there any chance you could pull it down and try it out?On Mar 12, 2024, at 10:09, Rohit Farmer ***@***.***> wrote:
It looks like it would be helpful. Have you merged the pull request?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Okay, I will give it a try. |
Thank you!On Mar 13, 2024, at 05:57, Rohit Farmer ***@***.***> wrote:
Okay, I will give it a try.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there. Thank you for developing this pipeline. I am interested in implementing it at the VRC/NIH. Our HPC currently does not support SLURM, but would you like to list the order of the scripts, the input, and the output? The IT folks or I can convert the submission scripts for our setup.
The text was updated successfully, but these errors were encountered: