add tips and tricks page

Author: mldesroc

_quarto.yml

@@ -19,6 +19,7 @@ website:
      - getting_started.qmd
      - tuning.qmd
      - timesync.qmd
+     - tips_tricks.qmd
 
 format:
   html:

getting_started.qmd

@@ -5,8 +5,6 @@ Both the original LandTrendr paper [Kennedy et al. 2010](https://sciencedirect.c
 
 For more specific information on LandTrendr in GEE, the holy grail is the [eMapR LT GEE Guide](https://emapr.github.io/LT-GEE/index.html). This document walks you through running LandTrendr in GEE step by step, with example code. Speaking of code, most of us in the CAFRI lab use the [eMapR API code](https://emapr.github.io/LT-GEE/example-scripts.html) (or derivatives of it) when running LandTrendr. These scripts are the easiest place to start if you would like to run LandTrendr on your own. For quick reference, the [GEE developers guide](https://developers.google.com/earth-engine/apidocs/ee-algorithms-temporalsegmentation-landtrendr) has good information about algorithm parameter defaults.   
 
-For those who may be interested in exploring LandTrendr without wading into running the algorithm themselves, the eMapR group have also developed several [UI applications](https://developers.google.com/earth-engine/apidocs/ee-algorithms-temporalsegmentation-landtrendr) of LandTrendr that offer several different ways to interact with LandTrendr timeseries data.
-
 
 ## Understanding algorithm parameters
 The LandTrendr algorithm has several parameters that a user can adjust to control how the algorithm segments the time series of spectral data. While each of these parameters serves a specific purpose, there are some that we have found to be more useful than others. For more detailed discussion of each parameter, and their sensitivity, see [Kennedy et al. 2010](https://sciencedirect.com/science/article/pii/S0034425710002245?via%3Dihub). For information on adjusting these parameters for using Landtrendr in the Northern Forest Region see [Algorithm Tuning](tuning.qmd)  

tips_tricks.qmd

@@ -0,0 +1,7 @@
+# Tips and Tricks
+A few miscelaneous thought and observations from several years of using LandTrendr
+
+-	Keeping careful track of what parameters you used to generate which outputs can save you lots of headaches down the line as there is no way to tell from an output what parameters were used to generate it once it’s been spun up. We recommended both a consistent naming convention and saving changes to your script between each output as GEE keeps a version history of your scripts. 
+- We have found that flucuations of water levels in wetlands areas often shows up disturbance in LT outputs, which depending on your purposes may not be ideal. Unfortunaltey these fluctuations do result in very real changes in spectral values, and closely resemble other types of changes that may be of interest. 
+- On a related note, we highly recomend applying a water mask to your LT outputs as predictions for bodies of water are typically meaningless. Depeneding on the area that you are interested in, masking out developed areas may also be useful.
+- For those who may be interested in exploring LandTrendr without wading into running the algorithm themselves, the eMapR group have also developed several [UI applications](https://developers.google.com/earth-engine/apidocs/ee-algorithms-temporalsegmentation-landtrendr) of LandTrendr that offer several different ways to interact with LandTrendr timeseries data.