-
Notifications
You must be signed in to change notification settings - Fork 0
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
Run global UnWW3 to provide boundary to Atlantic set up #9
Comments
To do:
|
https://cds.climate.copernicus.eu/cdsapp#!/dataset/reanalysis-era5-single-levels?tab=form |
See meeting notes here: oceanmodeling/ufs-weather-model#83 |
@yunfangsun you've run this and generated a boundary condition, correct? The next step is to verify that the BC you created is correct? Can you add some info here:
|
Hi @aliabdolali , I have used your global wave model configuration and run a simulation, when I generate the whole filed by using ww3_ounf.inp vi ww3_ounf.inp
It only generate one time step of results
and the ww3_ounp.inp could give me the correct outputs, could you please suggest me what I should modify in Thank you! |
from what you pasted here, I see 45 time steps in the netcdf file. you can see those time steps if you try: ncdump -tv time ww3.202209_hs.nc |
but``` // global attributes: time = "2022-09-15", "2022-09-15 01", "2022-09-15 02", "2022-09-15 03",
|
please attach ww3_shel.inp(nml) and ww3_ounf.inp(nml) here |
ww3.shel.nml
ww3_ounf.inp
|
change $ 20220901 000000 10800 999 to $ 20220901 000000 3600 9999 in ounf.nml |
in case you did not fix it, send me an invite and we can take a look at your log.ww3 and see what's wrong there |
Hi @aliabdolali |
It shouldn't, it is either a bug or some hidden character. That is why we switched to nml at ERDC |
For this week, I will try to set up to use the spectra from the outputs of the global wave model as open boundary conditions to drive the Atlantic domain with the coarse-resolution SCHISM mesh. |
awesome, keep up posted on your progress or if you faced an issue. |
@janahaddad thanks for the tag up this morning and suggestion to post here for UFS Coastal Applications Team (CAT) project. Several UFS CAT testers (a couple at Colorado School of Mines, and a couple at Univ of South Florida) are interested in getting WW3 outputs for boundary conditions/forcing for their testing of SCHISM and FVCOM. The location is Mid-Atlantic Bight (NY/NJ Harbor). The time periods are: This is an initial comment to track this issue and start the discussion. Thank you. |
@yunfangsun just following up on the above. Let me know if you were able to find out anything about the NOAA operational WW3 output (issues in wave spectra data but only prior to 2020 or 2016?) from the HPSS tapes. Thanks! |
Hi @gseroka , I have just rechecked, the global GFS wave spectra product from EMC is available from March 21, 2021, to June 26, 2022, version 16.2 from June 27, 2022, to Nov 29, 2022, version 16.3 from Nov 30, 2022, to now. The spectra bin number is 50, direction bin number is 36. The locations of the buoy around the Mid-Atlantic Bight are as follows: The spectra bin is 50, the direction bin is 36. The global wave model is updated every 6 hours, with 384-hour results, we need to pick up the first 6 hours of each run to interpolate the open boundary conditions. And before March 21, 2021, there are not enough buoy outputs from the global GFS wave model outputs. I have downloaded the wave spectra from HPSS on Hera for Jun 1 - Sep 30, 2021, and Dec 1, 2021 - Mar 31, 2022. And you can find some samples of the spectra on Hercules in the folder /work2/noaa/nosofs/yunfangs/hpss/2021/gfs.20210601/06/wave/station |
@yunfangsun thank you so much, highly appreciated. I will take a look and I will probably have some questions. Thank you again! |
@yunfangsun I added a short meeting tomorrow morning with you and Ayumi to discuss this. Let me know if this time doesn't work, thanks! |
Hi @gseroka , Yes, it works for me, should @janahaddad also be involved? |
Sure, I'll add her! (as optional) |
https://github.com/noaa-ocs-modeling/SurgeTeamCoordination/issues/431
...continue documenting this task here
The text was updated successfully, but these errors were encountered: