SQL2DBinaryWaveToTextWave and TextWave format
Lauri
But now I would like to be able to read the data also with PHP web interface when there is no access to Igor, and now the previous design decisions don't feel that clever. The problem is with the TextWave format, which should be converted to readable form without using Igor (i.e. SQLTextWaveTo2DBinaryWave commands). Is this TextWave format unique Igor thing? Are there means to get a grip on this conversion?
Igor Pro Folder\Technical Notes\Igor Tech Notes\TN003 Igor binary format
already?
This documents the Igor binary format. Although I don't know if this is the format used by the SQL* operations.
November 11, 2013 at 12:17 am - Permalink
So what is stored in the database is raw data. For example, if your 2D wave is 5 rows by 3 columns, single-precision floating point, then each record in the database will consist of 20 bytes (5 rows by 4 bytes per single-precision floating point value).
When you read it back into Igor using SQLTextWaveTo2DBinaryWave, Igor creates as 2D wave of type unsigned byte. You then must redimension it to the correct data type. This is explained in the help for SQLTextWaveTo2DBinaryWave. This is analogous to what you need to do in PHP - read a record as unsigned byte data and then reinterpret it as whatever data type it really is.
November 11, 2013 at 09:06 am - Permalink
November 12, 2013 at 07:45 am - Permalink