[ncl-talk] Coordinate syronising error
Dennis Shea
shea at ucar.edu
Wed Jun 2 21:31:44 MDT 2021
Rashad is correct.
Variable: cocol_retr_flip
Dimensions and sizes: [ncl_join | 12] x [XDim_MOP03 | 360] x [YDim_MOP03
| 180]
Coordinates:
XDim_MOP03: [-179.5..179.5] <=== these are longitudes
YDim_MOP03: [ 0.5..359.5] <=== these are longitudes
also
Both coordinate variables have ranges for longitudes. These values are not
suitable for latitudes.
Further, you have:
Variable: cocol_retr_flip
Dimensions and sizes: [ncl_join | 12] x [XDim_MOP03 | 360] x [YDim_MOP03
| 180]
For comparison the model output, it should be [lat,lon]
[ncl_join | 12] x [YDim_MOP03 | 180] x [XDim_MOP03 | 360]
-----
I have one [old] MOP03 file the latitudes range from:
YDim_MOP03:: 89.5 ..-89.5 [North to south ordering]
The variables do have ( XDim_MOP03, YDim_MOP03 ) ordering.
This can be rectified by using NCL's named dimension reordering.
After *addfiles*:
cocol_retr_flip := cocol_retr_flip(:,YDim_MOP03|:,XDim_MOP03|:) ;
reorder to (12,lat,lon)
printVarSummary( cocol_retr_flip ) ; ***LOOK at this*** especially
the ordering
Now reorder from N->S to S->N
cocol_retr_flip := cocol_retr_flip(:,::-1,:)
printVarSummary( cocol_retr_flip ) ; ***LOOK at this*** especially
the latitude coordinates
=========
I suggest that you only work on the one MOP03 variable to workk out the
ordering.
On Wed, Jun 2, 2021 at 10:03 AM Rashed Mahmood <rashidcomsis at gmail.com>
wrote:
> But even if it is the case, then still the range in your: XDim_MOP03:
> [-179.5..179.5], does not make sense for a latitude range. latitude range
> should be within -90 to 90. You need to look into your data to make sure it
> is read correctly. Also a suggestion, please reduce your script for
> debugging and test it with one input file.
>
> On Wed, Jun 2, 2021 at 5:52 PM Najib Yusuf <najibgal at yahoo.com> wrote:
>
>> No Rashed, could it be interchanged with longitude?
>>
>> Sent from Yahoo Mail on Android
>> <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
>>
>> On Wed, 2 Jun 2021 at 16:32, Rashed Mahmood
>> <rashidcomsis at gmail.com> wrote:
>> The latitude range from the variable summary looks strange:
>> Coordinates:
>> XDim_MOP03: [-179.5..179.5]
>> *YDim_MOP03: [ 0.5..359.5]*
>> Do you know why latitudes are expanding from 0.5 to 359.5?
>>
>> On Wed, Jun 2, 2021 at 4:39 PM Najib Yusuf via ncl-talk <
>> ncl-talk at mailman.ucar.edu> wrote:
>>
>> Dear Dennis,
>>
>> Thank you for this quick response. I have effected the suggestion, the
>> printVarSummary is:
>>
>> Variable: co_model
>> Type: float
>> Total Size: 148635648 bytes
>> 37158912 values
>> Number of Dimensions: 4
>> Dimensions and sizes: [time | 12] x [lev | 56] x [lat | 192] x [lon |
>> 288]
>> Coordinates:
>> time: [ 31.. 365]
>> lev: [1.867879997007549..992.5000106104562]
>> lat: [ -90.. 90]
>> lon: [ 0..358.75]
>> Number Of Attributes: 4
>> mdims : 1
>> units : mol/mol
>> long_name : CO concentration
>> cell_methods : time: mean
>>
>> Variable: cocol_retr_flip
>> Type: float
>> Total Size: 3110400 bytes
>> 777600 values
>> Number of Dimensions: 3
>> Dimensions and sizes: [ncl_join | 12] x [XDim_MOP03 | 360] x
>> [YDim_MOP03 | 180]
>> Coordinates:
>> XDim_MOP03: [-179.5..179.5]
>> YDim_MOP03: [ 0.5..359.5]
>> Number Of Attributes: 5
>> long_name : Retrieved CO Total Column Day
>> units : mol/cm^2
>> _FillValue : -9999
>> projection : Geographic
>> lonFlip : longitude coordinate variable has been reordered via
>> lonFlip
>>
>> However, when I run I get similar error:
>> fatal:NclOneDValGetClosestIndex: finish coordinate index out of range,
>> can't continue
>> fatal:Could not obtain coordinate indexes, unable to perform subscript
>> fatal:["Execute.c":8637]:Execute: Error occurred at or near line 172 in
>> file Annualaverage_MOPITTCO_nyg_modified.ncl
>>
>> I know you are busy, kindly spare some time to assist me look at the
>> script as you use to.
>>
>> Thank you sir.
>>
>> Najib
>>
>>
>>
>> On Tuesday, June 1, 2021, 09:29:32 PM GMT+1, Dennis Shea <shea at ucar.edu>
>> wrote:
>>
>>
>> I don't have the time to look at your script right now.
>>
>> However, The lat/lon ranges are different.
>>
>> In particular the longitudes. Likely, you will have to make the
>> longitudes both be (nominally) 0-to-360 or -180-to180
>> You can use *lonFlip*
>> <http://www.ncl.ucar.edu/Document/Functions/Contributed/lonFlip.shtml>
>> to accomplish this.
>>
>> Variable: co_model
>> Dimensions and sizes: [time | 12] x [lev | 56] x [lat | 192] x [lon |
>> 288]
>> Coordinates:
>> time: [ 31.. 365]
>> lev: [1.867879997007549..992.5000106104562]
>>
>> * lat: [ -90.. 90] lon: [ 0..358.75*]
>>
>> Variable: cocol_retr
>> Dimensions and sizes: [ncl_join | 12] x [XDim_MOP03 | 360] x
>> [YDim_MOP03 | 180]
>> Coordinates:
>>
>> * XDim_MOP03: [-179.5..179.5] YDim_MOP03:
>> [-89.5..89.5]*
>> ~
>>
>> On Tue, Jun 1, 2021 at 5:17 AM Najib Yusuf via ncl-talk <
>> ncl-talk at mailman.ucar.edu> wrote:
>>
>> Dear NCL users,
>>
>> I am comparing CO from MOPITT satellite retrieval and model CAM output
>> with averaging kernel been considered. I am having trouble synchronising
>> the coordinates amd the error is:
>> fatal:NclOneDValGetClosestIndex: finish coordinate index out of range,
>> can't continue
>> fatal:Could not obtain coordinate indexes, unable to perform subscript
>> fatal:["Execute.c":8637]:Execute: Error occurred at or near line 165 in
>> file Annualaverage_MOPITTCO_nyg_modified.ncl ( under: Collect
>> equivalent profile)
>>
>> I look around NCL examples but couldn't figure out how to resolve the
>> issue and get the plot.
>> Kindly assist to figure out the solution to this. The script Annualaverage_MOPITTCO_nyg_modified.ncl
>> and the run CO_MOPITT_MODEL_Comparison_run are attached.
>>
>> Thank you for your support.
>> _______________________________________________
>> ncl-talk mailing list
>> ncl-talk at mailman.ucar.edu
>> List instructions, subscriber options, unsubscribe:
>> https://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>> _______________________________________________
>> ncl-talk mailing list
>> ncl-talk at mailman.ucar.edu
>> List instructions, subscriber options, unsubscribe:
>> https://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.ucar.edu/pipermail/ncl-talk/attachments/20210602/bf29fdd4/attachment.html>
More information about the ncl-talk
mailing list