-
Notifications
You must be signed in to change notification settings - Fork 417
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
Running the annotation step does not work with the full samplesheet file described on the website or with the variantcalling.csv file generated by the pipeline in a previous step #949
Comments
See also #948 |
github-project-automation
bot
moved this to Todo (Hackathon General)
in nf-core Hackathon March 2023
Mar 21, 2023
Hi Mihaela! Is this working when just |
hm I am thinking about this issue. and it should probably fail: mutect2 is not an annotation tool, but it starts from |
Hi Friederike, no it doesn't. It requests that one provides the sex and if tumor or normal sample. Theoretically it requests the full input file as one would run the preprocessing and variant call step too.
…________________________________
Von: FriederikeHanssen ***@***.***>
Gesendet: Montag, 27. März 2023 17:25:46
An: nf-core/sarek
Cc: Mihaela Martis-Thiele; Author
Betreff: Re: [nf-core/sarek] Running the annotation step does not work with the full samplesheet file described on the website or with the variantcalling.csv file generated by the pipeline in a previous step (Issue #949)
Hi Mihaela! Is this working when just status?
—
Reply to this email directly, view it on GitHub<#949 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWZR5QRIQWZ2Z66SUUKQOODW6GWPVANCNFSM6AAAAAAVEJFIZA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Yes, mutect is not an annotation tool, but in this step I don't call it. I just make use of its output, which I want to annotate....
…________________________________
Von: FriederikeHanssen ***@***.***>
Gesendet: Montag, 27. März 2023 17:31:44
An: nf-core/sarek
Cc: Mihaela Martis-Thiele; Author
Betreff: Re: [nf-core/sarek] Running the annotation step does not work with the full samplesheet file described on the website or with the variantcalling.csv file generated by the pipeline in a previous step (Issue #949)
hm I am thinking about this issue. and it should probably fail: mutect2 is not an annotation tool, but it starts from --step annotate, so it should fail but for a different reason
—
Reply to this email directly, view it on GitHub<#949 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWZR5QXTWOLLWOXBFVOG5YDW6GXGBANCNFSM6AAAAAAVEJFIZA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Tool validation will now be skipped if |
Merged
9 tasks
github-project-automation
bot
moved this from In Progress
to Done
in nf-core Hackathon March 2023
May 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
Running only the annotation step using the csv file generated by the Sarek 3.1.2 pipeline in a previous run (variantcaller.csv) ends with the following error:
The sample-sheet only contains normal-samples, but the following tools, which were requested with "--tools", expect at least one tumor-sample : mutect2
The content of the variantcaller.csv corresponds to the full samplesheet described on the website and has the following format:
Solution: adding the columns sex and status to the input file (directly after the patient column) solves the problem
The documentation on the website needs to be adapted and the 2 columns added to the full samplesheet example.
This behavior is not consistent in all steps. If I run the pipeline from the beginning with the tools
--tools mutect2,strelka,vep
then the error does not occur.
The columns sex and status seems to be required in all cases when one runs the individual steps using the --step parameter. I encountered this also while running only the variant calling step.
Command used and terminal output
Relevant files
No response
System information
The text was updated successfully, but these errors were encountered: