-
Notifications
You must be signed in to change notification settings - Fork 38
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
Remove EXTRACTPSMFEATURES/IDScoreswitcher from workflow #448
Comments
Also remove IDScoreswitcher. I think @timosachsenberg merged my simplification changes |
I defnitely merged also some IDScoreSwitcher changes but I did not test it in the context of quantMS. I think it is a valuable change but should be done with two PRs that are each tested on some small data. |
What about changing all the tests in singularity and docker to point to OpenMS Dev. Which we sync the test and new deployments and changes in OpenMS with quantms more clearly-tidy. ? |
Related to this topic, we have one flag called |
We could remove this parameter and the corresponding modules if we make sure always use the Percolator probability. But I don't see any harm in leaving it there. I don't know if any other users use it, at least we |
No harm, but confusing if is always used with same value. |
Fine with me. Percolator will not work for very small data though. |
How small are we talking here? |
Hard to say. @timosachsenberg knows better. |
Ok, quantms is not designed for that anyway. I haven't seen any msruns with less that 1k psms. |
Yeah maybe 400 would still work. |
If people don't use it really, it should be here unless someone needs it, BTW, the pipeline becomes more complex for something that hardly happens. BTW, @timosachsenberg @jpfeuffer @daichengxin The PR removing |
Description of feature
In the latest OpenMS (dev) version, the FeatureExtraction process happens within each Search engine adapter MSGFAdapter, SAGEAdapter, etc. We don't have to rerun this step for every Search engine, then this step can be removed it.
Thoughts @timosachsenberg @jpfeuffer before starting.
The text was updated successfully, but these errors were encountered: