Add coastal_sandy_duck_atm2sch2ww3 regression test#188
Add coastal_sandy_duck_atm2sch2ww3 regression test#188mansurjisan wants to merge 1 commit intooceanmodeling:feature/new_rtfrom
Conversation
- Add new regression test for Sandy Duck with ATM2SCH2WW3 coupling - Fix CSTLSW WW3 component enabling in configure_apps.cmake - Remove -DBUILD_TOOLS=ON from atm2sch2ww3 compile configurations - Add nest.ww3 and namelists.nml copy to coastal_ww3_run.IN - Update LIST_FILES to include WW3 field outputs and restart files
|
Hi @uturuncoglu , I added the Duck NC regression test for the DATM+SCHISM+WW3 configuration. Please take a look when you get a chance. The input data location on Hercules HPC is: /work2/noaa/nos-surge/mjisan/RT_INPUT/ And the baseline directory is: The regression tests show a failing status when compared to the baseline results. I double checked the results and the differences in water elevation and wave height between baseline results and RT are zero at the first time step, but differences increase with each time step. This is something we also observed in Ike Shinnecock DATM+SCHISM+WW3 run. |
|
@mansurjisan I checked your configuration. It seems you are using 300 s as coupling interval. So, I modified the case to write mediator history file in every Couling step to see when or which component is starting to change the answer. The first coupling time step (t=300) the files were identical (I am checking with NCAR's cprnc tool) between two different runs but then at 600, it started to change. Here are the variables that are changing, As you could see all the fields have wavImp_* prefix. So, those are exported from the wave component. There might be some issue in the wave model configuration that leads to the difference. I am not seeing any issue in ocean side. To be sure, it would be nice to (a) run the model without any feedback from ocean to wave. If you still see some difference, that definitely there is something wrong with wave setup. (b) run the same case without ocean like DATM-WAV. If WAV results are still changing, there again there is something wrong with wave. Another question is that this configuration uses different atmospheric forcing than atm2sch. Why? We are trying to bring different Duck configurations but I am expecting to have them consistent in terms of forcing and just adding component or removing. So, we could clearly see the affect of single component or catch the issues. Anyway, let's discuss those in the meeting. |
Commit Queue Requirements:
Description:
This PR adds a new coastal regression test for Hurricane Sandy at Duck, NC with ATM-SCHISM-WW3 coupling configuration. The test includes:
This PR also fixes an issue where
coastal_ike_shinnecock_atm2sch2ww3was failing in the feature/new_rt branch due to missing CSTLSW in the WW3 enable regex and incompatible build flags.Commit Message:
Priority:
Git Tracking
UFSWM:
Sub component Pull Requests:
UFSWM Blocking Dependencies:
None
Blocked by #
None
Documentation:
Changes
Regression Test Changes (Please commit test_changes.list):
Input data Changes:
/work2/noaa/nos-surge/mjisan/RT_INPUT//work2/noaa/nos-surge/mjisan/RT_INPUT/DATM_input_data/Sandy/(mesh_datm.nc, wind.nc)/work2/noaa/nos-surge/mjisan/RT_INPUT/SCHISM/Sandy/atm2sch2wav/(hgrid.gr3, vgrid.in, param.nml, bctides.in, etc.)/work2/noaa/nos-surge/mjisan/RT_INPUT/WW3/Sandy/atm2sch2wav/(mesh_duck.nc, mod_def.ww3, nest.ww3, ww3_shel.nml, namelists.nml, points.list)Baseline Location:
/work2/noaa/nos-surge/mjisan/ufs-weather-model/tests/stmp/mjisan/FV3_RT/REGRESSION_TEST/coastal_sandy_duck_atm2sch2ww3_intel/Library Changes/Upgrades:
Testing Log: