-
Notifications
You must be signed in to change notification settings - Fork 508
Update FreeBayes parameters for nf-core/eager compatibility #7850
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
Open
mertydn
wants to merge
2
commits into
galaxyproject:main
Choose a base branch
from
mertydn:update-freebayes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be moved down to the big if statement that we already have for the
$options_type.options_type_selectorcases.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bernt-matthias I kept this block separate on purpose. The custom_discovery mode needs to run directly, without the --region i loop. If I move it inside the main block, it will add the --region parameters and break the command. Is it okay to keep it separate to avoid the region split?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about adding a 4th mode to
target_limit_type_selector. That is splitting thedo_not_limitin one where sequences are processed separately in parallel and one where all sequences on a bam file are processed jointly (I think it might be important to do distinguish this anyway).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mertydn can you explain why this particular set of options is incompatible with splitting? I'm a bit lost.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wm75 I am trying to run the nf-core/eager workflow on Galaxy and get the exact same results.
In eager, this step runs all at once without splitting the data:
freebayes --bam 'b_0.bam' --fasta-reference 'localref.fa' -p 2 -C 1 -g 0
I think galaxy splits the data into pieces (--region).
But this causes changes in the vcf file, so my results do not match nextflow. I needed a way to run it without --region parametre
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't generate the result that only the QUAL values of the Y chromosomes are different in usegalaxy. because I had changed the XML file to restrict it to only use that parameters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just share one of the prior freebayes runs, or even just the inputs and the eager-produced vcf in a history and I can play with freebayes myself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://usegalaxy.org/u/mert1907/h/freebayes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wm75 The freebayes in usegalaxy includes a large number of parameters. If you try running it by restricting it to only the parameters I mentioned, I think you will get a result showing a difference only in the Y chromosome.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll investigate, thanks!