english improved

This commit is contained in:
2026-03-05 20:09:16 +01:00
parent c6609d15f5
commit 733fe8c290
21 changed files with 954 additions and 1042 deletions

View File

@@ -5,24 +5,24 @@ For this course, we will use the web-based development environment [Jupyterhub](
For long-term work, a personal installation is recommended.
## Installation on Personal Computer (Linux/MacOS/MS Windows)
## Installing on Your Own Computer (Linux/MacOS/MS Windows)
1. Install Julia with the installation and update manager **juliaup**: <https://github.com/JuliaLang/juliaup/>
2. Install **Visual Studio Code** as editor/IDE: <https://code.visualstudio.com/>
3. Install the **Julia language extension** in VS Code: <https://www.julia-vscode.org/docs/stable/gettingstarted/>
1. Install Julia with the installation and update manager **juliaup**: <https://github.com/JuliaLang/juliaup/>.
2. Install **Visual Studio Code** as editor/IDE: <https://code.visualstudio.com/>.
3. Install the **Julia language extension** in VS Code: <https://www.julia-vscode.org/docs/stable/gettingstarted/>.
Entry point:
Getting started:
- Create a new file with the extension `.jl` in VS Code
- Write Julia code
- `Shift-Enter` or `Ctrl-Enter` at the end of a statement or block starts a Julia-REPL, code is copied to the REPL and executed
- `Shift-Enter` or `Ctrl-Enter` at the end of a statement or block starts a Julia-REPL: the code is copied to the REPL and executed
- [Key bindings for VS Code](https://code.visualstudio.com/docs/getstarted/keybindings#_keyboard-shortcuts-reference)
and [for Julia in VS Code](https://www.julia-vscode.org/docs/stable/userguide/keybindings/)
### The Julia-REPL
When Julia is started directly, the [Julia-REPL](https://docs.julialang.org/en/v1/stdlib/REPL/) (*read-eval-print* loop) starts, where one can work interactively with Julia.
When Julia is started directly from the command line, the [Julia-REPL](https://docs.julialang.org/en/v1/stdlib/REPL/) (*read-eval-print* loop) opens, allowing interactive work.
```default
@@ -44,9 +44,9 @@ julia>
### Jupyterhub & Jupyter
- [JupyterHub](https://de.wikipedia.org/wiki/Project_Jupyter) is a multi-user server for Jupyter notebooks.
- Jupyter is a web-based interactive programming environment that
- was originally written for and in Python, but now supports many programming languages
- In Jupyter, one works with so-called *notebooks*. These are structured text files (JSON), recognizable by the file extension `*.ipynb`.
- Jupyter is a web-based interactive programming environment
- Originally written for and in Python, but now supports many programming languages
- In Jupyter, one works with so-called *notebooks*: structured text files (JSON) with the file extension `*.ipynb`.
Our Jupyterhub server: <https://misun103.mathematik.uni-leipzig.de/>
@@ -56,7 +56,7 @@ After logging into Jupyterhub, a file manager appears:
![](../images/notebook001.png)
:::
::: {.content-visible when-format="pdf"}
::: {.content-visible when-format="typst"}
![Jupyterhub file manager](../images/notebook001.png){width=50%}
:::
@@ -65,8 +65,8 @@ This can be used to:
- open existing *notebooks*,
- create new *notebooks*,
- upload files, e.g., notebooks, from a local computer,
- end the session with `Logout` (please don't forget!).
- upload files, e.g., notebooks, from your local computer,
- log out when finished (Please don't forget this!)
### Jupyter notebooks
@@ -75,15 +75,15 @@ This can be used to:
![](../images/notebook003.png)
:::
::: {.content-visible when-format="pdf"}
::: {.content-visible when-format="typst"}
![Jupyter Notebook](../images/notebook003.png){width=50%}
:::
*Notebooks* consist of cells. Cells can contain
- code or
- text/documentation (Markdown)
- Code, or
- Text/documentation (Markdown)
In text cells, the markup language [Markdown](https://en.wikipedia.org/wiki/Markdown) can be used for formatting and LaTeX for mathematical equations.
@@ -103,9 +103,9 @@ The cell currently being worked on can be in `command mode` or `edit mode`.
| Save notebook | `s` | `Ctrl-s` |
| Rename notebook | `Menu -> File -> Rename` | `Menu -> File -> Rename` |
| Close notebook | `Menu -> File -> Close & Halt` | `Menu -> File -> Close & Halt` |
| *run cell* | `Ctrl-Enter` | `Ctrl-Enter` |
| *run cell, move to next cell* | `Shift-Enter` | `Shift-Enter` |
| *run cell, insert new cell below* | `Alt-Enter` | `Alt-Enter` |
| *Run cell* | `Ctrl-Enter` | `Ctrl-Enter` |
| *Run cell, move to next cell* | `Shift-Enter` | `Shift-Enter` |
| *Run cell, insert new cell below* | `Alt-Enter` | `Alt-Enter` |
: {.striped}
@@ -115,17 +115,17 @@ The cell currently being worked on can be in `command mode` or `edit mode`.
![](../images/notebook002.png)
:::
::: {.content-visible when-format="pdf"}
::: {.content-visible when-format="typst"}
![Julia working...](../images/notebook002.png){width=50%}
:::
When a cell is working, its cell number becomes a `*` and
the `kernel busy` indicator (solid black dot at the top right next to the
Julia version) appears. If this takes too long (an *infinite loop*
is quickly programmed), then
the `kernel busy` indicator appears (solid black dot at the top right next to the
Julia version). If this takes too long (an *infinite loop*
can easily happen):
- click `Menu -> Kernel -> Interrupt`; if this is ineffective,
- click `Menu -> Kernel -> Interrupt`. If this doesn't work,
- click `Menu -> Kernel -> Restart`.
@@ -134,7 +134,7 @@ After a `kernel restart`, all cells containing the required definitions,
`using` statements, etc. must be executed again.
**At the end of work, please always:**
**At the end of each session, please always:**
- `Menu -> File -> Save & Checkpoint`
- `Menu -> File -> Close & Halt`