This task depends on this issue being completed first (i.e. PR accepted and merged, and issue closed). Although it's not a requirement that the 2 tasks be completed by the same applicant, it will be a more interesting learning experience if they are.
BSgenome data packages are one of the many types of annotation packages available in Bioconductor. They contain the genomic sequences, which comprise chromosome sequences and other DNA sequences, of a particular genome assembly for a given organism. For example BSgenome.Hsapiens.UCSC.hg19 is a BSgenome data package that contains the genomic sequences of the hg19 genome from UCSC. Users can easily and efficiently access the sequences, or portions of the sequences, stored in these packages, via a common API implemented in the BSgenomesoftware package.
This task's goal is to make a new BSgenome data package for UCSC genome gorGor6. The process of making such package is documented in the "How to forge a BSgenome data package" vignette from the BSgenomesoftware package. The landing page for the BSgenome package contains a link to this vignette.
Other useful links:
BSgenome issues on GitHub where many Bioconductor users who went thru the process of forging a BSgenome data package have already asked questions about this process. Note that most issues where those questions have been asked (and answered) are now closed so do not exclude closed issues from your research.
Make sure to complete all the Preliminary taskslisted here before you start working on this task. In particular, make sure that you have R 4.2 and that you are set up to use the devel version of Bioconductor (currently 3.16).
Only one applicant can work on this task. If you choose to work on this task, please make sure to assign yourself so other applicants know that the task is already being worked on. If later on you change your mind, please unassign yourself. It's ok to change your mind!
To work on this task, there's no need to fork anything. The goal of the task is to produce a new package (a BSgenome data package), but we're not going to add this package to git or GitHub.
To test the new package: install it, start R, load the package, and play around with it. This process is called "ad hoc manual testing". Once everything behaves and looks as expected, run R CMD build and R CMD check on the package. Note that R CMD check should always be run on the source tarball produced by R CMD build.
R CMD check might produce some NOTEs and even some WARNINGs. Let me know if that's the case and we'll discuss them.
Once you are confident that your new BSgenome data package works as expected, please add your seed file to the inst/extdata/Outreachy/ folder of the BSgenome software package. You'll need to fork the BSgenome repository for that, then add the seed file, commit, push, and submit a PR.
This task depends on this issue being completed first (i.e. PR accepted and merged, and issue closed). Although it's not a requirement that the 2 tasks be completed by the same applicant, it will be a more interesting learning experience if they are.
BSgenome data packages are one of the many types of annotation packages available in Bioconductor. They contain the genomic sequences, which comprise chromosome sequences and other DNA sequences, of a particular genome assembly for a given organism. For example BSgenome.Hsapiens.UCSC.hg19 is a BSgenome data package that contains the genomic sequences of the
hg19genome from UCSC. Users can easily and efficiently access the sequences, or portions of the sequences, stored in these packages, via a common API implemented in the BSgenome software package.This task's goal is to make a new BSgenome data package for UCSC genome
gorGor6. The process of making such package is documented in the "How to forge a BSgenome data package" vignette from the BSgenome software package. The landing page for the BSgenome package contains a link to this vignette.Other useful links:
BSgenome issues on GitHub where many Bioconductor users who went thru the process of forging a BSgenome data package have already asked questions about this process. Note that most issues where those questions have been asked (and answered) are now closed so do not exclude closed issues from your research.
Some users have also asked questions about this process on the Bioconductor support site. See questions tagged with "BSgenome" there: https://support.bioconductor.org/tag/bsgenome/
The BSgenome.Hsapiens.UCSC.hg19 landing page: https://bioconductor.org/packages/BSgenome.Hsapiens.UCSC.hg19
List of BSgenome data packages available in Bioconductor: https://bioconductor.org/packages/release/BiocViews.html#___BSgenome
https://github.com/Bioconductor/BSgenomeForge for more information about BSgenome data packages and additional links.
IMPORTANT NOTES TO OUTREACHY APPLICANTS:
R CMD buildandR CMD checkon the package. Note thatR CMD checkshould always be run on the source tarball produced byR CMD build.R CMD checkmight produce some NOTEs and even some WARNINGs. Let me know if that's the case and we'll discuss them.inst/extdata/Outreachy/folder of the BSgenome software package. You'll need to fork the BSgenome repository for that, then add the seed file, commit, push, and submit a PR.