Re: [udf-dlm-develop] present status

[Ed S. <es...@la...>]

Harald,

Thanks for your progress report.  I'm glad we're farther along.

  >% UDF_OPEN: Unrecognized sensor type, 16

I have a strooong hunch that this is a bug in the VIDF file.  

The "sensor type" has always, in my experience, been one of:

	0 (unsigned 8/16/32 bits)
	1 (signed  ditto)
	2 (float)

In fact, the VIDF "spec"[1] only documents up to 6.

There's a number that goes close by, though, which is (ta-dah) the
bit length indicator of whether it's 8, 16, or 32 bits.

I'll bet good money that the "16" you're seeing is intended to be
the bit length...

Have I mentioned recently my opinion that the PIDF/VIDF files are
unmaintainable?


  >2. I'm still in the process of cross-checking, but the data which I can 
read are
  >fine and the same as we expect from our level-zero data.

Yahoo!  I'm delighted to hear it!


  >3. Every data structure contains [START_AZ and STOP_AZ]

Yeah, I'm not too sure what they are.  They seem to be set when one
does a "read_drec()", but I don't know if I'm getting the dimensions
right.  Are they one scalar value per record?

Maybe these are valid only for certain instruments?  Certain "sensors"?
If anyone on this list has any knowledge of these, please let us know.

Also, I see preposterous values there too sometimes.  I don't know why.


  >4. When I read our WIC, SI12 and SI13 files I always get a
  >% Program caused arithmetic error: Floating overflow

Interesting.  I see it too.  Yes, it's probably related to the
matrix thingies... I'll investigate further, as time allows, and 
let you know.

Regards,
^E


 [1] http://pluto.space.swri.edu/~frio/VIDFPg/SenInfo.html