Questions related to 'move nest'

[jc sun]

Hello, everyone

I am conducting an experiment on Automatic Moving Nest (Vortex-following) and have three questions:

1. When I use MODIS terrain data, running wrf.exe generates wrfout_d0x files. However, when I follow the Tutorial instructions (i.e., export TERRAIN_AND_LANDUSE=1, set geog_data_res = 'usgs_30s+default' in namelist.wps, and set input_from_hires = .true., .true., rsmas_data_path = 'terrain_and_landuse_data_directory' in namelist.input), I noticed that running wrf.exe does not generate wrfout_d0x files. Instead, rsl.out.0000 files are created, and cyclone-related information can be found using the command grep ATCF rsl.out.0000. What could be the reason for the wrfout_d0x files not being generated?

2. Are the files within the same folder names in the WPS V4 Geographical Static Data and WPS V3 Geographical Static Data directories identical?

3. The official guidelines state: "The sst_update option cannot be used with sf_ocean_physics or vortex-following options." If I use vortex-following options while coupling ocean models and atmospheric models, can I use the sst_update option to analyze only the outermost grid data?

 

[kwerner]

I'll respond to each of your questions below:

1. When I use MODIS terrain data, running wrf.exe generates wrfout_d0x files. However, when I follow the Tutorial instructions (i.e., export TERRAIN_AND_LANDUSE=1, set geog_data_res = 'usgs_30s+default' in namelist.wps, and set input_from_hires = .true., .true., rsmas_data_path = 'terrain_and_landuse_data_directory' in namelist.input), I noticed that running wrf.exe does not generate wrfout_d0x files. Instead, rsl.out.0000 files are created, and cyclone-related information can be found using the command grep ATCF rsl.out.0000. What could be the reason for the wrfout_d0x files not being generated?

Can you please share your rsl* files? Please package all of them together in a *.tar file and attach that.

2. Are the files within the same folder names in the WPS V4 Geographical Static Data and WPS V3 Geographical Static Data directories identical?

There are a few differences between the two versions, but for the data that is used in both versions, the directory and files names should be the same. You can compare the files included in the standard download (highest resolution of each mandatory field) between version 4 and version 3.

3. The official guidelines state: "The sst_update option cannot be used with sf_ocean_physics or vortex-following options." If I use vortex-following options while coupling ocean models and atmospheric models, can I use the sst_update option to analyze only the outermost grid data?

The issue is that the sst_update parameter only requests a single setting (i.e., there isn't a setting for each domain), so it's either turned on for all domains, or it's turned off for all domains.

 

[Hans]

The issue is that the sst_update parameter only requests a single setting (i.e., there isn't a setting for each domain), so it's either turned on for all domains, or it's turned off for all domains.

Can we assume that auxinput4 settings have implemented settings for each domain? When I only set auxinput4_interval for d01, real.exe only generated the lower boundary file file for d01.
I think the thread related to 'moving nest' that I previously asked about is the result of set sst_update on the moving nest.
The problem was solved in this way at that time.

 

[jc sun]

Hi,kwerner
Thank you for your response!

For the first question, I have identified the cause. I was using "&" as a comment marker, and after changing it to "!", the issue no longer exists.

As for the third question, if I perform ocean-atmosphere coupling, the official guidelines suggest not enabling sst_update when using vortex-following.
However, if it is not enabled, doesn't that mean there would be no way to reflect the feedback between the ocean and atmosphere? What is your opinion on how to handle this issue in the simulation of tropical cyclones?

Looking forward to your reply, thank you very much.

 

[kwerner]

Hi,kwerner
Thank you for your response!

For the first question, I have identified the cause. I was using "&" as a comment marker, and after changing it to "!", the issue no longer exists.

As for the third question, if I perform ocean-atmosphere coupling, the official guidelines suggest not enabling sst_update when using vortex-following.
However, if it is not enabled, doesn't that mean there would be no way to reflect the feedback between the ocean and atmosphere? What is your opinion on how to handle this issue in the simulation of tropical cyclones?

Looking forward to your reply, thank you very much.

I'm so glad to hear you were able to solve the original issue. Since your new question is a different issue than the one orignally posted here, please start a new thread for this problem. Keeping each post focused on one issue makes the forum easier to read and search in the future. Thanks!

 

[zzy]

Hi,kwerner
Thank you for your response!

For the first question, I have identified the cause. I was using "&" as a comment marker, and after changing it to "!", the issue no longer exists.

As for the third question, if I perform ocean-atmosphere coupling, the official guidelines suggest not enabling sst_update when using vortex-following.
However, if it is not enabled, doesn't that mean there would be no way to reflect the feedback between the ocean and atmosphere? What is your opinion on how to handle this issue in the simulation of tropical cyclones?

Looking forward to your reply, thank you very much.

Excuse me, where did you change the "&" comment marker to the "!" comment marker

 

[jc sun]

Excuse me, where did you change the "&" comment marker to the "!" comment marker

In the namelist I provided,

&input_from_file = .true.,.true.,.true.,