Re: [Psidev-ms-dev] use case: FT transient data

[Darren K. <dke...@ya...>]

> How does that strike you? Does the transient intensity array not have an
> X-axis to go with the intensities?


Looks good.  The name "primaryArrayLength" may suggest something beyond 
"defaultArrayLength" or just "arrayLength".  But I'm happy with any of 
the names.

Thermo transients assume a regularly spaced time axis, but I could 
imagine transient data being encoded with time samples.


Darren




Eric Deutsch wrote:
> Okay, well, your example is compels me to think that is not the way we
> should do it.  It seems like the most reasonable alternative is to go
> with the previous suggestion of allowing overriding of the arrayLength:
>
> <spectrum id="S19" index="1" primaryArrayLength="13020">
> 	<spectrumDescription>
> 		...
> 	</spectrumDescription>
> 	<binaryDataArray encodedLength="5433"
> dataProcessingRef="Xcalibur Processing">
> 		<cvParam cvLabel="MS" accession="MS:1000514" name="m/z
> array" value=""/>
> 		...
> 		<binary>AAAAwDsGeUAAAAD...</binary>
> 	</binaryDataArray>
> 	<binaryDataArray encodedLength="4892">
> 		<cvParam cvLabel="MS" accession="MS:1000515"
> name="intensity array" value=""/>
> 		...
> 		<binary>AAAAAIBJxk...</binary>
> 	</binaryDataArray>
> 	<binaryDataArray encodedLength="23445" arrayLength="56343">
> 		<cvParam cvLabel="MS" accession="MS:100xxxx"
> name="transient intensity array" value=""/>
> 		...
> 		<binary>AAAAAIBJxk...</binary>
> 	</binaryDataArray>
> </spectrum>
>
> How does that strike you? Does the transient intensity array not have an
> X-axis to go with the intensities?
>
> Eric
>
>
>
>