:robot: This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.
If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
The following changes were observed in the rendered markdown documents:
01-intro-to-rnaseq.md | 138 ++++++++++++++++++---
03-import-annotate.md | 5 +-
04-exploratory-qc.md | 2 +-
08-extra-design.md => 06-extra-design.md | 20 +--
06-gene-set-analysis.md => 07-gene-set-analysis.md | 38 +++---
07-next-steps.md => 08-next-steps.md | 0
...tial-expression-rendered-unnamed-chunk-19-1.png | Bin 22611 -> 22621 bytes
...6-extra-design-rendered-unnamed-chunk-10-1.png} | Bin
...6-extra-design-rendered-unnamed-chunk-11-1.png} | Bin
...6-extra-design-rendered-unnamed-chunk-12-1.png} | Bin
...6-extra-design-rendered-unnamed-chunk-13-1.png} | Bin
...6-extra-design-rendered-unnamed-chunk-13-2.png} | Bin
...06-extra-design-rendered-unnamed-chunk-6-1.png} | Bin
...06-extra-design-rendered-unnamed-chunk-6-2.png} | Bin
...06-extra-design-rendered-unnamed-chunk-7-1.png} | Bin
...06-extra-design-rendered-unnamed-chunk-8-1.png} | Bin
...06-extra-design-rendered-unnamed-chunk-9-1.png} | Bin
...analysis-rendered-unnamed-chunk-15-1.png (gone) | Bin 191049 -> 0 bytes
...-analysis-rendered-unnamed-chunk-15-1.png (new) | Bin 0 -> 191092 bytes
...e-set-analysis-rendered-unnamed-chunk-48-1.png} | Bin
...e-set-analysis-rendered-unnamed-chunk-50-1.png} | Bin
...e-set-analysis-rendered-unnamed-chunk-50-2.png} | Bin
...e-set-analysis-rendered-unnamed-chunk-55-1.png} | Bin
...e-set-analysis-rendered-unnamed-chunk-56-1.png} | Bin
...e-set-analysis-rendered-unnamed-chunk-57-1.png} | Bin
...e-set-analysis-rendered-unnamed-chunk-59-1.png} | Bin
...ne-set-analysis-rendered-unnamed-chunk-8-1.png} | Bin
fig/alternative_splicing_sub.png (new) | Bin 0 -> 851001 bytes
fig/factors-affecting-measurements.png (new) | Bin 0 -> 90935 bytes
fig/heatmap-example.png (new) | Bin 0 -> 22611 bytes
fig/maPlot-example.png (new) | Bin 0 -> 30027 bytes
fig/rnaseq_martin_wang.png (new) | Bin 0 -> 1609633 bytes
md5sum.txt | 36 +++---
setup.md | 8 +-
34 files changed, 178 insertions(+), 69 deletions(-)
What does this mean?
If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.
This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.
Thank you!
Thank you for your pull request :smiley:
:robot: This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.
If you have files that automatically render output (e.g. R Markdown), then you should check for the following:
Rendered Changes
:mag: Inspect the changes: https://github.com/carpentries-incubator/bioc-rnaseq/compare/md-outputs..md-outputs-PR-76
The following changes were observed in the rendered markdown documents:
What does this mean?
If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.:stopwatch: Updated at 2023-09-02 14:28:00 +0000