From: Matt C. <mat...@gm...> - 2013-10-24 17:31:01
|
Hi Chris, I just committed the fix for this. Thanks for persevering. :) I wish you OpenMS guys would wrap up your semantic validator in a statically linked executable either for Linux or Windows and then we could automatically run it with our continuous integration tests on TeamCity. Last I checked the validator wasn't easy to separate from the rest of OpenMS... but I admit that was a while ago. Thanks, -Matt On 10/23/2013 8:07 AM, Chris Bielow wrote: > > Dear PWiz team, > > I recently bugged you with a constant neutral loss issue, which was solved very quickly. Thanks again! > > Now that I’m fixing some loose ends on the pipeline which uses this data I came across an > inconsistency which I thought you should be aware of: > > [Term] > > id: MS:1000803 > > name: analyzer scan offset > > def: "Offset between two analyzers in a constant neutral loss or neutral gain scan. The value > corresponds to the neutral loss or neutral gain value." [PSI:MS] > > xref: value-type:xsd\:float "The allowed value-type for this CV term." > > is_a: MS:1000503 ! scan attribute > > relationship: has_units MS:1000040 ! m/z > > Is currently written by msconvert as child of “<spectrum>”, not “<scan>”. > > This currently prevents OpenMS from reading the value correctly, so that I have to maintain a > local workaround. > > Can this be fixed?! > > Cheers > > Chris > |