Skip to content
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

Give users the option to delete DATAROOT when running setup_expt.py/setup_xml.py #3071

Open
6 tasks
DavidHuber-NOAA opened this issue Nov 5, 2024 · 0 comments
Labels
feature New feature or request triage Issues that are triage

Comments

@DavidHuber-NOAA
Copy link
Contributor

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 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request triage Issues that are triage
Projects
None yet
Development

No branches or pull requests

1 participant