-
Notifications
You must be signed in to change notification settings - Fork 2
Changes for 2018
see notes on status of data product reviews https://docs.google.com/document/d/1LqIVYYlU47Q0H1R_F0hhAm3xlydRzlHpH8QjlfP-K24/edit s/356
- Need to purge deprecated datasets
- Migrate Globus from ROGER to Nebula
need equations to compute traits
https://github.com/terraref/computing-pipeline/issues/216
- region of interest
- needs to work on raw images + scale to plot (like other image analyses)
aggregate points and compute plot level means
https://github.com/terraref/computing-pipeline/issues/356
need to add T correction defined here: https://github.com/terraref/reference-data/issues/161
https://github.com/terraref/reference-data/issues/179
- exclude wavelength from geostreams dataset
- improve irrigation (perhaps per-plot)
- georeferenced or referenced to gantry xyz ply product
- leaf angle high priority
- height distribution: add skewness and kurtosis
- we may not need to keep variables in both geostreams and netcdf. netcdf can be used specifically for solar informtion
- redundant variables:
raw_
andsensor_
values (e.g. of par, co2, etc) are redundant with variables that have names like 'Atmospheric_CO2_concentration'.- Remove variables beginning in
raw_
from the environmental logger netcdf files - variables beginning in
sensor_
have no data - use consistent standard names
- Remove variables beginning in
to subset out just the spectral radiometer and other values needed for the hyperspectral workflow, something like
ncks -v time -v flx_dwn -v flx_sns -v flx_spc_dwn -v wvl_lgr -v wvl_dlt \
Level_1/EnvironmentLogger/2017-08-12/EnvironmentLogger_lv1_2017-08-12_uamac.nc #outfile.nc?
?? what variables are needed for hyperspectral workflow?
https://github.com/terraref/reference-data/issues/176
- use controlled vocabularies, e.g. as described in https://github.com/terraref/sensor-metadata/blob/master/README.md
- provide dictionary for metadata fields
- add url link to managements from experiment_metadata field (??) similar to
select * from managements where treatment_id in (select id from treatments join traits join sites join experiments where experiments.name = ....)
Might be v. simple - should export plot-level black/white masks from the canopy cover extractor.
https://github.com/terraref/computing-pipeline/issues/376
https://github.com/terraref/computing-pipeline/issues/356
- all sensor metadata should be publicly acessible (this was a bug?)
- per-user, read-only API keys
- enable search interface
cross-platform search
Wei Qin to develop protocol / testing framework with feedback from Zongyang, Rob Kooper, Craig, others
- write protocol for submitting an extractor that includes:
- Pull requests
- Tests
- Protocol
- quality statement
-
need to make sure we have done code reviews, have tests, protocols, quality statements for extractors above
-
(Proposed) Format for READMEs
-
Extractor name:
-
Date: date documentation was created
-
Author: documentation and extractor author(s)
-
Extractor Description: One or two sentence english description of the extractor purpose
-
Inputs and Outputs: Specific definition of the input and output of the extractor
-
Algorithm description: Long form description of the algorithm
-
Parameters: If there are parameters that may need changing for future
-
Failure Conditions: Known situations where the extractor might fail.
- how to use / store in BETYdb
- how to archive / assign doi, share etc
- data reviews / qa/qc
- process to handle scan programs https://github.com/terraref/computing-pipeline/issues/362
implement methods following https://docs.google.com/document/d/1hWqkowvopYqGkeckSWg-_JzN3-DIS36rCBCFI09Sqyk/edit also search for related issues
computing on nebula w/ data on roger is slow https://github.com/terraref/computing-pipeline/issues/368
- mount specific directories rw on an as needed basis