blackwater_2022_hep

[NewGraphEnvironment]

https://github.com/NewGraphEnvironment/blackwater_2022_hep

blackwater_2022_hep is a bit of a crazy beast that might be a good side show for you for a while and introduce you to a bunch of things that we can do that you might not be familiar yet. I see us doing many of these things for this Wedzin kwa project so I think you should try to see if you can get it to work. Even if it won't run or takes a long time to get through it all - this repo is a great reference for a bunch of these things and can help you understand about alternatives to handbombing things. You can view the gitpages (link top right of repo landing page of course) with the password I shared in LastPass to see some of what it produces when run. There are also a schwack of gpkg layers (same as tables but spatially represented stream segments and I think riparian treatments) that it produces that open in an associated Q project.

I will give you generally non-coding tasks to do too so that you can have things to switch between to allow you to keep moving and generate deliverables. Often even the "non-coding" tasks will follow coding principles so that we can leverage our work elsewhere (ex. table of riparian setbacks gets built in csv and/or tribble (yes - tribble vs tibble) with a xref table of "pretty names" and potentially column indexes so that it can be reused in scripts.

Things going on in blackwater_2022_hep:

1. amalgamation of column names from excel spreadsheets so we can combine multiple rows of title together into one (surprisingly - frequently necessary to retain all the info in "untidy" but common storage formats). the heavy lifting for this is done with R/functions.R so that part should be portable to this repo

2. storage of data outside of the repo for privacy. Data will be required to try to run it. Its in onedrive/repo/ . To get the data copy the entire data folder to your version of the repo using the command line and store the call required in a gist or in an issue on github. here is an example of the rsync call sort, store and modify all photos on onedrive so that all collaborators can see all photos fish_passage_peace_2023_reporting#2

3. password protected git pages

4. use of renv to have a stable package configuration so that the scripts shouldn't be breakable and should be portable between systems

5. interface with QGIS and SAGA through R and system commands (see R chunk mathews-dissolve-qgis and mathews-split-saga2 in 0120_mathews.Rmd

6. Use of DT tables (javascript library wrapped with DT package) to present interactive tables that can be sorted by the user

7. iteratively rename columns and combine complex dataframes for visual and computational comparison (good for baseline/predicted, baseline/after )