update

Author: terzev

Intro/2_preparations_project.qmd

@@ -2,13 +2,9 @@
 
 As your course assignment (Leistungsnachweis) you will develop a semester project, in groups of two. In this semester project you will analyze trajectory data of movement activities (e.g. biking, hiking, running, shopping). 
 
-In fact, we give you the opportunity to track your own movement behavior, generating trajectory data you will subsequently analyze yourself. There are two ways for you to generate your own trajectory data. 
+In fact, we give you the opportunity to track your own movement behavior, generating trajectory data you will subsequently analyze yourself.
 
-Please let us know which option you choose by filling out the survey on Moodle.
-
-## Option 1: Tracking App
-
-By using a tracking app, your phone will collect your movement data automatically. There are different types of tracking apps, from tracking specific activities to passivly tracking 24 hours. Here is a not conclusive list of tracking tools you could use. But fill free to use your own tracking tool if you are already using one:
+By using a tracking app, your phone will collect your movement data automatically. There are different types of tracking apps, from tracking specific activities to passively tracking 24 hours. Here is a not conclusive list of tracking tools you could use. But fill free to use your own tracking tool if you are already using one:
 
 ::: {#tbl-data-collection}
 
@@ -33,14 +29,8 @@ Tracking Methods
 
 :::
 
-Please check after a view days if the tracking is working properly. If you have any issues during installation or you are not able to track yourself after the installtion [please get in contact with us](mailto:terz@zhaw.ch).
-
-***If, however, for privacy reasons, you dont want to use a Tracking App we can hand out a GPS tracker to you.***
-
-## Option 2: GPS Tracker 
-
-You can use a GPS tracker, provided by our research group. By using a GPS tracker all your data will stay with you locally. 
+Please check after a view days if the tracking is working properly. If you have any issues during installation or you are not able to track yourself after the installation [please get in contact with us](mailto:terz@zhaw.ch).
 
-The drawback off this option is, that in order to retreave the data, you need to bring the tracker to us. Also more manual preprocessing is necessary when preparing your data for the project.
+If, however, for privacy reasons, you don't want to use a tracking app we can hand out a GPS tracker to you. They are, however, quite old and we would recommend that you would use a state of the art app. Another drawback off this option is, that in order to retrieve the data, you need to bring the tracker to us. Also more manual preprocessing is necessary when preparing your data for the project.
 
 If you choose this option please send us a quick [E-Mail](mailto:terz@zhaw.ch) so we can arrange the handover of the GPS tracker. You can get the tracker in our office GC 134 at the [Campus Grüental, Wädenswil](https://goo.gl/maps/xDvGFMBEvwBMdWiz7).

Unterrichtsunterlagen.Rproj

@@ -1,5 +1,4 @@
 Version: 1.0
-ProjectId: 43cdd95c-d3cc-4093-bf7c-a93f64fb3a17
 
 RestoreWorkspace: No
 SaveWorkspace: No

_freeze/Intro/1_preparations_course/execute-results/html.json

@@ -2,7 +2,7 @@
   "hash": "c96c32b96861df609ae2225c1845e3b5",
   "result": {
     "engine": "knitr",
-    "markdown": "# Preparation Course {#w0-preparation}\n\nIn this course we will be using R, RStudio and Git. We ask you to install and/or update these programs *before* the start of the course, so that we do not loose time once the course starts. In this chapter, we cover the course requirements and some tips on how you should change your RStudio settings. \n\n\n\n\n\n\n\n\n\n## Install or update R (not RStudio)\n\nIf you haven't installed R yet, do so now by getting the newest version from [CRAN](https://cran.r-project.org/). If you do have R installed, check your Version of `R` by opening RStudio and typing the following command into the console. \n\n\n\n\n::: {.cell}\n\n```{.r .cell-code}\nR.version.string\n```\n\n::: {.cell-output .cell-output-stdout}\n\n```\n[1] \"R version 4.3.3 (2024-02-29)\"\n```\n\n\n:::\n:::\n\n\n\n\nThis returns the version number of your R installation, whereas the first digit (`4`) indicates the number of the *major release*, the second digit  (`3`) indicates the *minor release* and the last digit (`3`) refers to the *patch release*. As a general rule of thumb, you will want to update R if you\n\n- don't have the current *major* version or\n- are lagging two (or more) versions behind the current *minor release*\n\nIn the time of writing (February, 2025), the current `R` Version is 4.4.2 (released on 31.10.2024, see [cran.r-project.org](https://cran.r-project.org/)). Your installation should therefore not be older than 4.3.0.\n\nIf your current installation is older, make sure that you have updated R before the course. Check [these instructions on how to update R](https://www.linkedin.com/pulse/3-methods-update-r-rstudio-windows-mac-woratana-ngarmtrakulchol/)\n\n## Install or update RStudio {#sec-update-rstudio}\n\nRStudio is the IDE (integrated development environment) we use in our course to interact with R. There are good alternatives you can use, RStudio simply seems to be [the most popular choice](https://twitter.com/mdancho84/status/1502237075550392323). If you want to use your own IDE, please feel free to do so. However, we don't recommend this if you are a beginner.\n\nWe recommend updating RStudio to the newest version before the course: check if this is the case by clicking on *help > check for updates*. \n\n## Install the necessary packages\n\nIn the course, we will be needing several packages. Save time during the course by installing these upfront! The classical way to install a package (e.g. `pacman`) is as follows:\n\n\n\n\n::: {.cell}\n\n```{.r .cell-code}\ninstall.packages(\"pacman\")\n```\n:::\n\n\n\n\nHowever, the function `install.packages` does not check whether you already have the package installed. If you only want to install missing packages, you can use the function `p_install` with the option `force = FALSE` (from the package `pacman`).\n\n\n\n\n::: {.cell}\n\n```{.r .cell-code}\nlibrary(\"pacman\")\n\np_install(\"dplyr\", force = FALSE)\np_install(\"ggplot2\", force = FALSE)\np_install(\"readr\", force = FALSE)\np_install(\"tidyr\", force = FALSE)\np_install(\"sf\", force = FALSE)\np_install(\"terra\", force = FALSE)\np_install(\"tmap\", force = FALSE)\np_install(\"zoo\", force = FALSE)\np_install(\"units\", force = FALSE)\np_install(\"plotly\", force = FALSE)\np_install(\"patchwork\", force = FALSE)\n```\n:::\n\n\n\n\n\n## Configure RStudio{#configure-rstudio}\n\nNow we will set some RStudio Global options. Go to *Tools → Global options*. \n\n- **R General**\n  - Deactivate the option \"*Restore .RData into workspace at startup*\"[^restore]\n  - Set \"*Save workspace to .RData on exit*\" to \"*Never*\"[^saveworkspace]\n- **Code**\n  - Activate the option \"*Use native pipe operator, |> (requires R 4.1+)*\"[^pipe]\n- **R Markdown**\n  - Deactivate the option \"*Show output inline for all R Markdown documents*\"\n\n\n  \nClick on \"Ok\" to apply the change and close the options menu.\n\n[^restore]: We recommend that you start each RStudio session with a blank slate, as recommended by @wickham2023 see [here](https://r4ds.hadley.nz/workflow-scripts#projects)\n[^saveworkspace]: If we don't restore the workspace at startup, there is no need to save it on exit.\n[^pipe]: Our group has adapted the native pipe operator `|>` to reduce package dependencies. If you use the `magrittr` pipe `%>%` and would like to stick to it, feel free. \n",
+    "markdown": "# Preparation Course {#w0-preparation}\n\nIn this course we will be using R, RStudio and Git. We ask you to install and/or update these programs *before* the start of the course, so that we do not loose time once the course starts. In this chapter, we cover the course requirements and some tips on how you should change your RStudio settings. \n\n\n\n## Install or update R (not RStudio)\n\nIf you haven't installed R yet, do so now by getting the newest version from [CRAN](https://cran.r-project.org/). If you do have R installed, check your Version of `R` by opening RStudio and typing the following command into the console. \n\n\n::: {.cell}\n\n```{.r .cell-code}\nR.version.string\n```\n\n::: {.cell-output .cell-output-stdout}\n\n```\n[1] \"R version 4.4.3 (2025-02-28 ucrt)\"\n```\n\n\n:::\n:::\n\n\nThis returns the version number of your R installation, whereas the first digit (`4`) indicates the number of the *major release*, the second digit  (`4`) indicates the *minor release* and the last digit (`3`) refers to the *patch release*. As a general rule of thumb, you will want to update R if you\n\n- don't have the current *major* version or\n- are lagging two (or more) versions behind the current *minor release*\n\nIn the time of writing (March, 2026), the current `R` Version is 4.5.2 (released on 31.10.2025, see [cran.r-project.org](https://cran.r-project.org/)). Your installation should therefore not be older than 4.4.0.\n\nIf your current installation is older, make sure that you have updated R before the course. Check [these instructions on how to update R](https://www.linkedin.com/pulse/3-methods-update-r-rstudio-windows-mac-woratana-ngarmtrakulchol/)\n\n## Install or update RStudio {#sec-update-rstudio}\n\nRStudio is the IDE (integrated development environment) we use in our course to interact with R. There are good alternatives you can use, RStudio simply seems to be [the most popular choice](https://twitter.com/mdancho84/status/1502237075550392323). If you want to use your own IDE, please feel free to do so. However, we don't recommend this if you are a beginner.\n\nWe recommend updating RStudio to the newest version before the course: check if this is the case by clicking on *help > check for updates*. \n\n## Install the necessary packages\n\nIn the course, we will be needing several packages. Save time during the course by installing these upfront! The classical way to install a package (e.g. `pacman`) is as follows:\n\n\n::: {.cell}\n\n```{.r .cell-code}\ninstall.packages(\"pacman\")\n```\n:::\n\n\nHowever, the function `install.packages` does not check whether you already have the package installed. If you only want to install missing packages, you can use the function `p_install` with the option `force = FALSE` (from the package `pacman`).\n\n\n::: {.cell}\n\n```{.r .cell-code}\nlibrary(\"pacman\")\n\np_install(\"dplyr\", force = FALSE)\np_install(\"ggplot2\", force = FALSE)\np_install(\"readr\", force = FALSE)\np_install(\"tidyr\", force = FALSE)\np_install(\"sf\", force = FALSE)\np_install(\"terra\", force = FALSE)\np_install(\"tmap\", force = FALSE)\np_install(\"zoo\", force = FALSE)\np_install(\"units\", force = FALSE)\np_install(\"plotly\", force = FALSE)\np_install(\"patchwork\", force = FALSE)\n```\n:::\n\n\n\n## Configure RStudio{#configure-rstudio}\n\nNow we will set some RStudio Global options. Go to *Tools → Global options*. \n\n- **R General**\n  - Deactivate the option \"*Restore .RData into workspace at startup*\"[^restore]\n  - Set \"*Save workspace to .RData on exit*\" to \"*Never*\"[^saveworkspace]\n- **Code**\n  - Activate the option \"*Use native pipe operator, |> (requires R 4.1+)*\"[^pipe]\n- **R Markdown**\n  - Deactivate the option \"*Show output inline for all R Markdown documents*\"\n\n\n  \nClick on \"Ok\" to apply the change and close the options menu.\n\n[^restore]: We recommend that you start each RStudio session with a blank slate, as recommended by @wickham2023 see [here](https://r4ds.hadley.nz/workflow-scripts#projects)\n[^saveworkspace]: If we don't restore the workspace at startup, there is no need to save it on exit.\n[^pipe]: Our group has adapted the native pipe operator `|>` to reduce package dependencies. If you use the `magrittr` pipe `%>%` and would like to stick to it, feel free. \n",
     "supporting": [],
     "filters": [
       "rmarkdown/pagebreak.lua"