Re: [las_users] LAS Animation error response

[Ansley Manke <ansley.b.manke@xxxxxxxx>]

Hi Kacie,
Both this issue with animations and your question last week about Hovmuller plots with datasets having long time axes are running into an error in the NetCDF libraries when we try to read  strided (decimated) grids of data.

I've tested these kinds of read operations on your datasets with with the various versions of NetCDF, and none of them return a correct result.  I have made a report to the authors of the NetCDF library.

I see that your LAS is currently running version 7.3.  When we do have a fix for this, it will require an upgrade to your LAS, to the newer LAS Version 8.

Ansley

On 5/1/2013 10:17 AM, Ansley Manke wrote:

Hi Kacie,
This is very likely the same issue that you wrote about last week.  Again, we're asking for a portion of the data, in this case a number of time steps spaced across the time region you have asked for.  The first step of making an animation is to get the range of the data represented, so that the color scale can be the same across all the frames of the animation.  Once that's done, we can just read one timestep at a time and make the image.

I'll try to get back to you in the next couple of days.

Ansley

On 4/30/2013 2:47 PM, Shelton, Kacie E (398C) wrote:

Hi.

 

We are having issues with LAS animation, and it nominally appears to be the same or similar error with our datasets that are very large (either volume or time series). 

 

The behavior:  we can only request animation for a very small area for only a few days.  If an error returns, we need to close the tab, return to the main LAS window, and click on Animation again – basically trial and error to find how many granules it will animate in one request.  6 granules is the limit for the dataset GHRSST AVHRR_AMSR_OI.  The error is returned before the “Stop Downloading” button appears. 

 

Cached data cleared from memory

**netCDF error

             NetCDF: Malformed or inaccessible DAP DATADDS (OPeNDAP/netCDF Error code -73)

 

I am attaching an image of the error, and a rtf of the long error report. 

 

Any idea what is going on?

 

Thank you,

Kacie