Initial ms1 scan of 1 peak

Open joewandy opened this issue 2 years ago • 1 comments

It appears that an initial MS1 scan of exactly 1 peak is always inserted at the start of a simulated run. I can't remember why we do this, but maybe it's something that can be removed now.

Jul 06 '23 12:07 joewandy

@joewandy I think the matching is built around this behaviour too... I might need to change things a bit if it's not like this on the real machine...

EDIT: Actually, it might be self-correcting with the resynchronisation... I don't think we're running any non-simulated comparisons involving the resynchronisation and I can't see any reason why one would run on the real machine without it, so I guess it might be fine?

Oct 13 '23 15:10 mcbrider5002