Skip to content
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

coawst runs but logs don't grow #188

Open
arief121 opened this issue Oct 30, 2023 · 6 comments
Open

coawst runs but logs don't grow #188

arief121 opened this issue Oct 30, 2023 · 6 comments

Comments

@arief121
Copy link

Dear all,

I tried to create a simulation by modeling the JOETC project by coupling the WRF+ROMS+SWAN model. The planned simulation is for 3 days with each timestep WRF=54s; ROMS=27s; SWAN=270s.

coawst can be compiled and produced coawstM. when coawst is executed, the model runs until the 130th timestep. the model writes :

+time 20221229.094500 , step 130; iteration 1; sweep 4 grid 1
1299 2022-12-29 09:44:33.00 6.176085E-03 2.044396E+04 2.044397E+04 1.365553E+15
(059,049,20) 2.034723E-03 8.678012E-07 2.918013E-02 1.490179E+00
1300 2022-12-29 09:45:00.00 6.177132E-03 2.044396E+04 2.044397E+04 1.365553E+15
(059,049,20) 2.051754E-03 3.173592E-06 2.964586E-02 1.490560E+00
Timing for Writing wrfout_d01_2022-12-29_12:00:00 for domain 1: 1.75411 elapsed seconds
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF
d01 2022-12-29_12:00:00 wrf: SUCCESS COMPLETE WRF

that is the last line I got from the log file. I tried to check through slurm, the job model is still running, but the lines or text in the log file are not increasing.

Does anyone can help or have experience and information related to the problem I am experiencing? I've also attached the coupling.in, coupling.h, wrf.input, roms.in and swan.in files that I used in the simulation so you can see what I did to the model.

Thank you.
Arief
sunda_couple_log.log

coupling_sunda_h.txt
coupling_sunda_in.txt
roms_sunda_in.txt
swan_sunda_in.txt
namelist.input.txt
coupling_sunda.out.txt

@jcwarner-usgs
Copy link
Collaborator

thanks for providing all that info. i see
"Max map factor in domain 1 = 1.01. Scale the dt in the model accordingly."
...
Timing for main (dt= 45.94): time 2022-12-29_00:04:04 on domain 1: 0.16478 elapsed seconds
+time 20221229.000900 , step 2; iteration 1; sweep 4 grid 1
+time 20221229.000900 , step 2; iteration 2; sweep 1 grid 1
Timing for main (dt= 48.24): time 2022-12-29_00:04:53 on domain 1: 0.16964 elapsed seconds
+time 20221229.000900 , step 2; iteration 2; sweep 2 grid 1
+time 20221229.000900 , step 2; iteration 2; sweep 3 grid 1
Timing for main (dt= 50.65): time 2022-12-29_00:05:43 on domain 1: 0.16328 elapsed seconds
+time 20221229.000900 , step 2; iteration 2; sweep 4 grid 1
Timing for main (dt= 53.18): time 2022-12-29_00:06:36 on domain 1: 0.17756 elapsed seconds

The "Timing for main" is WRF. And WRF is adjusting the time step for each time. So the models will not come together at the same time for the coupling. We need to have the models all get to the same model time for the coupling.

can you set
use_adaptive_time_step = .false.,
in the wrf namelist and try again?

@jcwarner-usgs
Copy link
Collaborator

jcwarner-usgs commented Oct 31, 2023 via email

@arief121
Copy link
Author

arief121 commented Nov 6, 2023

Hi J,
thank you

yes, the model is running well now, and yes I realized that some of my WRF settings were wrong and changed it to 2 days.
another question, can I run coawst with 3 domains in one simulation? Are there any special settings that I have to do if I want to simulate using 3 domains at once? because I see in the sandy case, it only uses 2 domains.

Arief

@jcwarner-usgs
Copy link
Collaborator

it should work for 3 domains. i have had people do this. it just needs a different scrip file, and you need to add columns in the namelist.input.

@arief121
Copy link
Author

Hi J,

good news, now I can run a simulation with 3 domains, although the ROMS model is still blowup, but this is a good achievement in my opinion. thank you for your help.

Question, can I set the coawst model to run a simulation using different domain for wrf and the ocean? For example, WRF uses 3 domains, but the oceans (ROMS and SWAN) only use 2 domains, and are coupled in COAWST in one simulation. is it possible to do?

Arief

@jcwarner-usgs
Copy link
Collaborator

yes you can do wrf 3 domains, and 2 for roms and 2 for swan.
suggest you keep the roms and swan domains the same. those physics are on the same scale.
but you can do different size and number of wrf grids than the r+s grids.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants