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

Added sawfish. #175

Open
wants to merge 7 commits into
base: develop-v3
Choose a base branch
from
Open

Added sawfish. #175

wants to merge 7 commits into from

Conversation

williamrowell
Copy link
Collaborator

@williamrowell williamrowell commented Dec 13, 2024

Added sawfish v0.12.7.

  • Added sawfish_discover and sawfish_call tasks.
  • sawfish_call optionally outputs supporting reads json (default true) for SVTopo
  • Removed pbsv task calls from workflow and replaced with sawfish task calls.
  • Added tests for sawfish tasks and removed tests for pbsv tasks.

To do:

  • Update documentation.
  • Integration test.

@williamrowell williamrowell self-assigned this Dec 13, 2024
@williamrowell williamrowell added the enhancement New feature or request label Dec 13, 2024
@williamrowell williamrowell requested a review from ctsa December 13, 2024 20:46
Copy link
Member

@ctsa ctsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good in general. I'd consider not using the sex-specific ploidy tracks by default for now based on my experience with downstream tools. Probably I should change the behavior to process these regions as haploid internally, but then still output GT values of "0/0" and "1/1" to improve downstream tool compatibiltiy.

ref_index = ref_map["fasta_index"], # !FileCoercion
out_prefix = "~{sample_id}.~{ref_map['name']}",
expected_male_bed = ref_map["hificnv_expected_bed_male"], # !FileCoercion
expected_female_bed = ref_map["hificnv_expected_bed_female"], # !FileCoercion
Copy link
Member

@ctsa ctsa Dec 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm still a bit on the fence about using the XX and XY ploidy tracks for sawfish in deployment (at least as implemented today). The "0" and "1" GT values on the sex chromosomes seem to be unexpected by a number of downstream pipelines, so this introduces some downstream risk with a pretty minor benefit.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does HiPhase handle haploid genotypes? @holtjma

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will pass them through, we already do this for TRGT

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was not thinking so much of pb pipeline tools, moreso things like truvari and various sv script bricabrac in use downstream. It's fine for now, but once some kind of CNV integration comes into play then this ploidy file will be essential, so I might make the switch to keep genotypes as 'diploid-formatted-haploid' (ie. 0/0 and 1/1) at that point.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now, do you suggest dropping the ploidy support?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think doing so would create fewer downstream problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants