-
Notifications
You must be signed in to change notification settings - Fork 5
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
ufs-coastal DATM+SCHISM DuckNC #127
Comments
@mansurjisan next steps discussed today, per my notes (plz edit/comment as needed)
|
I completed the following simulations and uploaded the water elevation and wave height plots to Google Drive.
|
@mansurjisan I used your scripts to generate input files for the RT. That are working fine but I did not integrate them to the workflow or try to run the case yet. I have also couple of suggestion and question about the scripts,
Is there any way to get those files from public space. Do we need to register?
Anyway, I think overall it is great to have these script. Thanks for your help. I am plaining to move these scripts to app level and integrate with the workflow. |
@mansurjisan I saw you tested replacing seawater with gsw in your pyschism fork right? |
@mansurjisan I have one minor question. In |
Hi @uturuncoglu , Regarding your questions about gen_bnd.py:
For the Duck, NC RT case, I am using a different approach to generate required elev.th file. Pyschism currently doesn't have the function to generate this file. I've used OSU OTPS for this, but I'm working on generating it directly with pyschism. |
@janahaddad, yes, you're correct! I've addressed this issue in my fork of pyschism. Here's what I did:
If you're interested in implementing these changes, I'd be happy to provide more details or assist with any questions you might have about the modification process. |
@mansurjisan @janahaddad JFYI, I integrated https://github.com/oceanmodeling/ufs-coastal-app/tree/feature/workflow I think that |
@mansurjisan BTW, why you are calling |
@mansurjisan |
Hi @uturuncoglu , thanks for letting me know. I'll look into this as soon as the Hercules cluster is back online. |
For most of our RT cases, we will likely use either TPXO or HYCOM to generate boundary conditions. Regarding TPXO, since it requires user registration to download the files, we may not be able to distribute those files via GitHub. One potential solution is to use HYCOM for all RT cases, which would avoid this issue. We can discuss this further and explore what steps are needed during our Monday meeting. |
Hi @uturuncoglu , I’ve uploaded the missing hgrid.ll file to the /data directory, which should resolve the issue with gen_bctides.py. You can find it here: GitHub link. Please give it a try and let me know if you encounter any further issues. |
@mansurjisan Thanks but I think that the issue with |
Hi @uturuncoglu , I see, thanks for the clarification. You can access the TPXO dataset files directly from my directory on Hercules: Unfortunately, due to TPXO registration restrictions, I’m unable to upload the files to GitHub. Let me know if this resolves the issue or if you encounter any other problems. |
@mansurjisan Yes. I am using same location but when I run the script. It could not find the required files and I think it is not looking your directory. So, I wonder if you tested that script recently. |
Hi @uturuncoglu , Yes, I just ran the script and it was able to access the required files without any issues. I also placed these files in |
@mansurjisan Yes, I think that it is the trick. So, it is getting them from |
Hi @uturuncoglu , I think you're right, it seems like the script is defaulting to I'll work on this and keep you updated! |
@mansurjisan Thank you. |
@uturuncoglu , here is an issue I am currently investigating related to the use of elev.th file in SCHISM within the UFS-Coastal. We can discuss it more during today's meeting. |
Updated simulations with elev2D.th.nc file instead of using elev.th file due to possible bug
SCHISM Required Files Table (Duck, NC RT 1994 Case)
Note: This table includes the core files typically required for each configuration. Additional files might be necessary depending on specific model setups and options chosen in the parameter files.
Next steps
|
related to Implementing Flexible Build Steps in UFS-Coastal Using ecFlow's Event-based Triggers |
(9/10/2024 moving @mansurjisan updates from SSM team repo)
Note that this Issue also includes steps to be integrated at the app-level workflow oceanmodeling/ufs-coastal-app#8 & oceanmodeling/ufs-coastal-app#9, and testing for other NOAA-OCS workflows outside ufs-coastal (noaa-ocs-modeling/SurgeTeamCoordination/issues/563)
Repository Link
UFS-Coastal-Inputs on GitHub
Objective
The primary goal of this project is to develop scripts that will be integrated into the UFS coastal app workflow to generate input files for regression tests (RT). These scripts ensure consistency and allow for easier validation of the input file generation process across different test cases.
Current Status
Key Features
PySCHISM
library for SCHISM model input file generationRecent Activities
gen_gr3_input.py
gen_bctides.py
gen_bnd.py
Script Details
1. gen_gr3_input.py
/scripts/coastal_ike_shinnecock_atm2sch/gen_gr3_input.py
python gen_gr3_input.py
2. gen_bctides.py
/scripts/coastal_ike_shinnecock_atm2sch/gen_bctides.py
3. gen_bnd.py
/scripts/coastal_ike_shinnecock_atm2sch/gen_bnd.py
python gen_bnd.py
Project Structure
Next Steps
Recent Activities
Visualizations
Model Grid File
Depth-Averaged Velocity Map
https://drive.google.com/file/d/1r8XpCgZp7EGT_WnVgao2I9VC8m58_rha/view?usp=sharing
Wind Input Visualization
https://drive.google.com/file/d/1dp5VYbAoaY8BG97WDd_qkVMUcfCPIX-_/view?usp=sharing
https://github.com/user-attachments/assets/88284baa-7466-46cf-b70e-3315ad23e5b7
Snapshot of elevation
https://drive.google.com/drive/folders/1aqsMBu_0c4fNmoTMmcEp7HUWygky0vJZ?usp=sharing
The text was updated successfully, but these errors were encountered: