Skip to content

Issues: AdityaSavara/MSRESOLVE

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.

Sign up for GitHub

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

21 Open 12 Closed
21 Open 12 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Tuning Correction Improvements enhancement New feature or request
#277 opened Nov 10, 2021 by AdityaSavara
4 of 8 tasks
createMSDataObject and readMSDataFromFile functions should be made to read Experiment Data from file enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
#269 opened Nov 1, 2021 by AdityaSavara
1
Tuning Correction for tuningCorrectionIntensity (Correction Values) should be checked for cases where pattern max changes
#268 opened Oct 29, 2021 by AdityaSavara
exporting improvements (reference pattern and other things) enhancement New feature or request
#267 opened Oct 29, 2021 by AdityaSavara
8 tasks
Reference extraction uncertainties don't get propagated to the standardized reference pattern
#237 opened Jun 30, 2020 by AdityaSavara
Pre-processed data masses should have a version with an abscissa that matches ExperimentData.mass_fragment_numbers and RawSignalsSimulation good first issue Good for newcomers help wanted Extra attention is needed
#228 opened May 17, 2020 by AdityaSavara
clarify / for choices for implicitSLScorrection compatibilities
#227 opened May 17, 2020 by AdityaSavara
collectedFileUncertainties should have UserInput validiation and vectorization help wanted Extra attention is needed
#225 opened Apr 18, 2020 by AdityaSavara
Add a try statement and warning for smoothing good first issue Good for newcomers help wanted Extra attention is needed
#222 opened Feb 28, 2020 by AdityaSavara
Add back in uncertainties and signals from filtered peaks for SLSUnique enhancement New feature or request help wanted Extra attention is needed
#221 opened Feb 13, 2020 by AdityaSavara
1
making uncertainties compatible with more choices enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
#220 opened Feb 13, 2020 by AdityaSavara
try statement inside userInputValidityFunctions.py good first issue Good for newcomers wontfix This will not be worked on
#217 opened Feb 13, 2020 by AdityaSavara
manual should say "concentration relative to CO" for matrix
#214 opened Feb 6, 2020 by AdityaSavara
Logical error in negative analyzer
#206 opened Jan 16, 2020 by AdityaSavara
making SLS more efficient by "gaussian elimination"
#205 opened Dec 17, 2019 by AdityaSavara
Strange inequality in code: probably hardcoded filtering to be removed bug Something isn't working invalid This doesn't seem right
#203 opened Sep 27, 2019 by AdityaSavara
1
export scaled concentrations and also resolved concentrations graphs wontfix This will not be worked on
#202 opened Sep 26, 2019 by AdityaSavara
1
making reading of data more robust against blanks wontfix This will not be worked on
#201 opened Sep 26, 2019 by AdityaSavara
1
specifications for Brute should be documented help wanted Extra attention is needed
#198 opened Jul 22, 2019 by AdityaSavara
add feature of ionization correction factor & make concentration scaling factors a list enhancement New feature or request
#138 opened Aug 14, 2018 by AdityaSavara
@aroger34
2
preprocessing "load" option is not working. enhancement New feature or request help wanted Extra attention is needed wontfix This will not be worked on
#128 opened Aug 10, 2018 by AdityaSavara
ProTip! Follow long discussions with comments:>50.