-
Notifications
You must be signed in to change notification settings - Fork 106
Changes to enable coupling with WW3 using 3d vortex formulation #162
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
Changes to enable coupling with WW3 using 3d vortex formulation #162
Conversation
|
@josephzhang8 JFYI. |
|
Looks good; thx @uturuncoglu. |
|
@josephzhang8 Thanks for asking, let is wait for the discussion to solve the build issue under UFS coastal. This could include some extra work about it. More info: schism-dev/schism-esmf#32 (comment) |
|
@josephzhang8 Are we expecting answer change in this version of SCHSIM? This branch is sync with the master and I am running DATM+schism configuration (no WW3). I am seeing some difference in the output when it is compared with the RT baseline. Both |
|
@josephzhang8 I have just check that mediator history file is fine. So, the difference is caused by SCHISM. |
|
@josephzhang8 Here is the details from first time step, We have only difference in air pressure but not with wind. Second coupling time step is also same but in third we have also difference in wind. |
|
Yes, differences are expected due to changes from nws=2 to 4. USE_ATMOS assumes atmos model will fill in those arrays on SCHISM mesh. Also, I added air-sea exchange for this option (which was missing before). |
|
@josephzhang8 Okay. Thanks for clarification. It seems that the model is modifying the given forcing as input or through the couplign interface. Is this a correct assumption? If so maybe it would be nice to add unmodified forcing to the output too since this could confuse the user if they compare the input with the output. |
|
@uturuncoglu: no the code does not modify inputs like wind, pressure etc. I think this is related to reading inputs in 2 time records '1' and '2'; in _step, time interpolation is done from these 2 to get the values at the 'current' time. What are the var names you used for outputs? |
|
@josephzhang8 So, we have difference due to the temporal interpolation. Is it because model internal time step is different than the coupling time step? I am just checking |
|
Below is the code in _step that save vars read in from ATMOS model: So basically, first 5 vars are saved into '2' and the others are saved as the values at this (SCHISM) time step (no time interp). Time interp is done for the first 5 vars. I think older versions only have first 3 vars. So I think you can use the new results as RT, with the understanding that results might evolve further based on the specific requirements of the coupling. Thx. |
|
@josephzhang8 Tests are good and I created baselines. This PR can be merged now. Once it is merged, I'll update UFS coastal to point recent version. Thanks for your help. |
This are changes in the model side that needs to be merged to complete the 3d vortex coupling. Since, schism-dev/schism-esmf#32 is already merged. this could be merged as well.