You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UFS-DA jobs currently look within the UFS-DA repo for a lot of settings (parm files, yaml files, etc.). To meet EE2 standards, all these need to be located in the global-workflow structure. These files can be linked from UFS-DA using the link_workflow.sh script (in ops, this script copies the files rather than using symlinks), or they can just be moved to the g-w repo.
What are the requirements for the new functionality?
No job can point to any file located within gdas.cd (or any other repo held within sorc). All needed files need to be linked/copied to parm during the link step of workflow setup or moved to the workflow repo entirely. Work with workflow CMs about names if you need new directories for this in parm.
Acceptance Criteria
All UFS-DA jobs run as before.
No job uses a path that includes gdas.cd or another directory in sorc.
Suggest a solution (optional)
No response
The text was updated successfully, but these errors were encountered:
What new functionality do you need?
UFS-DA jobs currently look within the UFS-DA repo for a lot of settings (parm files, yaml files, etc.). To meet EE2 standards, all these need to be located in the global-workflow structure. These files can be linked from UFS-DA using the
link_workflow.sh
script (in ops, this script copies the files rather than using symlinks), or they can just be moved to the g-w repo.What are the requirements for the new functionality?
No job can point to any file located within
gdas.cd
(or any other repo held withinsorc
). All needed files need to be linked/copied toparm
during the link step of workflow setup or moved to the workflow repo entirely. Work with workflow CMs about names if you need new directories for this inparm
.Acceptance Criteria
All UFS-DA jobs run as before.
No job uses a path that includes
gdas.cd
or another directory insorc
.Suggest a solution (optional)
No response
The text was updated successfully, but these errors were encountered: