diff options
| author | Christian Kolset <christian.kolset@gmail.com> | 2025-04-30 09:12:41 -0600 |
|---|---|---|
| committer | Christian Kolset <christian.kolset@gmail.com> | 2025-04-30 09:12:41 -0600 |
| commit | c92bce22a096db9275756628613317998b083359 (patch) | |
| tree | d54e1394fa846d75037abb8383713c763c82a592 | |
| parent | eb2830349fd1892ec68659c22bab73f26255e268 (diff) | |
Updated book pdf
| -rw-r--r-- | admin/meeting-notes/2025-04-29.md | 22 | ||||
| -rw-r--r-- | book/computingME.pdf | bin | 4060639 -> 4056336 bytes | |||
| -rw-r--r-- | book/module1/module1.tex | 2 | ||||
| -rw-r--r-- | book/module2/error.tex | 8 | ||||
| -rw-r--r-- | tutorials/module_2/documentation.md | 2 |
5 files changed, 28 insertions, 6 deletions
diff --git a/admin/meeting-notes/2025-04-29.md b/admin/meeting-notes/2025-04-29.md new file mode 100644 index 0000000..5e8e9b7 --- /dev/null +++ b/admin/meeting-notes/2025-04-29.md @@ -0,0 +1,22 @@ +## Updates +- Working on Jupyter Notebooks (/tutorials/notebooks). Module 1 & 2 -> notebooks +- Writing in .md -> convert to .ipynb & .tex +- Time + +--- +## Topics +and questions + +- Course Overview + + +--- +## Discussion + + +--- +## Actions +- [ ] Finish off Jupyter tutorial (.md version) +- [ ] Finish Module 2 +- [ ] Start Module 3 +- [ ] Work on Jupyter Notebooks & focus on interaction for module 1
\ No newline at end of file diff --git a/book/computingME.pdf b/book/computingME.pdf Binary files differindex 4ef935c..298134f 100644 --- a/book/computingME.pdf +++ b/book/computingME.pdf diff --git a/book/module1/module1.tex b/book/module1/module1.tex index 5fd38b9..27bf133 100644 --- a/book/module1/module1.tex +++ b/book/module1/module1.tex @@ -7,8 +7,6 @@ \input{module1/control_structures} \input{module1/functions} \input{module1/classes_and_objects} -\input{module1/fundamentals_of_programming} -\input{module1/computing_fundamentals} \input{module1/open_source_software} \input{module1/1_excel_to_python} \input{module1/computational_expense} diff --git a/book/module2/error.tex b/book/module2/error.tex index 2646dc8..d515c4a 100644 --- a/book/module2/error.tex +++ b/book/module2/error.tex @@ -29,12 +29,12 @@ part of the computation}. An example of this could be using a finite number of terms from a Taylor Series expansion to approximate a function. -Approximating \(e^x\) by the first few terms of its Taylor series: +Approximating $e^x$ by the first few terms of its Taylor series: -\[e^x \approx 1 + x + \frac{x^2}{2!} + \frac{x^3}{3!}\] +$e^x \approx 1 + x +\frac{x^2}{2!} + \frac{x^3}{3!}$ The error comes from \textbf{neglecting} all the higher order terms -(\(\frac{x^4}{4!}, \frac{x^5}{5!}\), \ldots). +($\frac{x^4}{4!}, \frac{x^5}{5!}$), \ldots). Truncation error occurs when using numerical methods such as approximating and calculating derivatives and integrals. A @@ -57,7 +57,7 @@ algorithms. Round-off error is caused by \textbf{the limited precision} with which computers represent numbers. Since computers cannot store an infinite number of digits, \textbf{they round off} after a certain number of -decimal or binary places. For example, instead of representing π with +decimal or binary places. For example, instead of representing pi with infinite decimal places it may be rounded off to approximately 16 digits depending on number of bits and the representation of the bits. diff --git a/tutorials/module_2/documentation.md b/tutorials/module_2/documentation.md index 817914a..984c404 100644 --- a/tutorials/module_2/documentation.md +++ b/tutorials/module_2/documentation.md @@ -9,7 +9,9 @@ When documenting a project, it's essential to include detailed notes that captur ## Explain Your Decisions In programming, there are often several valid approaches to solving a problem. When documenting your code, it's important to clarify why you chose a particular method—especially if it deviates from common practices. Anticipating potential questions and addressing them directly in your documentation helps others follow your reasoning and builds trust in your solution. +  + A useful strategy for articulating these decisions is the "rubber duck" technique—explaining your code as if you're teaching it to someone else. Whether spoken aloud or written down, this practice helps you clarify your logic and communicate the reasoning behind your choices, providing valuable context for future collaborators or reviewers. ## Include a README |
