markdown source builds

Auto-generated via `{sandpaper}`
Source  : 1966412
Branch  : main
Author  : Matthew <6177028+bielsnohr@users.noreply.github.com>
Time    : 2025-05-27 14:21:56 +0000
Message : Merge pull request #456 from carpentries-incubator/bielsnohr/ukaea-march-2025

Updates from UKAEA March 2025 Run

Author: actions-user

32-software-architecture-design.md

@@ -131,6 +131,8 @@ goal of having *maintainable* code, which is:
 Now that we know what goals we should aspire to, let us take a critical look at the code in our
 software project and try to identify ways in which it can be improved.
 
+## Designing a New Feature for Our Project
+
 Our software project contains a pre-existing branch `full-data-analysis` which contains code for a new feature of our
 inflammation analysis software, which we will consider as a contribution by another developer.
 Recall that you can see all your branches as follows:
@@ -154,7 +156,7 @@ This bit of functionality is handled by `inflammation-analysis.py` in the projec
 The new data analysis code is located in `compute_data.py` file within the `inflammation` directory
 in a function called `analyse_data()`.
 This function loads all the data files for a given a directory path, then
-calculates and compares standard deviation across all the data by day and finaly plots a graph.
+calculates and compares standard deviation across all the data by day and finally plots a graph.
 
 :::::::::::::::::::::::::::::::::::::::  challenge
 

34-code-refactoring.md

@@ -95,12 +95,12 @@ we refactor or change code in the future.
 Start from the skeleton test code below:
 
 ```python
+from inflammation.compute_data import analyse_data
+
 def test_analyse_data():
-    from inflammation.compute_data import analyse_data
-    path = Path.cwd() / "../data"
+    path = os.path.join( os.getcwd(), "../data")
     data_source = CSVDataSource(path)
     result = analyse_data(data_source)
-
     # TODO: add assert statement(s) to test the result value is as expected
 ```
 
@@ -115,7 +115,6 @@ When determining the correct return data result to use in tests, it may be helpf
 result equals some random made-up data, observe the test fail initially and then
 copy and paste the correct result into the test.
 
-
 :::::::::::::::::::::::::
 
 :::::::::::::::  solution
@@ -134,11 +133,10 @@ Putting this together, our test may look like:
 
 ```python
 import numpy.testing as npt
-from pathlib import Path
+from inflammation.compute_data import analyse_data
 
 def test_analyse_data():
-    from inflammation.compute_data import analyse_data
-    path = Path.cwd() / "../data"
+    path = os.path.join( os.getcwd(), "../data")
     data_source = CSVDataSource(path)
     result = analyse_data(data_source)
     expected_output = [0.,0.22510286,0.18157299,0.1264423,0.9495481,0.27118211,

fig/mvc_arch.svg

@@ -23,9 +23,9 @@
 "episodes/25-section2-optional-exercises.md" "439682a4955568fa290b79ab2b486797" "site/built/25-section2-optional-exercises.md" "2024-12-06"
 "episodes/30-section3-intro.md" "24e70667c1848061ecb3d42ecf17dbf8" "site/built/30-section3-intro.md" "2024-12-06"
 "episodes/31-software-requirements.md" "adf1d73eb1d6449a95378b3f931327e2" "site/built/31-software-requirements.md" "2025-02-25"
-"episodes/32-software-architecture-design.md" "368bfd3da942c5aeceb2491a7203e787" "site/built/32-software-architecture-design.md" "2024-12-06"
+"episodes/32-software-architecture-design.md" "a5de51c1b48bd4de29e184060108dcc6" "site/built/32-software-architecture-design.md" "2025-05-27"
 "episodes/33-code-decoupling-abstractions.md" "b8985feb5faae7512cfa3d670b23dd40" "site/built/33-code-decoupling-abstractions.md" "2025-03-10"
-"episodes/34-code-refactoring.md" "a326b0b49f7114cf0b2e56c81231c4c7" "site/built/34-code-refactoring.md" "2024-12-06"
+"episodes/34-code-refactoring.md" "ecfc3e80e4e9a453a0a10069d0d4e894" "site/built/34-code-refactoring.md" "2025-05-27"
 "episodes/35-software-architecture-revisited.md" "8f92fb912d61d3aded15f51020699a14" "site/built/35-software-architecture-revisited.md" "2024-12-06"
 "episodes/40-section4-intro.md" "d8aa3c327409db1b14826b7619287c45" "site/built/40-section4-intro.md" "2024-12-06"
 "episodes/41-code-review.md" "726036baff329ef792c6b871135dc23a" "site/built/41-code-review.md" "2025-05-01"
@@ -51,8 +51,8 @@
 "learners/reference.md" "d5d60c894664895ab3423a31bd1e2aaa" "site/built/reference.md" "2024-12-06"
 "learners/setup.md" "172016f61e91f7d5402d1c8ebdde32df" "site/built/setup.md" "2024-12-06"
 "profiles/learner-profiles.md" "60b93493cf1da06dfd63255d73854461" "site/built/learner-profiles.md" "2024-12-06"
-"slides/section_1_setting_up_environment.md" "fbe98eecc7de47f1888f851a5023696e" "site/built/section_1_setting_up_environment.md" "2025-04-01"
-"slides/section_2_ensuring_correctness.md" "c07cf076af61c8fdcbcfe66f6817b5e7" "site/built/section_2_ensuring_correctness.md" "2024-12-06"
-"slides/section_3_software_dev_process.md" "95bbcd9fd58b0c7d522b786748cb0298" "site/built/section_3_software_dev_process.md" "2024-12-06"
-"slides/section_4_collaborative_soft_dev.md" "a31281464ece578e328d8f1210b2770e" "site/built/section_4_collaborative_soft_dev.md" "2025-03-07"
-"slides/section_5_managing_software.md" "ee351c9e92ba29cda41bca7d2647fb1f" "site/built/section_5_managing_software.md" "2024-12-06"
+"slides/section_1_setting_up_environment.md" "65631efd5db06ee9335f3ef026bdab72" "site/built/section_1_setting_up_environment.md" "2025-05-27"
+"slides/section_2_ensuring_correctness.md" "9ff6a044969f7959e32ffd1d9c60edd8" "site/built/section_2_ensuring_correctness.md" "2025-05-27"
+"slides/section_3_software_dev_process.md" "2f273ac5d34158dfc0cd0e98c8308c82" "site/built/section_3_software_dev_process.md" "2025-05-27"
+"slides/section_4_collaborative_soft_dev.md" "1a525b52fc0b08d2abd669411df544d5" "site/built/section_4_collaborative_soft_dev.md" "2025-05-27"
+"slides/section_5_managing_software.md" "378f9bc03723cc1113cc4766df35186d" "site/built/section_5_managing_software.md" "2025-05-27"