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

Barotropic run setup #35

Closed
seshrajagopal opened this issue Jun 20, 2023 · 1 comment
Closed

Barotropic run setup #35

seshrajagopal opened this issue Jun 20, 2023 · 1 comment

Comments

@seshrajagopal
Copy link
Contributor

seshrajagopal commented Jun 20, 2023

  1. How do you check that prepare_schism finished successfully? Presently we rely on the message "done" at the end of the process and check if the gr3 files were created.
  2. How do you check elev2D.bat was successful? Currently you check that the elev2D.*.th.nc is created, is there any other way to check?
  3. multi_clip uses a DCD sink source file, it is unclear how that sink file is created.
@water-e
Copy link
Collaborator

water-e commented Jul 22, 2023

Shey I'm closing this because the ideas are too broad to be a single issue in issue tracking. I have created issue #38 to convey that we would like to address regression testing items.

If you see "Done" there probably was no error with prepare_schism. Similarly you should see elev2D bomb. prepare_schism does about 20 things, so hard to be specific. For elev2D the things that can go wrong is that NOAA delivers an unexpected datum (they've gone back and forth between using NAVD88 or NAVD in the URL and it lapses to a station datum if you do it wrong). Or sometimes data at Point Reyes is missing ... you'll get warned about that though.

@water-e water-e closed this as completed Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants