Processing Flight in a Workflow
After a new flight is created, there are seven steps to process a flight from raw images to phenotypic values. Some steps require user interaction through web interface, and other can be automatically processed in the server side.
- Upload images: Upload all images in a flight through web or transfer to storage.
- Extract image information: The image information is extracted by cluster and visualized to show flight path and raw images.
- Add ground control point: Ground control points are manually added into raw images.
- Stitch ortho-mosaic: All raw images are stitched together using all information above and specified parameters.
- Generate pyramid retile: All ortho-mosaic and vegetative index are retiled for online visualization.
- Segment plots: Plots are created using drawing tools and copied from flights in the same field. The reverse calculation is used to segment undistorted images.
- Extract phenotypic values: Phenotypic values are extracted using pre-defined functions and applied for each vegetative index.
- Archive: All flight data in the hard drive is archived into a
tarfile, transfered into long-term storage (e.g. tape) and deleted from the active storage to save space.
Five statuses are used to represent a workflow from wait to finish.
- Wait for previous workflows to finish.
- Ready to start to this workflow.
- Schedule to run on the cluster.
- Processing on the cluster.
- Finish to process all required tasks.
Workflow notification and logs
Email will send to all users with write permission on the flight when a workflow is finished and failed. A single email will send if there are multiple sub-tasks in each workflow (e.g. pyramid retile is running for each layer as a sub-task). User can disable email notification at the user setting.