ElucidataInc / ElMaven

LC-MS data processing tool for large-scale metabolomics experiments.
https://resources.elucidata.io/elmaven/
GNU General Public License v2.0
85 stars 52 forks source link

Edits are not saved in Peak Editor for certain compounds #1393

Closed kehj215 closed 3 years ago

kehj215 commented 3 years ago

Describe the bug When I'm working through a batch, certain compounds that definitely, absolutely have a peak are not integrated. When I manually select the peak in the peak editor, change the thresholding, alter the integration window, then click apply edits, the edits don't save. This only happens for certain compounds- others in my batch are totally unaffected.

To Reproduce Steps to reproduce the behavior:

  1. Bookmark a compound
  2. Click peak editor
  3. press "C" to create a peak
  4. change threshold and RT window to encompass peak
  5. click apply edits
  6. Click peak editor again, see that no edits have been applied.

Expected behavior Edits to my peak I created are saved after clicking "apply edits"

Screenshots attached.

System:

Additional context I am totally new to El Maven and trying to learn so it could very well be that I am the one causing the issue, however because I am able to apply edits for other peaks I'm less inclined to think so.

Screen Shot 2021-03-30 at 11 35 38 AM Screen Shot 2021-03-30 at 11 35 57 AM Screen Shot 2021-03-30 at 11 36 20 AM
saif-el commented 3 years ago

@kehj215 I suspect this may not be a bug. Looking at this peak, it seems to me that it is likely being classified as a "bad" peak and being discarded even if you manually integrate it and "Apply edits".

To check whether this is the actual issue, you can turn down your quality threshold in "Peak filtering" settings tab: Screenshot 2021-03-31 at 11 12 16 AM

After doing that, if you are still unable to get these to show up after editing integration, then this is something we should look into.

saif-el commented 3 years ago

@kehj215 One more thing, you might have to re-integrate the entire peak-group, after reducing quality thresholds. This is because once a peak-group is created, it gets frozen with its own copy of settings - which for your original peak-group would have the original quality threshold and changing the global peak-filtering settings will have no effect on its peak-editing.

You can get a log of what settings a peak-group has been integrated with by selecting that peak-group in the table and clicking the "Settings log" button:

Screenshot 2021-03-31 at 11 31 32 AM

kehj215 commented 3 years ago

Unfortunately my minimum peak quality was already set to 0 so it doesn't look like that's it.

I'm also realizing that if I apply edits for a peak that is recognized, that also deletes the peak.

saif-el commented 3 years ago

In that case, would it be possible to share that one sample's mzML/mzXML file over email? This will allow us to narrow down on the issue faster than making guesses.

kehj215 commented 3 years ago

Yup you got it! Thanks!

saif-el commented 3 years ago

@kehj215 The fix has been deployed. You can use the same link to download a newer build, or wait for it land in the main v0.12.1 release (which we are trying to send out within this month).

kehj215 commented 3 years ago

Great! I downloaded the newer build and it's working. Can't wait for the main release. Thanks so much!