Main content
Home
Menu
Loading wiki pages...
Drone Pipeline
A processing pipeline for drone captured plant phenomic information.
This document is intended to provide a high level context on the drone pipeline and provide information on how to use it.
Overview
The goals motivating the drone pipeline are (in no particular order):
- common processing: provide components that are reusable in multiple environments
- dynamic work flows: mix common and unique processing components to create meaningful processing pipelines
- scalable work flows: use scalable architecture as needed, in the right places, to return results faster
The drone pipeline effort is part of the larger TERRA REF project and the source code resides on TERRA REF GitHub site. Additional code and information can be found on the Drone Pipeline portion of our Digital Agriculture GitHub site.
Below is an overview diagram of the data processing pipelines.
Processing Steps
At its simplest level, the drone pipeline has the following steps:
- Make captured and configuration data available
- Trigger the start of processing
- Process data until the workflow is complete
- Make the result of the workflow available
Of course, there are many details the above steps gloss over. Details such as: how does one makes data available, and what does it mean to make it available?
In our approach we use the Scientific Filesystem based on Docker to package up the workflows and other functionality. This approach requires the data processed and produced to be local to the running Docker image. This can be done by using Docker volumes to make data available. See the Docker volumes pages for more information.
Transformers
Transformer are worker processes that perform specific units of work in our workflow. There are many alternative names for transformers, such as "nodes". We use the term transformers to indicate their specific conceptual basis and that they are used in our workflows.
All workflows consist of one or more transformers. Transformers work in sequence, and possibly together, to complete a workflow. Most transformers have different input requirements that need to be satisfied before they can be successfully run.
Workflows
Information on workflows can be found here, on this site
A workflow defines the order of transformer events. Workflows can have implicit or explicit components. An implicit workflow component are one or more transformers that are automatically triggered by the right conditions, an uploaded file for example. An explicit workflow component is one that is configured to be started after a separate component instance has completed its work.
Future Work
There is a roadmap on Zenhub for this pipeline's planned development.
Acknowledgements
Many people have put a lot of work into making this project happen. Our Acknowledgement page lists people and projects that have made contributions. If you feel that you have been left out of our Acknowledgements, or if you want to be removed, let us know!
Page permissions have changed
Your browser should refresh shortly…
Renaming wiki...
Wiki page deleted
Press Confirm to return to the project wiki home page.
Connected to the collaborative wiki
This page is currently connected to the collaborative wiki. All edits made will be visible to contributors with write permission in real time. Changes will be stored but not published until you click the "Save" button.
Connecting to the collaborative wiki
This page is currently attempting to connect to the collaborative wiki. You may continue to make edits. Changes will not be saved until you press the "Save" button.
Collaborative wiki is unavailable
The collaborative wiki is currently unavailable. You may continue to make edits. Changes will not be saved until you press the "Save" button.
Browser unsupported
Your browser does not support collaborative editing. You may continue to make edits. Changes will not be saved until you press the "Save" button.
Start managing your projects on the OSF today.
Free and easy to use, the Open Science Framework supports the entire research lifecycle: planning, execution, reporting, archiving, and discovery.
Copyright © 2011-2025
Center for Open Science
|
Terms of Use
|
Privacy Policy
|
Status
|
API
TOP Guidelines
|
Reproducibility Project: Psychology
|
Reproducibility Project: Cancer Biology