-
Notifications
You must be signed in to change notification settings - Fork 6
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+WW3 DuckNC #128
Comments
By using the version of c6492b9, the duck case gives the following err message: The error message appears both in the ufs-coastal ww3 and atm+ww3 are related to the initial configurations.
|
Then I compiled the WW3 stand-alone with the same configuration of UFS-coastal WW3 (812b8f7) and reproduce
To compare the ww3 stand-alone cases of the successful and failed ones: I find the switch has been modified: The successful one is The failed one is |
Then I modified the UFS-coastal to use the switch of The 52 error is not existed any more. And the ufs-coastal ww3 shows the following errors:
And the ufs-coastal atm+ww3 shows the following errors:
|
By adding a
|
Although there are no errors about the water level forcing and the log shows the water level information is read from the namelist, the output of water level shows zero fields:
Then I try to add a level.ww3 file as external forcing, and tried both INPUT%FORCING%WATER_LEVELS = "H" or "T", there are error messages about the water levels, however, the water level outputs are always 0, which is different from the WW3 stand-alone outside ufs-coastal. |
And for the ATM+WW3 duck case, there are errors from the mediator:
|
For this ATM+WW3, the WW3 switch used is in ufs-weather-model/WW3/model/bin/switch_meshcap_pdlib |
Hey @SmithJos13, @yunfangsun will need a DOCN component in for this wave case with sea level surface field input. Would it be possible to share your path for your docn cice case and give Yunfang permissions to read? |
@ Do you want access to me version of UFS coastal DIR that I have been working on? If so here you go. I think the copy all data mode has been modified to accept some more fields, and you can look at the CMEPS coastal coupling mode to see how the exchange of information is handled in the mediator
This is the working directory on Hercules. Let me know if the permissions are lacking and I can fix it. |
Hi @SmithJos13, I can access the folder of /work2/noaa/vdatum/jsmith/dev/ufs-coastal-cice-dev/, however, I am not in the group of vdatum, I can't read most of the files in the folder, for example /work2/noaa/vdatum/jsmith/dev/ufs-coastal-cice-dev/tests, /work2/noaa/vdatum/jsmith/dev/stmp/jsmith/FV3_RT/rt_182747. Could you please add the other user to read permission? Thank you! Best, Yunfang |
@yunfangsun does this mean I need to give you access to the vdatum folder? Or maybe the issue is that I have you read privileges to all the folders and not the files! I’ll look into this and let you know when I fixed it. Best wishes, |
Hi @SmithJos13 , I am not in the vdatum group, therefore, you have to change the permission of the files from 750 to 755, then I can read the files in your folder. Best, Yunfang |
@yunfangsun ahhh gotcha! I’ll fix that! |
@yunfangsun okay let me know if it's working now! You should have 755 for all DIR in the folder and 644 for all the files. I think that should be good enough? |
Hi @SmithJos13 , Thank you, I can see the file in the folder of Thank you! |
Okay, I think it should be good now! let me know if it is working. |
Hi @uturuncoglu @janahaddad , The original CDEPS's ocn components only have T, U, V variables, therefore, I am using @SmithJos13 's docn_datamode_cice_roms_output_mod.F90, config_component.xml and stream_definition_docn.xml to compile the ATM+WW3 case. And add the docn_in:
and docn.streams:
ufs.configure:
and try to run the ATM+WW3 case with
It gives me the following error messages:
@uturuncoglu , do you have any suggestions? The case is located at /work2/noaa/nosofs/yunfangs/stmp/yunfangs/FV3_RT/rt_2692414_cdep_12302024/coastal_duck_atm2ww3_intel |
@yunfangsun, from our meeting today:
|
Hi @uturuncoglu , I would like to make it clear that for the option in docn_in
It will directly try to find the mode in the folder of CDEPS-interface/CDEPS/datm Do I need further modifications to point it to the datamode when I am compiling it? Thank you! |
@yunfangsun I think data mode is fine but for |
Hi @uturuncoglu , Could I know which file should I take a look at in the folder of Thank you! |
@yunfangsun I think copy all uses |
By using the CDEPS-interface/CDEPS/docn/docn_datamode_copyall_mod.F90 from Joey, and add
And for the WW3, by uncommenting of WW3/model/src/wav_import_export.F90 the Now the code is in /work2/noaa/nosofs/yunfangs/ufs-3d/ufs-weather-model_cdep_01052025/ |
No description provided.
The text was updated successfully, but these errors were encountered: