|
Hi Emanuele,
The Ferret script that runs inside LAS is doing several extra
things beyond what any of us would do in a Ferret session to make
a basic plot. In LAS for large grids like this, we do striding
for better performance; the plot isn't going to render a
resolution as high as 2500x750 and so the scripts calculate a
stride based on the pixel size of the plot rectangle that it is
going to draw. The scripts also do a number of things to remove
the many labels that Ferret would automatically draw on the plot
and instead gather that as the information that's going to go in
the annotation box at the top of the result page. It customizes
the colorbar and places it at the top of the plot.
So the plot that is being drawn is something more like this
script. Running this from the Ferret command line, you'll see the
behavior on the shade command.
use
http://giotto.casaccia.enea.it:8080/thredds/dodsC/path_MITO
set window/size=.83/aspect = 0.337:axis
define view/x=0:0.95/y=0:1 xspace
set view xspace
set axis/stride=10 jx
set axis/stride=4/offset=3 iy
let plot_var = 't'[z=-1:-1,t="16-jan-2018
00:00":"16-jan-2018 00:00",i=1:240,j=1:184]
define variable/title="longitude"/units=degrees xcoord
= lon[i=1:240,j=1:184]
define variable/title="latitude"/units=degrees ycoord
= lat[i=1:240,j=1:184]
shade/key=cont/trim/levels=v/modulo/set plot_var[d=1] ,
xcoord, ycoord
go reset_labels
go key_at_top
ppl shade
fill/levels/over/nolab plot_var[d=1] , xcoord, ycoord
This looks like a Ferret bug in Ferret v7.2. I'll write your
outside the LAS list with a couple of ideas for working around it
until we can get it fixed. (The more-recent Ferret release v7.3
does not fix it.)
Ansley
Dear LAS
users,
I've troubles using LAS 8.6.2 with my data.
The problem is that LAS image has a faulty region that Ferret plot
(made outside LAS) has not.
I've THREDDS serving my data at
http://giotto.casaccia.enea.it:8080/thredds/dodsC/path_MITO.html
If I use Ferret to SHADE such data I have no problem,
ferret -gif
NOAA/PMEL TMAP
FERRET v7.2 (optimized)
Linux 2.6.32-696.3.2.el6.x86_64 64-bit - 07/11/17
15-Jan-18 13:55
yes? use
http://giotto.casaccia.enea.it:8080/thredds/dodsC/path_MITO
*** NOTE: Axis coordinates are decreasing-ordered.
Reversing ordering for axis lev
yes? show data
currently SET data sets:
1>
http://giotto.casaccia.enea.it:8080/thredds/dodsC/path_MITO
(default)
name title I J K
L
LAT Latitude on Grid Center 1:2500 1:752 ...
...
LON Longitude on Grid Center 1:2500 1:752 ...
...
S Salinity 1:2500 1:752
1:100 1:109
T Temperature 1:2500 1:752
1:100 1:109
U U-Velocity 1:2500 1:752
1:100 1:109
V V-Velocity 1:2500 1:752
1:100 1:109
yes? shade/K=100/L=1 'T',LON,LAT
yes? frame/file=Ferret_image.gif
As you can see from the attached file Ferret_image.gif, the image
is nice, without any problem
But when I pass the same THREDDS to LAS at
http://giotto.casaccia.enea.it:8080/las/
I get a gif image which has a problem in the region
31<LAT<37 0<=LON<=9 (the yellow box) and also some
other problem nearby it
Please have a look at the attached file "Screenshot-2018-1-15 LAS
UI.png"
I verified it is not a MEMORY/SIZE problem (which I set to 99999)
Debugging LAS is a quite complex task thus I only ask for a hint.
For who wants to go deeper into the problem I attach the file
E2253A97F5022824FE3DF9B3E4E188E0_debug.txt which is produced by
LAS.
Dear LAS users,
thanks a lot for any help,
Regards,
Emanuele Lombardi
Rome, Italy
Here it follows some info about data:
cdo sinfo
http://giotto.casaccia.enea.it:8080/thredds/dodsC/path_MITO
File format : NetCDF
-1 : Institut Source Steptype Levels Num Points Num Dtype
: Parameter ID
1 : unknown unknown instant 100 1 1880000 1 F32
: -1
2 : unknown unknown instant 100 1 1880000 1 F32
: -2
3 : unknown unknown instant 100 1 1880000 1 F32
: -3
4 : unknown unknown instant 100 1 1880000 1 F32
: -4
Grid coordinates :
1 : curvilinear : points=1880000 (2500x752)
lon : -8.800445 to 41.92491
degrees_east
lat : 30.18093 to 47.27765
degrees_north
Vertical coordinates :
1 : generic : levels=100
lev : -1 to -5071.839 meters
Time coordinate : 109 steps
RefTime = 2018-01-01 00:00:00 Units = seconds Calendar =
standard
YYYY-MM-DD hh:mm:ss YYYY-MM-DD hh:mm:ss YYYY-MM-DD hh:mm:ss
YYYY-MM-DD hh:mm:ss
2018-01-14 00:00:00 2018-01-14 01:00:00 2018-01-14 02:00:00
2018-01-14 03:00:00
2018-01-14 04:00:00 2018-01-14 05:00:00 2018-01-14 06:00:00
2018-01-14 07:00:00
2018-01-14 08:00:00 2018-01-14 09:00:00 2018-01-14 10:00:00
2018-01-14 11:00:00
2018-01-14 12:00:00 2018-01-14 13:00:00 2018-01-14 14:00:00
2018-01-14 15:00:00
2018-01-14 16:00:00 2018-01-14 17:00:00 2018-01-14 18:00:00
2018-01-14 19:00:00
2018-01-14 20:00:00 2018-01-14 21:00:00 2018-01-14 22:00:00
2018-01-14 23:00:00
2018-01-15 00:00:00 2018-01-15 01:00:00 2018-01-15 02:00:00
2018-01-15 03:00:00
2018-01-15 04:00:00 2018-01-15 05:00:00 2018-01-15 06:00:00
2018-01-15 07:00:00
2018-01-15 08:00:00 2018-01-15 09:00:00 2018-01-15 10:00:00
2018-01-15 11:00:00
2018-01-15 12:00:00 2018-01-15 13:00:00 2018-01-15 14:00:00
2018-01-15 15:00:00
2018-01-15 16:00:00 2018-01-15 17:00:00 2018-01-15 18:00:00
2018-01-15 19:00:00
2018-01-15 20:00:00 2018-01-15 21:00:00 2018-01-15 22:00:00
2018-01-15 23:00:00
2018-01-16 00:00:00 2018-01-16 01:00:00 2018-01-16 02:00:00
2018-01-16 03:00:00
2018-01-16 04:00:00 2018-01-16 05:00:00 2018-01-16 06:00:00
2018-01-16 07:00:00
2018-01-16 08:00:00 2018-01-16 09:00:00 2018-01-16 10:00:00
2018-01-16 11:00:00
2018-01-16 12:00:00 2018-01-16 13:00:00 2018-01-16 14:00:00
2018-01-16 15:00:00
2018-01-16 16:00:00 2018-01-16 17:00:00 2018-01-16 18:00:00
2018-01-16 19:00:00
2018-01-16 20:00:00 2018-01-16 21:00:00 2018-01-16 22:00:00
2018-01-16 23:00:00
2018-01-17 00:00:00 2018-01-17 01:00:00 2018-01-17 02:00:00
2018-01-17 03:00:00
2018-01-17 04:00:00 2018-01-17 05:00:00 2018-01-17 06:00:00
2018-01-17 07:00:00
2018-01-17 08:00:00 2018-01-17 09:00:00 2018-01-17 10:00:00
2018-01-17 11:00:00
2018-01-17 12:00:00 2018-01-17 13:00:00 2018-01-17 14:00:00
2018-01-17 15:00:00
2018-01-17 16:00:00 2018-01-17 17:00:00 2018-01-17 18:00:00
2018-01-17 19:00:00
2018-01-17 20:00:00 2018-01-17 21:00:00 2018-01-17 22:00:00
2018-01-17 23:00:00
2018-01-18 00:00:00 2018-01-18 01:00:00 2018-01-18 02:00:00
2018-01-18 03:00:00
2018-01-18 04:00:00 2018-01-18 05:00:00 2018-01-18 06:00:00
2018-01-18 07:00:00
2018-01-18 08:00:00 2018-01-18 09:00:00 2018-01-18 10:00:00
2018-01-18 11:00:00
2018-01-18 12:00:00
cdo sinfo: Processed 4 variables over 109 timesteps ( 1.04s )
|