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

LFQProfiler: Transfer FASTA databases from processing workflow to consensus workflow #6

Open
hannesveit opened this issue Jul 1, 2016 · 0 comments
Assignees

Comments

@hannesveit
Copy link
Contributor

hannesveit commented Jul 1, 2016

Ideally, we would find a way to access the file names of the FASTA databases that were used by Sequest HT in the processing step and use the same databases for the LFQProfiler consensus step, instead of asking the user to select the same FASTA databases again.

This is a bit less straightforward than one might think at first glance:

  • At the moment, our only officially supported processing workflow is the one that includes Sequest HT. But in principle, the search engine is interchangeable. We would thus have to find out which node of the processing workflow was the search engine node that produced the PSMs.
  • If the consensus step is a multi consensus step combining the results of several processing workflows, these processing workflows could (in theory) have used different fasta databases. Although there is probably no scenario in which it would make sense to combine processing results that were searched against different sequence databases, we would have to deal with it. In this case we would probably want to use the union of all FASTA files used in any of the processing workflows.
@hannesveit hannesveit added this to the Release 2.0.3 milestone Jul 1, 2016
@hannesveit hannesveit self-assigned this Jul 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant