From: Matthew C. <mat...@gm...> - 2012-05-30 19:57:54
|
What do you want for Agilent/Bruker/Waters data? The .d and .raw directory name? On 5/30/2012 1:56 PM, Brendan MacLean wrote: > I would really prefer to have the full source file name that the MGF came from. In most existing > cases, I will be able to show that to the user in Skyline. I actually still think we should just > move to comma separated fields in TITLE, and let people adapt. Once they do adapt, we will be able > to add more comma separated fields in the future, if need be. Just add a flag for MSConvert and a > checkbox for MSConvertGUI that allows people to get the legacy behavior, which should not remain the > default forever, simply because it was the first thing we ever came up with. Ideally the number of > people relying on this now is still small compared to what it can become. Let's move toward a more > flexible format (comma separated <name>: <value> pairs) now. > > People managing pipelines generally will be a lot less affected by needing to add a new flag or fix > their code to handle comma separated properties that naive users looking for out of the box solutions. > > On Wed, May 30, 2012 at 11:40 AM, Matthew Chambers <mat...@gm... > <mailto:mat...@gm...>> wrote: > > Compatibility is more important in the command-line version which is infinitely more likely to be > included in an automated pipeline. So that's why the change can't go in Serializer_MGF. The checkbox > for "TPP compatibility" is still sounding like the best option, defaulting to on. > > Brendan, you said you were going to adjust your parser to work with the old basename.1.1.2 format; > does that mean I can keep to that format with "TPP compatibility" mode? > > -Matt |