[Thread Prev][Thread Next][Index]
Problems setting up insitu data access
Hello fellow LAS users,
I'm working on serving non-gridded data from a database and as a first step I've been trying to setup the insitu dataset that comes with the LAS distribution. I'm using LAS version 6.4.1 on a itanium 64 running Redhat 9. I went through the 'make insitu' process and everything seemed to install fine. However, when I try to get any sort of output from the the insitu dataset I get an error.
With the following options selected:
Select view: Longitude-Depth Sections
Select output: ASCII table
Select region: Full Region
Select time range: 01 Jan 1986 to 31 Dec 1988
Select depth range: 0 to 2000
Select Constraints: None
Rather than getting the expected ASCII table, I receive the following error:
LAS Error
The following error message was received from LAS:
Can't find match target '/lasdata/operations/insitu_data' at 'insitu_data' at ../xml/perl/LAS.pm line 613
Depending on the selected view and selected output, I get other similar errors:
LAS Error
The following error message was received from LAS:
Can't find match target '/lasdata/operations/insitu_data_cdf' at 'insitu_data_cdf' at ../xml/perl/LAS.pm line 613
LAS Error
The following error message was received from LAS:
Can't find match target '/lasdata/operations/insitu_meta_xy' at 'insitu_meta_xy' at ../xml/perl/LAS.pm line 613
Looks like I've got some sort of path configuration problem, but I can't find any documentation on how to set up the lasdata path. Additionally, I can't find an "operations" directory within my LAS installation. I see a .jnl file named insitu_meta_xy in $LASHOME/server/jnls/insitu/ is this what LAS is looking for? I don't see any files named insitu_data or insitu_data_cdf anywhere in the $LASHOME directory.
Any thoughts, suggestions?
Thanks,
Andrew
Andrew C. Chase
Software Engineer
Monterey Bay Aquarium Research Institute
(831) 775-1865 :: Work
(858) 349-3443 :: Cell
[Thread Prev][Thread Next][Index]
Dept of Commerce /
NOAA /
OAR /
PMEL /
TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement