youngdjn
commented
4 years ago This is completed via pull request #27 . YAML config file can specify whether to open an existing project vs. create a new one. It also allows specification of the specific steps to run (so for example, if loading an existing project that has already had photos added and aligned, you would disable add photos and align photos via the YAML config).
--This would allow a user to run downstream processing (e.g., orthoimage generation) using existing upstream data outputs (e.g., dense point cloud or aligned photos). Thus, a user could produce, for example, multiple orthoimages (each with different stitching parameters) without having to repeat the photo alignment for each one.
--Need to determine if this can be built into the master control script and YAML config, or whether it is more sensible to code separately.
--Need to determine a good way to keep track of Metashape project files so that they can be reliably re-located when they are needed for resuming an existing project/pipeline.
--One option is to use the same master control script and YAML config, and allow the flexibility to specify which components of the pipeline to run and also to specify an existing project to load if it exists.
--If a project is resumed, need a way to load its processing parameters (e.g., of dense cloud generation) so that they can be added to the log that is output for the new (downstream) partial processing components (e.g., orthoimage generation).
--If a project is resumed, need to save any modifications (due to additional downstream processing) as a new project rather than modifying the existing project file. This will allow the original project file to be re-used repeatedly.