Re: [proteowizard-developer] mzidconvert?

[Matthew C. <mat...@gm...>]

Why ms instead of mz? I'm afraid that people would mix up msconvert with msidconvert. Yikes, somebody even mixed up mzWiff with msconvert. :P

-Matt


On 1/11/2011 1:32 PM, Joe Slagel wrote:
> +1 for msidconvert
>
> On Tue, Jan 11, 2011 at 11:28 AM, Jarrett Egertson <jeg...@gm... <mailto:jeg...@gm...>> wrote:
>
>     Matt,
>
>           This would be _great_, +1 for 'msidconvert'.
>
>     -Jarrett
>
>
>     On Tue, Jan 11, 2011 at 11:02 AM, Matthew Chambers <mat...@gm... <mailto:mat...@gm...>> wrote:
>
>         Since I added read/write serialization for pepXML, I'd like to create an msconvert-like application (basically just copying it and renaming some
>         variables :) )
>         for transcoding identification formats. Is mzidconvert a good name for it? Or idconvert? Or something else?
>
>         At first it'll just support mzIdentML, and pepXML, and Mascot DAT (although I haven't tested the latter yet), but we can add Sequest SRF, .OUT, SQT, and
>         TandemXML at some point. Basically, my goal for the MzIdentML support is to duplicate the Algorithm2XML converters in TPP (and then some). Like with the
>         MSData
>         formats, my goal is for identification applications using pwiz to be able to read these formats as if they were MzIdentML files. Unfortunately there's a lot
>         more parameter wrangling with this than in MSData, but since I plan to use this capability in IDPicker I have an interest in making sure it works.
>
>         Converting from DAT to pepXML almost certainly won't be as fast as Mascot2XML, but if I can read straight from DAT in the first place, it's probably a
>         net gain. :)
>
>         -Matt