-
Notifications
You must be signed in to change notification settings - Fork 3
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
NAS-friendly extraction #322
Comments
List STC, to accommodate these changes we'll need to make the following adjustments:
This is assuming that we need explicit separation of proficient and deficient channels. I'm not sure if integration over |
This issue may or may not be dependent on #313. If multiple people are doing a run in the immediate future, we might be able to wait until we fully test the intermediate callbacks. |
Closing this issue for now, will reopen once someone chooses to figure out which channels need specific mass ranges. We'll need to define custom panels for this. |
Is your feature request related to a problem? Please describe.
The current practice of storing all the bin files is likely not necessary for the long term. In order to ensure everyone is confident that they can remove their bin files after a year, we'll want to have extracted all potentially relevant information from all bin files before we delete them.
Describe the solution you'd like
We'll want to extract the mass-proficient (x+0.3) in addition to our current deficient (x-0.3) setup. In addition, we'll want to extract all potentially relevant antibody/naturally abundant channels. We'll then need to decide how we handle the proficient and deficient copies of each channel so that rosetta and normalization work as expected.
The text was updated successfully, but these errors were encountered: