https://github.com/bioconductor/biocworkshops2019

The official repository of the Bioconductor 2019 Conference Workshops :confetti_ball:

https://github.com/bioconductor/biocworkshops2019

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (15.7%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

The official repository of the Bioconductor 2019 Conference Workshops :confetti_ball:

Basic Info
Statistics
  • Stars: 25
  • Watchers: 15
  • Forks: 15
  • Open Issues: 34
  • Releases: 0
Created about 7 years ago · Last pushed over 3 years ago
Metadata Files
Readme

README.md

This repository contains details of the build process and usage for materials from the Bioc2019 conference.

Compiled Workshops Link

https://rebrand.ly/biocworkshops2019

Running workshop materials locally

The workshops (except the CWL workshop) are all installed and ready-to-run inside docker; you will need to install docker on your machine to follow along. We have a base docker image seandavi/bioc_2019 that contains the operating system and base R installation. The workshops and additional package (over 600) are included as a separate download that can be mounted into the container as a volume. To use the entire set of workshop materials, do:

  • Make a directory for the installed packages:

    mkdir /home/ubuntu/bioc-libs # or another convenient directory with about 20GB of free space

  • Download and untar entire tar.gz file with all installed packages and materials:

    cd /home/ubuntu/bioc-libs # use the directory from above wget https://s3.amazonaws.com/biocbuild.cancerdatasci.org/bioc2019-usr-local.tar.gz tar -xzf bioc2019-usr-local.tar.gz

  • Run docker locally with (you may or may not need sudo depending on your docker setup):

    ```

    again, use the directory from above

    sudo docker run --name bioc2019 -d -v /home/ubuntu/bioc-libs:/usr/local/lib/R/site-library \ -p 80:8787 -e PASSWORD=bioc seandavi/bioc2019 ```

  • Credentials:

    • username: 'rstudio'
    • password: 'as you set it--bioc above'

Instructions For Workshop Authors

Getting started

To contribute a new workshop, open a BiocWorkshops issue starting with the [Workshop] keyword in the title of the issue. Provide a link to the repository in the issue message body. You may also include GitHub usernames of workshop collaborators. For a successful workshop build, adhere to the following:

  1. Package your workshop as an R package. The example package https://github.com/lpantano/dummychapter1 demonstrates all key elements of how your package must be prepared, and also provides an example .travis.yml for Continuous Integration against bioc-devel.
  2. Include a standard vignette in the vignettes directory
  3. Put any extra files (images, .bib) in inst/vignettes and reference them in the vignette using system.file
  4. Number 3 requires package chapter installation before vignette build or build_vignettes=TRUE when building the package.
  5. Use only one top-level section (#), for the title of your workshop. All other sections must be second-level (##) or lower. You may find the usage section of the Bookdown documentation helpful for background.
  6. Do not use BiocStyle functionality. The style will be based on bookdown/gitbook.

DESCRIPTION

Update the DESCRIPTION file adding packages utilized in your workshop to the Imports field.

Use bioc-devel

BioC2019 workshops will run on bioc-devel (3.10). That means that this book will be built on bioc-devel, workshop participants will use virtual machines running bioc-devel, and your workshops will be tested against bioc-devel. See Using ‘bioc-devel’ during mid-April to mid-October for how to run bioc-devel; thankfully we are in the easy time of year for running release and devel side-by-side. Also, the dummy chapter includes a highly recommendable TravisCI setup for Continuous Integration against bioc-devel.

Deadlines for Bioc2019

Please be aware of the following deadlines for the Bioconductor 2019 Conference in New York

  • Mon May 27: draft workshop materials submitted as an Issue to this Bioconductor GitHub repo
  • Mon June 10: complete workshop submitted. Only bugfixes / refinements should be made after this point.
  • Mon June 17: All workshops complete and building without error. No new commits to contributor repos will be incorporated.

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Owner

  • Name: Bioconductor
  • Login: Bioconductor
  • Kind: organization

Software for the analysis and comprehension of high-throughput genomic data

GitHub Events

Total
Last Year

Issues and Pull Requests

Last synced: over 1 year ago

All Time
  • Total issues: 36
  • Total pull requests: 2
  • Average time to close issues: 18 days
  • Average time to close pull requests: 4 days
  • Total issue authors: 27
  • Total pull request authors: 2
  • Average comments per issue: 1.61
  • Average comments per pull request: 0.0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • lwaldron (4)
  • PeteHaitch (3)
  • lcolladotor (2)
  • lgeistlinger (2)
  • hubentu (2)
  • mritchie (2)
  • vjcitn (1)
  • torongs82 (1)
  • cmirzayi (1)
  • nsheff (1)
  • seandavi (1)
  • Liubuntu (1)
  • jianhong (1)
  • gabrielodom (1)
  • HelenaLC (1)
Pull Request Authors
  • hubentu (1)
  • Liubuntu (1)
Top Labels
Issue Labels
status unknown (28) system.file_ok (18) request made to author (5) files_in_vignettes_dir (4) need_fix_system.file (3) no_need_system.file (3) need_repository (2) more_than_one_Rmd (1)
Pull Request Labels