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
If a user needs to restart an experiment, the DATAROOT directory may still be populated with the previous experiment's forecast files. This can cause the forecast job to restart from the last available forecast restart file set. However, if COMROOT does not contain the product files for hours previous to the restart files, then the prod jobs will fail.
To help with this issue, the setup scripts should check if DATAROOT exists. If it does, they should prompt the user and let them decide whether it should be deleted.
What are the requirements for the new functionality?
One or both of setup_xml.py and setup_expt.py should check for the existence of DATAROOT at setup time
A prompt should be given to let the user know and ask if it should be deleted
Answering 'yes' should delete this directory
Acceptance Criteria
There are no changes to the CI test results
Documentation on the new feature is clear
The feature is tested and incorporated into create_experiment.py and generate_workflows.sh
Suggest a solution (optional)
No response
The text was updated successfully, but these errors were encountered:
What new functionality do you need?
If a user needs to restart an experiment, the DATAROOT directory may still be populated with the previous experiment's forecast files. This can cause the forecast job to restart from the last available forecast restart file set. However, if
COMROOT
does not contain the product files for hours previous to the restart files, then theprod
jobs will fail.To help with this issue, the setup scripts should check if
DATAROOT
exists. If it does, they should prompt the user and let them decide whether it should be deleted.What are the requirements for the new functionality?
DATAROOT
at setup timeAcceptance Criteria
create_experiment.py
andgenerate_workflows.sh
Suggest a solution (optional)
No response
The text was updated successfully, but these errors were encountered: