Another branching out expand_hcw and revert to a previous commit #1605
Conversation
…does not change the extra budget fracs
…ue to another 5 runs of no expansion
…scenario run script
|
Hi @tamuri @matt-graham, I have to create this temporary branch to submit some jobs, which is branched out from another branch that did not merge in latest master. These jobs have to be submitted in the branch/time (i.e. expand_hcw on 6 Dec 2024) when my other jobs were submitted, for results consistency. Would the conflict below affect me submitting jobs? If it would, how shall I fix it so that this branch keeps intact? Many thanks! |
|
You can still run analysis in this branch (assuming everything else is in order) - but you can't merge it into master without resolving this conflict. |
Thanks a lot Asif. That would be great for me then; I only need to submit jobs at an earlier time point and delete the branch once job completed. |
There was a problem hiding this comment.
Hi @tamuri, I am submitting jobs to DIDE cluster and have found this change can be made to cli file so that we do not need to submit the command of mkdir in advance of submit job run command. Do you think this could be added to master that may be helpful for others but not affecting TLO functions or submitting jobs to Azure? I will be totally fine to make this change in my local branch though.
This branch is branched out from bs/expand_hcw_till_14Dec2024, so that we can safely revert it to a previous commit and run jobs of random samples of extra budget allocation here. This is due to consistency with the branch status of when the main analysis jobs were submitted.
Once jobs completed, could delete this branch.