Skip to content

Conversation

@jt14den
Copy link
Member

@jt14den jt14den commented Jan 22, 2026

This PR adds a new section to 'computation_programming.md' explicitly teaching how to define Inputs and Outputs before designing algorithms. Fixes #18.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 22, 2026

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/LibraryCarpentry/lc-computational-thinking/compare/md-outputs..md-outputs-PR-34

The following changes were observed in the rendered markdown documents:

 computation_programming.md |   18 +-
 config.yaml (gone)         |   89 ----
 md5sum.txt                 |    4 +-
 renv.lock (gone)           | 1009 --------------------------------------------
 4 files changed, 19 insertions(+), 1101 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 2026-01-22 01:53:12 +0000

github-actions bot pushed a commit that referenced this pull request Jan 22, 2026
@jt14den jt14den merged commit a8beaa1 into main Jan 22, 2026
7 of 8 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 22, 2026
Auto-generated via `{sandpaper}`
Source  : a8beaa1
Branch  : main
Author  : Tim Dennis <tdennis@library.ucla.edu>
Time    : 2026-01-22 01:54:07 +0000
Message : Merge pull request #34 from LibraryCarpentry/feat/inputs-outputs

Add section on Defining Inputs and Outputs
github-actions bot pushed a commit that referenced this pull request Jan 22, 2026
Auto-generated via `{sandpaper}`
Source  : f28c8e0
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2026-01-22 01:55:01 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : a8beaa1
Branch  : main
Author  : Tim Dennis <tdennis@library.ucla.edu>
Time    : 2026-01-22 01:54:07 +0000
Message : Merge pull request #34 from LibraryCarpentry/feat/inputs-outputs

Add section on Defining Inputs and Outputs
github-actions bot pushed a commit that referenced this pull request Jan 22, 2026
Auto-generated via `{sandpaper}`
Source  : a8beaa1
Branch  : main
Author  : Tim Dennis <tdennis@library.ucla.edu>
Time    : 2026-01-22 01:54:07 +0000
Message : Merge pull request #34 from LibraryCarpentry/feat/inputs-outputs

Add section on Defining Inputs and Outputs
github-actions bot pushed a commit that referenced this pull request Jan 22, 2026
Auto-generated via `{sandpaper}`
Source  : d1a2194
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2026-01-22 01:56:47 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : a8beaa1
Branch  : main
Author  : Tim Dennis <tdennis@library.ucla.edu>
Time    : 2026-01-22 01:54:07 +0000
Message : Merge pull request #34 from LibraryCarpentry/feat/inputs-outputs

Add section on Defining Inputs and Outputs
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.

Modelling inputs and outputs

2 participants