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

+ document how to run bcftools commands from pysam #1275

Closed
wants to merge 1 commit into from

Conversation

indraniel
Copy link
Contributor

I recently had trouble running the bcftools commands within pysam. I saw the "Using samtools commands within python" section within the documentation and thought things would behave similarly. I didn't find it to be true. I ended up finding the solution through github issue 958.

I thought it would be nice to have this bcftools feature more explicitly documented for future users.

Let me know if any additional changes are desired.

  - this wasn't explicitly stated in the documentation.  I was
    using the notes described in [github issue 958][0] as a guide.
  - in the changes also put updated links to the bcftools and htslib.org pages

[0]: pysam-developers#958
jmarshall added a commit that referenced this pull request Jan 21, 2025
…tation

Describe both samtools and bcftools invocations. Supersedes #1275.
Add reference documentation covering all the keyword arguments, etc.

Describe in detail how to redirect output to a file, a common use case.
Fixes #1096, fixes #1241, fixes #1323, et al.

Update doc/conf.py's rst_epilog samtools and bcftools URLs to point to
version-specific man pages, and have devtools/import.py update the URLs.
@jmarshall
Copy link
Member

Thanks for the suggestion to document the bcftools subcommands too. I've taken an alternative approach in 51ff3f1 and incorporated bcftools into the existing samtools documentation.

@jmarshall jmarshall closed this Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants