Skip to content

add severity data #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Apr 12, 2025
Merged

add severity data #173

merged 4 commits into from
Apr 12, 2025

Conversation

avallecam
Copy link
Member

No description provided.

Copy link

github-actions bot commented Apr 9, 2025

Thank you!

Thank you for your pull request 😃

🤖 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:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials-middle/compare/md-outputs..md-outputs-PR-173

The following changes were observed in the rendered markdown documents:

 config.yaml (new)                |   86 +
 data-severity-static.R           |   23 +-
 data-severity-stratified.R (new) |   43 +
 data/diamond_70days.rds (new)    |  Bin 0 -> 1943 bytes
 data/mers_byage.rds (new)        |  Bin 0 -> 1799 bytes
 renv.lock (new)                  | 6232 ++++++++++++++++++++++++++++++++++++++
 6 files changed, 6374 insertions(+), 10 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.

⏱️ Updated at 2025-04-12 18:13:58 +0000

@avallecam avallecam mentioned this pull request Apr 9, 2025
15 tasks
github-actions bot pushed a commit that referenced this pull request Apr 9, 2025
github-actions bot pushed a commit that referenced this pull request Apr 12, 2025
@avallecam avallecam merged commit 5513ce6 into main Apr 12, 2025
5 of 6 checks passed
@avallecam avallecam deleted the add-severity-data branch April 12, 2025 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant