Closed karlmsmith closed 6 years ago
Modified by jeremy.malczyk on 1 Jul 2008 23:36 UTC
Comment by steven.c.hankin on 1 Jul 2008 23:56 UTC There is definitely some kind of script error -- or an incorrect passing of symbols to the script. The carbon cruise variables returned from the database are ungridded, which means (I presume) that Ferret sees them on a 1D grid which is simply an X axis that runs from 1, ..., Npoints. The line of the Ferret script that gives the error is
STAT atm_press[d=1,X=-178:-130]
In this command Ferret is being asked for atm_press based upon its longitude range -- as if it were a gridded variable. Wrong logic.
Comment by @AnsleyManke on 8 Jul 2008 18:17 UTC I think this is fixed, it was a bug in the Ferret scripts, and the fix checked in June 16 [r3061] on the trunk and also checked in on the v7.0.beta branch. The comment in the script is: ''! region syms also dont apply to insitu data (they are just on an abstract axis)''
Jeremy's original request wont run right now, but below is one which I believe is similar.
To test this Jeremy, you can update only the Ferret scripts if you don't want to take the time to update everything on your test server. Update the ferret scripts, and copy them to these directories as set up in a CUSTOMIZATION directory, $(ARMSTRONG_HOME)/WebContent/WEB-INF/classes/resources/ferret/scripts/ $(CATALINA_HOME)/webapps/$(LAS_NAME)/WEB-INF/classes/resources/ferret/scripts/
Reported by jeremy.malczyk on 1 Jul 2008 23:34 UTC Near as I can tell, this is a Ferret error and not an LAS configuration error. There are only 2 places, AFAIK, where the Lat and Lon domains are specified, the database_access and axes blocked in the dataset configuration xml. Both of these are set correctly (-180 to 180) but I keep gettign out of range errors on the x axis (it usually tells me the grid spans 0.5 to something huge, like 5545).
Perhaps more telling is that this error only seems to happen on queries that return less than about 200 points (although it is hard to tell, the smallest I have been able to retrieve is about 200).
It is entirely possible that this has been fixed in a recent scripts update .. this server's Ferret scripts were current as of (at least) 6/11/2008.
For a request: http://porter.pmel.noaa.gov:8580/OCDMS/ProductServer.do?xml=%3C%3Fxml+version%3D%221.0%22%3F%3E%3ClasRequest+package%3D%22%22+href%3D%22file%3Alas.xml%22+%3E%3Clink+match%3D%22%2Flasdata%2Foperations%2Foperation%5B%40ID%3D%27OCDMS_interactive_plot%27%5D%22+%2F%3E%3Cproperties+%3E%3Cferret+%3E%3Cview+%3Exy%3C%2Fview%3E%3Cformat+%3Egif%3C%2Fformat%3E%3COCDMS_palette+%3Erainbow%3C%2FOCDMS_palette%3E%3Cdeg_min_sec+%3Edefault%3C%2Fdeg_min_sec%3E%3Cmargins+%3Edefault%3C%2Fmargins%3E%3Cpoly_levels+%3E%3C%2Fpoly_levels%3E%3Cset_aspect+%3Edefault%3C%2Fset_aspect%3E%3Csize+%3E0.5%3C%2Fsize%3E%3Cuse_graticules+%3Edefault%3C%2Fuse_graticules%3E%3C%2Fferret%3E%3C%2Fproperties%3E%3Cargs+%3E%3Cconstraint+type%3D%22text%22+%3E%3Cv+%3Esubsampling%3C%2Fv%3E%3Cv+%3E%3D%3C%2Fv%3E%3Cv+%3Edata_24hourly%3C%2Fv%3E%3C%2Fconstraint%3E%3Clink+match%3D%22%2Flasdata%2Fdatasets%2FSOfCO2%2Fvariables%2Fatm_press%22+%2F%3E%3Cregion+%3E%3Crange+low%3D%22-178.0%22+type%3D%22x%22+high%3D%22-130.0%22+%2F%3E%3Crange+low%3D%22-6.0%22+type%3D%22y%22+high%3D%2228.0%22+%2F%3E%3Crange+low%3D%2217-Nov-1968+00%3A00%3A00%22+type%3D%22t%22+high%3D%2206-Nov-2008+00%3A00%3A00%22+%2F%3E%3C%2Fregion%3E%3C%2Fargs%3E%3C%2FlasRequest%3E&JSESSIONID=2DFF7A8F790EF98A15573F4753E8A2F6
The full debug output is as follows:
Migrated-From: http://dunkel.pmel.noaa.gov/trac/las/ticket/531