RSAPIAIN_DMC
New member
Hello.
Managed to run MPAS finally, and now converting to lat/lon (using convert_mpas ) the history and diagnostic file output to visualize with ncview, but I'm getting some zones without any data.
Centro-RM was run with the 3km static mesh as a base; Sinoptico-15km used the 15km static mesh as a base, 120 forecast hours, file output every 1-hr-forecast, using GFS 0p25 data ungribbed with WPS 4.1
I'm seeing that weird white area in the space... I guess it means there is no data there. I tested with various forecast hours and the white-area doesn't change at all; and it happens with all the variables.
The nlat and nlon were made in a best-guess given the meshes used in each case:
I'm attaching what I get, and the simulation run logs:
only warning on initial conditions, no warning on border condition computations; some warnings on the atmosphere-run; no errors in log.
I haven´t used the files: include_fields , nor the exclude_fields (but definitely I'm thinking that I should).
My questions:
1.- For the MPAS simulation, should the area of simulation be larger by at least 1 deg on each side?
(for example, for Centro: rectangle( (-31.5, -67.5), (-35.5, -73.5 )) for the MPAS-run, and then perform the convert_mpas with the target_domain config specified previously?) )
2.- Or are those 'white areas', are something that is expected to happen ? Or maybe something with the specific GFS data that day?
Thank you in advance.
Managed to run MPAS finally, and now converting to lat/lon (using convert_mpas ) the history and diagnostic file output to visualize with ncview, but I'm getting some zones without any data.
Centro-RM was run with the 3km static mesh as a base; Sinoptico-15km used the 15km static mesh as a base, 120 forecast hours, file output every 1-hr-forecast, using GFS 0p25 data ungribbed with WPS 4.1
I'm seeing that weird white area in the space... I guess it means there is no data there. I tested with various forecast hours and the white-area doesn't change at all; and it happens with all the variables.
The nlat and nlon were made in a best-guess given the meshes used in each case:
- 3km means about 32 or 33 points per lat.degree; Centro-3k has 3-deg lat and 6 deg. lon in the pts file definition
- 15km... I guess I interpolated at 10km by mistake (Sinoptico15 has only a small white patch on top, but the rest of the data has values)
Code:
cat Centro-RM-3k/target_domain
nlat = 99
nlon = 198
startlat=-32.0
startlon=-68.0
endlat=-35.0
endlon=-74.0
Code:
cat Sinoptico15/target_domain
startlat = -15.0
startlon = -115.0
endlat = -55.0
endlon = -65.0
nlat = 400
nlon = 500
I'm attaching what I get, and the simulation run logs:
only warning on initial conditions, no warning on border condition computations; some warnings on the atmosphere-run; no errors in log.
I haven´t used the files: include_fields , nor the exclude_fields (but definitely I'm thinking that I should).
My questions:
1.- For the MPAS simulation, should the area of simulation be larger by at least 1 deg on each side?
(for example, for Centro: rectangle( (-31.5, -67.5), (-35.5, -73.5 )) for the MPAS-run, and then perform the convert_mpas with the target_domain config specified previously?) )
2.- Or are those 'white areas', are something that is expected to happen ? Or maybe something with the specific GFS data that day?
Thank you in advance.