[Thread Prev][Thread Next][Index]

[las_users] still a las problemm



at lamm@xxxxxxxxxxxxx

Woops, I see my last post was responded to but even
with the correction and even after making
sure my environment variables are set
right it still does not work.  

I now get the error message:

------

LAS Error
The following error message was received from LAS:

Adding an acceptable error string: "*** NOTE: ".
        NOAA/PMEL TMAP
        FERRET v6  
        Linux(g77) 2.4.21-32 - 08/23/06
         3-May-07 18:12     

yes? cancel mode verify
yes? cancel mode interp
yes? define symbol mark_grid = default
yes? define symbol image_format = default
yes? canc data/all
yes? go std_initialize "http://gw550-3.coaps.fsu.edu/thredds/dodsC/eee";
"1" "1" "covice"
 **netCDF error
             OPeND(OPeNDAP/netCDF Error code 1001)
             Data set: http://gw550-3.coaps.fsu.edu/thredds/dodsC/eee
set data "http://gw550-3.coaps.fsu.edu/thredds/dodsC/eee";
Command file, command group, or REPEAT execution aborted

Content-disposition: inline; filename=LASoutput.html Content-length:
2396 Content-Type: text/html; charset=ISO-885

-------

At this
point, I have my root environment set where I can
as root, go by hand and get beyond the the 

go std_initialize "http://gw550-3.coaps.fsu.edu/thredds/dodsC/eee"; "1"
"1" "covice"

without error.
But when the thing is run through las where it
calls ferret I get that error message.  I went and
said ./configure to make sure server/Ferret_configure.pl got run again
and I have
every environment variable set as I do for root.  It still does not
work.
Does anyone know what error code 1001 means?
Also, is there a way of writing out what my environment variables are as
it runs
on las or get ferret to write out more info?  I wonder where las stores
the data
it gets from the thredds server to give to ferret.  Maybe ferret can't
read that
directory?  Any advice at all?  Thanks.




[Thread Prev][Thread Next][Index]


Contact Us
Dept of Commerce / NOAA / OAR / PMEL / TMAP

Privacy Policy | Disclaimer | Accessibility Statement