Page Index - NEONScience/NEON-IS-data-processing GitHub Wiki
56 page(s) in this GitHub Wiki:
- Home
- How to use this wiki
- Terminology
- Github repo organization
- Best practices
- Minimize data stored in the Git repo
- Naming conventions
- Naming convention for code
- Naming convention for docker images
- Naming convention for pipelines
- Documentation
- Versioning
- Use functions as much as possible
- Use hierarchical logging
- Use dependency management
- Make your code efficient at scale
- 0 Workflow for product creation
- Please reload this page
- 1.0 Pipeline & repo structure, pipeline naming, terms
- Please reload this page
- 1.1 Generate L0 data in Pachyderm
- Please reload this page
- 1.2 Processing triggers and date controls
- Please reload this page
- 1.3 Groups and Context
- Please reload this page
- 1.4 Populating properties of named locations in Pachyderm
- Please reload this page
- 1.5 Glob pattern, and the filter_joiner
- Please reload this page
- 1.5 Populating Thresholds
- Please reload this page
- 2.1 Calibration and Uncertainty Functions
- Please reload this page
- 2.2 So, you've made it to the date gap filler
- Please reload this page
- 2.7 Timeseries padder: variable vs. constant
- Please reload this page
- 3.0 Updating modules or creating new modules
- Please reload this page
- 3.1 Combining modules
- Please reload this page
- 4.0 Release and deployment process
- Please reload this page
- 4.1 Validating L1 output
- Please reload this page
- 4.5 NEON data release and history (commit) squashing
- Please reload this page
- 9.0 Troubleshooting tips
- Please reload this page
- 9.1 Tailoring Pipeline Resources
- Please reload this page
- 9.1 Useful Pachyderm Commands
- Please reload this page
- 9.6 Converting .json pipe files to .yaml
- Please reload this page