Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

for QC/QA, analysis regions should be stored on the chromatogram #72

Open
lorenzgerber opened this issue Oct 15, 2019 · 7 comments
Open
Labels
api-change Marks an issue that would most-likeley requires an API change enhancement New feature or request user feedback Feedback from Users
Milestone

Comments

@lorenzgerber
Copy link
Contributor

If a processor/filter etc. is run on a zoomed chromatogram, the information of the analysis regions should be stored on the chromatogram for QC/QA reasons. Else, it will not be possible to reproduce which modifications where made to which part of the chromatogram.

@laeubi laeubi added api-change Marks an issue that would most-likeley requires an API change enhancement New feature or request user feedback Feedback from Users labels Oct 15, 2019
@laeubi
Copy link
Member

laeubi commented Oct 15, 2019

We use a similar approach in the NMR part, each processing step is recorded with

  • time
  • processor
  • settings

so it is possible to exactly see what was done to get the final result.

@laeubi
Copy link
Member

laeubi commented Oct 15, 2019

grafik

@eselmeister
Copy link
Contributor

eselmeister commented Oct 15, 2019 via email

@lorenzgerber
Copy link
Contributor Author

I don't think we need the flipping back and forth feature for QC/QA in Chromatogram. It would be enough to have the region where a certain filter or processor was applied registered/stored somewhere.

@kerner1000
Copy link
Contributor

We have been discussing something similar for NMR spectra.
it should be possible to persist a spectra, chromatogram, ... selection. Ideally, this would also be stored inside the ocb file.
This could also be used for things like bookmarking or copy a selection to a new chromatogram.

@eselmeister
Copy link
Contributor

eselmeister commented Oct 17, 2019 via email

@lorenzgerber
Copy link
Contributor Author

From what I can see in the source, the edit history is only a string based log, not really suitable to store numeric information that shall be reusable/accessible from other classes in a modular way. However, range selections stored in an appropriate class could certainly also trigger an entry in the edit history.

@laeubi laeubi added this to the 0.9.x milestone Mar 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-change Marks an issue that would most-likeley requires an API change enhancement New feature or request user feedback Feedback from Users
Projects
None yet
Development

No branches or pull requests

4 participants