github-actions[bot]
commented
1 year ago 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:
- :dart: correct output
- :framed_picture: correct figures
- :question: new warnings
- :bangbang: new errors
Rendered Changes
:mag: Inspect the changes: https://github.com/datacarpentry/r-raster-vector-geospatial/compare/md-outputs..md-outputs-PR-397
The following changes were observed in the rendered markdown documents:
12-time-series-raster.md | 283 +++---
config.yaml (gone) | 95 --
...ulti-band-in-r-rendered-plot-brick-1.png (gone) | Bin 457926 -> 0 bytes
...integration-rendered-compare-data-extents-1.png | Bin 33131 -> 33043 bytes
...tion-rendered-repeat-compare-data-extents-1.png | Bin 33131 -> 33043 bytes
...me-series-raster-rendered-ndvi-stack-wrap-1.png | Bin 29587 -> 28981 bytes
fig/12-time-series-raster-rendered-ndvi-wrap-1.png | Bin 28987 -> 28210 bytes
...ries-raster-rendered-view-stack-histogram-1.png | Bin 11034 -> 10887 bytes
md5sum.txt | 50 +-
renv.lock (gone) | 1004 --------------------
10 files changed, 156 insertions(+), 1276 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.:stopwatch: Updated at 2023-03-17 17:25:34 +0000
Episode 12 updated by replacing calls to raster and rgdal packages with calls to terra package. #368 #363