It's probably emitting mzXML 3, which has a byteOrder attribute in the Peaks element.
On Wed, Feb 2, 2011 at 3:20 AM, dre <[email protected]> wrote: > Hey guys, > > No bugs here - I just have a question for the mzXML format experts. > I've been trying to learn about the format these days and I'm a little > bit stuck on the data encoding. The mzXML 2.1 specification states > that data should be encoded from IEEE float to Network binary to Base > 64, however when I decode the data I am able to retrieve proper > numbers without applying a network to host conversion. Wikipedia lists > network data as big endian, but from my results it would appear that > my ReAdW-generated mzXML file contains little-endian data encoded > directly into base 64 (so basically skipping the host to network > conversion step which should be required according to the > specification). Am I correct in this assessment or am I missing > something here? Any clarifications would help greatly. > > Thanks! > > Andrej > > -- > You received this message because you are subscribed to the Google Groups > "spctools-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/spctools-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en.
