[Thread Prev][Thread Next][Index]
"ASCII table" output problem
Hi all!
Happy New Year!
I have installed the insitu data example that comes with LAS and I have been
modifying it to work with my database.
I would say that 75% of it work. I guess the other 25% needs a bit of
tweaking.
First, I needed to download etopo5.cdf to get some of the ferret operations
to work.
Now I am trying to get the "ASCII output" to work.
Whatever "view" I select, I always get the same error:
-----------------------------------------------------------------
LAS Error
The following error message was received from LAS:
Died at ../xml/perl/LAS/Server.pm line 1046.
------------------------------------------------------------------
I pulled the following error message out of the LAS debug file:
--------------------------------------------------------------------------------------------------------------
--- Returning from: LAS::Server::Ferret::accessDatabase
FER_GO=custom custom jnls jnls/insitu jnls/section . . /usr/local/ferret/go
/usr/local/ferret/examples /usr/local/ferret/contrib
Starting:/usr/local/ferret/bin/ferret -gif -server
Got reply: NOAA/PMEL TMAP
FERRET v5.70
Linux(g77) 2.4.20 - 06/28/04
3-Jan-05 14:31
yes?
Sent command: cancel mode verify
Got reply: yes?
Sent command: cancel mode interp
Got reply: yes?
Sent command: define symbol timeout = 3600
Got reply: yes?
Sent command: canc data/all
Got reply: yes?
Sent command: go std_initialize "output/ba1b7d189c61089565352b73ee60cf4f.nc"
"1" "1" "sal_ctd"
Got reply: yes?
LAS::Server::Handler::run(): 0.059435 secs to perform all 'preExecute'
activities (database access and parsing)
--- Calling: LAS::Server::Ferret::insitu_data
killing...Waiting for program to exit...
program exited...
--------------------------------------------------------------------------------------------------------------
The insitu_data subroutine in the insitu.pl looks fine to me.
Any ideas?
Thanks a lot!
Jerome.
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement