-
Notifications
You must be signed in to change notification settings - Fork 136
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
Integer indexing for sub-regions in diag_table #1209
Comments
The current diag manager does not support the use of indices for a subregion. It only supports the use of lat/lon. The new diag manager being developed will support the use of indices. If this entry worked in your diag table, I am not sure how. If you have a problem with a lat/lon subregion, then we will be more concerned with that. What does the diag table entry look like for that? |
The lat/lon examples look much the same: They fail the same way since my domain covers the north pole and latitude is not monotonic across the domain, plus of course longitude wraps around at +/-180. |
@kshedstrom Would you be able to provide us with a workdir on gaea to reproduce the error? FYI , for a small global test case of MOM6-SIS2, when I use the 360 complements of the lons you used in diag_table the test runs:
but when I change it to your choice of longitudes I get an error
I get
It could be that FMS diag_manager is looking for bounding longitudes commensurate with the ocean_hgrid bounds (-280 to 80 in this test case). FYI, in the OM4p125 diag_table for sections Bering Strait bounds appear as:
|
Sure, my most recent run is in /lustre/f2/scratch/gfdl/Katherine.Hedstrom/work/fre/run23 |
I cannot access the ocean_hgrid.nc and probably the rest of the INPUT files to run your test:
|
Sorry, did I just fix it for you? |
Fixed in #1505 |
I swear I ran my regional Arctic domain with a bunch of cross sections saved, using the i,j indices of the cross sections. It no longer works, giving me the error:
FATAL from PE 0: diag_util_mod::get_index: array NOT monotonously ordered
I get this error with the lat/lon locations as well, since the lat/lon values are indeed not monotonously ordered.
Would it be possible to get the i,j indices working again, for instance like:
"ocean_model_z", "volcello", "volcello", "ocean_Bering_Strait", "all", "mean", "321 330 184 184 -1 -1",2
The text was updated successfully, but these errors were encountered: