When Haglof arrives we'll see you about workflow and data format.
@bpbond - never touch (always keep copies of) raw data; everything done via scripts; things defined in only one place
@atkinsjeff - how will repos be organized? Repositories for
leaf physiology and chemistry
soil fluxes (FoRTE-soilfluxes)
inventory and Haglof (FoRTE-inventory)
Lidar structure, optical (FoRTE-canopy)
We learn that @atkinsjeff has strong feelings about spaces and capitalization.
@bpbond - data files should encode all information necessary; doesn't depend on directory tree position
In general - plot identifier - e.g. A45G - but that is informational only! Ben makes the point that just numbering the plots 1-16 or something is also good and 'blinds' data collection a little better. We'll think about it.
In July - use early data and set up example workflow - e.g. inventory data or something
When Haglof arrives we'll see you about workflow and data format.
@bpbond - never touch (always keep copies of) raw data; everything done via scripts; things defined in only one place @atkinsjeff - how will repos be organized? Repositories for
FoRTE-soilfluxes)FoRTE-inventory)FoRTE-canopy)We learn that @atkinsjeff has strong feelings about spaces and capitalization.
@bpbond - data files should encode all information necessary; doesn't depend on directory tree position
In general - plot identifier - e.g. A45G - but that is informational only! Ben makes the point that just numbering the plots 1-16 or something is also good and 'blinds' data collection a little better. We'll think about it.
In July - use early data and set up example workflow - e.g. inventory data or something