You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/units/_unit05/unit05-05_best_scripting.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,11 @@ So if I want to extract a section from a LAS file it would be very helpful to be
29
29
30
30
Furthermore it is mandatory for further projects to have a detailed or standardized documentation. This costs once more time but pays off more than. Please note that the following examples already use the `Roxygen2` documentation syntax which can be used later for automated documentation
31
31
32
+
Let us start with the `10_CHM_Catalog.R` control script. This script already uses a setup script (`000_setup.R`) to create a reproducible environment. So we have to identify four different aspects:
32
33
34
+
* what is code that is used again and again? -> make a function of it
35
+
* what is the general setup for my working environment? -> put it into the setup script
36
+
* what are the overall control structures (workflow, settings etc.)-> create a master control file for ruling the rest
0 commit comments