[Thread Prev][Thread Next][Index]

Re: [las_users] genLas.pl error! Can't add large number of datasets!!



Thanks, Jon,
 
I writed a simple perl to parse las.xml.
  #!/usr/bin/perl
  use XML::DOM;
  my $xmlFile = $ARGV[0];
  my $parser = new XML::DOM::Parser;
  my $doc = $parser->parsefile ($xmlFile);
  print "$doc\n";
It isn't work, too.
 
Is this a bug of XML::DOM::Parser module?
 
----- Original Message -----
To: cch
Sent: Tuesday, March 07, 2006 8:18 AM
Subject: Re: [las_users] genLas.pl error! Can't add large number of datasets!!

cch,

Do you really have 983+ separate datasets?  If some of these datasets are just separate timesteps in a 3D dataset then you can aggregate them together and then reference the aggregate as a single dataset.

You can aggregate multiple NetCDF slices using the THREDDS Data Server.


-- Jon

cch wrote:
Hi, all,
 
I try to trace the code,
and the error message is printed by LAS.pm at line 552.
  $self->{doc} = $parser->parsefile($fname) or croak "Can't parse $fname";
The reason is there is nothing returned from parsefile(), the $self->{doc} is undefined.
 
I use linux command 'xmlwf' to detect las.xml, it shows me the las.xml is well-form.
 
I dig out the max number of dataset xml files is 983,
if the number is larger than 983, LAS can't parse las.xml.
 
Please help me, thanks!!
 
 
 
>Hi, Jon.
>Thanks for you suggestion.
>I have tried this metohd.
>First, I complie helf of datasets like this:
>&dset1;
>&dset2;
>&dset3;
>&dset4;
><!--
>&dset5;
>&dset6;
>&dset7;
>&dset8;
>-->
>
>And it's ok.
>Then I complie another helf of datasets.
><!--
>&dset1;
>&dset2;
>&dset3;
>&dset4;
>-->
>&dset5;
>&dset6;
>&dset7;
>&dset8;
>
>It's ok, too.
>But when I complie all datasets, it wrong....
>
>Thanks for your help!!
 
 
cch,

My first thought is that one of your dataset configuration files must
not be well formed. The easiest way to look for this is to comment out
blocks of datasets in *las.xml* using XML comments. For instance, to
find out whether things will compile using only the first dataset you
can do this:

&dset1;
<!--
&dset2;
&dset3;
&dset4;
&dset5;
&dset6;
&dset7;
&dset8;
-->
 

How about when you include the first 4?, last 4?, ...

You'll quickly find the offending file and then be able to inspect it
for any errors.


-- Jon
--
cch


[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement