by
TyDy76 » Fri Oct 01, 2021 12:01 pm
I have just noticed a glitch in the new version of TargetLynx that we have been installing on our new Windows 10 computers. If you use the PEAK DELETE or DELETE ALL PEAKS function it causes some other peaks to no longer be quantified or identified correctly. When it happens it is not necessarily obvious, but has a high level of potential to produce incorrect data.
This is a glitch that existed in older versions of MassLynx, but was fixed years ago in TargetLynx 4.1. It’s back.
Anyone know how to fix this issue. As of now our solution is to "delete" peaks by manually integrating the start/end points together which is ridiculously tedious.
Cheers