Repository navigation
Add visuals to explain signal vs noise - #130
Conversation
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:
Rendered Changes🔍 Inspect the changes: https://github.com/UoMResearchIT/Programming-With-Python/compare/md-outputs..md-outputs-PR-130 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. ⏱️ Updated at 2026-11-13 15:35:13 +0000 |
- add output for SD and mean - change line type for SD plots
Changes were made to copyright noticesThere are copyright updates on the (temporary) add-license-headers-to-17-clear-visual-to-explain-the-signal-vs-noise-2026-11-13-15-34-31 branch. Please review and merge, or add further commits (this branch will be deleted). |
Auto-generated via `{sandpaper}`
Source : 8010f01
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-11-13 15:47:45 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 67141b2
Branch : main
Author : Andrew Gait <andrew.gait@manchester.ac.uk>
Time : 2026-11-13 15:46:47 +0000
Message : Merge pull request #130 from UoMResearchIT/17-clear-visual-to-explain-the-signal-vs-noise
Add visuals to explain signal vs noise
Resolves #17