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

improve manual range picking n fix simulation of diagonal peaks in COSY prediction #3308

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

jobo322
Copy link
Member

@jobo322 jobo322 commented Dec 3, 2024

  • fix the simulation of the peaks in the diagonal in COSY predicted spectra.
  • improve auto-processing 2D raw data, apodization
  • improve/fix the multiplicity determination by multiplet-analysis in manual range picking:
    • by phase the selected range data before analyze the multiplet
    • reduce criteria value for the selection of J coupling

@jobo322 jobo322 linked an issue Dec 3, 2024 that may be closed by this pull request
@jobo322
Copy link
Member Author

jobo322 commented Dec 3, 2024

@lpatiny should we allow the prediction of COSY with cross-peaks with a path length of 4 bonds as max value?

@jobo322 jobo322 changed the title 3307 manual range picking returns wrong multiplicity for quadruplet improve manual range picking n fix simulation of diagonal peaks in COSY prediction Dec 3, 2024
Copy link

cloudflare-workers-and-pages bot commented Dec 3, 2024

Deploying nmrium with  Cloudflare Pages  Cloudflare Pages

Latest commit: 41dca64
Status:🚫  Build failed.

View logs

@lpatiny
Copy link
Member

lpatiny commented Dec 4, 2024

@lpatiny should we allow the prediction of COSY with cross-peaks with a path length of 4 bonds as max value?

No we should not. But we have the couplings coming back from the prediction so we should check from the result if there are some couplings or not. I would put a threshold of 1.5Hz in order to display the cosy coupling or not.

So we should not simply use 2J or 3J anymore but use the result from the prediction.

@jobo322 jobo322 force-pushed the 3307-manual-range-picking-returns-wrong-multiplicity-for-quadruplet branch from 5716ff7 to 0dae656 Compare December 9, 2024 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

manual range picking returns wrong multiplicity for quadruplet
2 participants