Re: "ASCII table" output problem

[Joe McLean <joe.mclean@xxxxxxxx>]

Hi Jerome,
What version of LAS are you using?
Apologies for the uninformative error messages.  I have run into similar 
sudden ends when the Perl NetCDF interface (used in insitu.pl) fails.  
Try using the data from output/ba1b7d189c61089565352b73ee60cf4f.nc in a 
command line Ferret session.  Do the values of the various axis 
variables and fields look like they make sense?  Is it possible that 
your modifications to the DB access driver incorrectly write data to the 
NetCDF file?

insitu.pl tries to read the data into perl arrays with the following 
commands:
-----------
 my $prof_id = $cdf->getVariable("PROF_ID");
 my $xax = $cdf->getVariable("xax");
 my $yax = $cdf->getVariable("yax");
 my $zax = $cdf->getVariable("zax");
 my $tax = $cdf->getVariable("tax");

# Get all requested variables
 foreach my $var (@varnames) {
   $varObjects{$var} = $cdf->getVariable($var);
 }
[...]
# Get data for internal variables we know we'll need
 my @prof_ids  = $prof_id->getData([0],[$size]);
 my @lons = $xax->getData([0],[$size]);
 my @lats = $yax->getData([0],[$size]);
 my @depths = $zax->getData([0],[$size]);
 my @hours = $tax->getData([0],[$size]);
-------------

If any of these variables are missing, Perl NetCDF calls might fail and 
handle the error incorrectly.  Let me know what you find.

Joe
-----------------------------------

Jerome King wrote:

> 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.