Dear David and Greg, thanks for your answers.
I still don't see the sense in having the "base_name" constraint,
though. The basic question for me is, what would break without the
constraint? Because as far as I can tell now, it just prevents a
sensible use case - searching the same mzXML file with
David, just a quick reply to part of your message. Normally, I make a
directory for an experiment and I will process the mascot, sequest,
and possibly X!Tandem data from each mzXML file in the same directory. I do
append the name of the search to the TPP files, so I can determine which
search engin
I will try to reason this through using trying to think from the
original authors point of view. The idea is that different searches
of the same data would happen in separate directories and the
base_name (full path to the data file) would identify one search of an
mzXML file representing one msms
OK I take that back. I see where the unique constraint is listed. I
will have to consider your questions further.
-David
On Fri, Nov 20, 2009 at 10:27 AM, David Shteynberg
wrote:
> Hi Hendrik,
>
> The element msms_pipeline_analysis/msms_run_summary has an attribute
> base_name to specify the p
Hi Hendrik,
The element msms_pipeline_analysis/msms_run_summary has an attribute
base_name to specify the path to the datafile. In case the searched
file specified is different from the original data file there is
another entry in the element
msms_pipeline_analysis/msms_run_summary/search_summary
Hi Hendrik, I think we need to get an authoritative answer from David on
this one. And he is currently traveling in the Land of the Finns. We will
let/ask him to answer when he is next able.
Regards,
Eric
> From: spctools-discuss@googlegroups.com [mailto:spctools-
> disc...@googlegroups.com] O
