generated from Bioconductor/BuildABiocWorkshop
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
151 additions
and
12 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,5 @@ | ||
^renv$ | ||
^renv\.lock$ | ||
^LICENSE\.md$ | ||
.github | ||
Dockerfile | ||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,3 +2,6 @@ inst/doc | |
*~ | ||
.Rproj.user | ||
*Rproj | ||
renv/ | ||
renv.lock | ||
.Rprofile |
This file contains 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,112 @@ | ||
--- | ||
title: "Writing an iSEE extension" | ||
author: Kevin Rue-Albrecht^[kevinrue67@gmail.com],Federico Marini^[marinif@uni-mainz.de], Charlotte Soneson^[charlottesoneson@gmail.com] | ||
output: rmarkdown::html_vignette | ||
vignette: > | ||
%\VignetteIndexEntry{Writing an iSEE extension} | ||
%\VignetteEngine{knitr::rmarkdown} | ||
%\VignetteEncoding{UTF-8} | ||
--- | ||
|
||
|
||
```{r, include = FALSE} | ||
knitr::opts_chunk$set( | ||
collapse = TRUE, | ||
comment = "#>" | ||
) | ||
``` | ||
|
||
# Writing an iSEE extension | ||
|
||
Authors: | ||
Kevin Rue-Albrecht^[University of Oxford], | ||
Federico Marini^[Johannes Gutenberg-Universität Mainz], | ||
Charlotte Soneson^[Friedrich Miescher Institute for Biomedical Research]. | ||
<br/> | ||
Last modified: 09 July, 2024. | ||
|
||
## Overview | ||
|
||
### Description | ||
|
||
This package demo will present a brief introduction to the functionality of the | ||
iSEE package and its existing extension packages, before demonstrating the | ||
writing of new functionality suitable for release in additional extension | ||
packages. | ||
|
||
### Pre-requisites | ||
|
||
* Familiarity with the SummarizedExperiment class. | ||
* Familiarity with the shiny package | ||
|
||
List any workshop prerequisites, for example: | ||
|
||
* Basic knowledge of R syntax | ||
* Familiarity with the GenomicRanges class | ||
* Familiarity with xyz vignette (provide link) | ||
|
||
List relevant background reading for the workshop, including any | ||
theoretical background you expect students to have. | ||
|
||
* List any textbooks, papers, or other reading that students should be | ||
familiar with. Include direct links where possible. | ||
|
||
### Participation | ||
|
||
Describe how students will be expected to participate in the workshop. | ||
|
||
### _R_ / _Bioconductor_ packages used | ||
|
||
List any _R_ / _Bioconductor_ packages that will be explicitly covered. | ||
|
||
### Time outline | ||
|
||
An example for a 45-minute workshop: | ||
|
||
| Activity | Time | | ||
|------------------------------|------| | ||
| Packages | 15m | | ||
| Package Development | 15m | | ||
| Contributing to Bioconductor | 5m | | ||
| Best Practices | 10m | | ||
|
||
### Workshop goals and objectives | ||
|
||
List "big picture" student-centered workshop goals and learning | ||
objectives. Learning goals and objectives are related, but not the | ||
same thing. These goals and objectives will help some people to decide | ||
whether to attend the conference for training purposes, so please make | ||
these as precise and accurate as possible. | ||
|
||
*Learning goals* are high-level descriptions of what | ||
participants will learn and be able to do after the workshop is | ||
over. *Learning objectives*, on the other hand, describe in very | ||
specific and measurable terms specific skills or knowledge | ||
attained. The [Bloom's Taxonomy](#bloom) may be a useful framework | ||
for defining and describing your goals and objectives, although there | ||
are others. | ||
|
||
### Learning goals | ||
|
||
Some examples: | ||
|
||
* describe how to... | ||
* identify methods for... | ||
* understand the difference between... | ||
|
||
### Learning objectives | ||
|
||
* analyze xyz data to produce... | ||
* create xyz plots | ||
* evaluate xyz data for artifacts | ||
|
||
## Workshop | ||
|
||
Divide the workshop into sections (`## A Section`). Include | ||
fully-evaluated _R_ code chunks. Develop exercises and solutions, and | ||
anticipate that your audience will walk through the code with you, or | ||
work on the code idependently -- do not be too ambitious in the | ||
material that you present. | ||
|
||
|
||
|