-
Notifications
You must be signed in to change notification settings - Fork 49
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
WRF+SWAN WIND input grids #261
Comments
when it 'crashes' what actually happens? |
WRF starts normally. They should exchange data every 27 seconds. WRF works with 27,9,3 s. SWAN with 90 and 30. At 4:30, COAWST crashes. Errfile are empty, but PRINT (attached) doesn't show the continuation of the computation of SWAN. I address hereby this problem to SWAN. Let me know if i can provide additional files. Thanks a lot for the help coupling_belgium.txt |
ok first the models need to time step evenly into the coupling interval. how about WRF at like 30 10 and 5, and SWaN at 90 and 30, with a coupling at 90 sec? |
I did 45,15,5 in order to keep the same time step ratio of WRF, SWAN at 90,30 and coupling interval at 90. WRF grid 1 sent data to WAVE grid 1Timing for main: time 2022-03-29_00:01:30 on domain 3: 0.17093 elapsed seconds WRF grid 2 sent data to WAVE grid 1WRF grid 3 sent data to WAVE grid 1WRF grid 1 sent data to WAVE grid 2== SWAN grid 1 recv data from WRF grid 2 WRF grid 2 sent data to WAVE grid 2WRF grid 3 sent data to WAVE grid 2== SWAN grid 2 recv data from WRF grid 2 |
can you send the full output? |
log.coawst.txt |
looks like SWAN did not really statrt . I see |
It still crashed. I attach the outputs. I'm running SWAN in parallel, it shouldn't be a problem as long as the hotfiles are the same number of processors no? |
not sure. try this: |
Still the same problem, with the same output files. Unfortunately i cannot pinpoint where exactly it stops and why |
belgium.h.txt |
have you run swan nested by itself? |
Yes i ran both swan and wrf standalone models and they work. I could try, but i would like to understand why is the wind grid that creates problem. Without it works perfectly fine |
i would like to understand also. But i need your help. |
log.sandy.txt Ok sandy test case now crashes. Could be directly a problem with the installation, but that's odd. I was pretty sure back then to have the tutorial running. Thank you again for your time |
i dont see the error. mpirun -np 2 ./coawstM Projects/Sandy/coupling_sandy.in &> outfile.txt |
ok. So i did a git pull, made a tar file, copied it to a new directory, untarred, set the build_coawst.sh to build the sandy case, edited the Projects/Sandy/sandy.h to be #undef ROMS_MODEL /.... rest of sandy.h is unchanged ./build_coawst.sh -j 14 .... WRF grid 1 recv data from WAVE grid 2WAVtoWRF Min/Max HSIGN (m): 0.000000E+00 8.345883E+00 WRF grid 2 recv data from WAVE grid 2WAVtoWRF Min/Max HSIGN (m): 0.000000E+00 8.363349E+00 Can you try those exact steps? |
Good afternoon,
i'm running COAWST simulations with WRF+SWAN coupling, on different grids. I'm trying to compare the results with WRF standalone simulations to assess the importance of wind wave interactions.
I'm having issues with the WIND grid of SWAN. If i don't select it, the simulation runs smoothly, but when i postprocess the results, there is zero difference with WRF standalone simulations. When i add only INPGRID, without READINP, the simulation crashes. I attach here my swan input files, hoping to figure out the problem.
Thanks in advance for the help.
swan_Belgium.txt
swan_Belgium_ref3.txt
The text was updated successfully, but these errors were encountered: