Qimera Production Line Processing

This method is used where full processing capability is required for multiple users but the final result needs to be checked and final products created from it. Production line cleaning merges multiple Qimera projects into one single project where data cleaning and QC can be performed, this is done by importing the QPD results from the processing projects into a new and final project where the results are staged for delivery.  The graphic below explains the basic workflow concepts.


Benefits of this are:

  • For a Hydrographic office, a hydrographic survey can be portioned up between the bathymetry appraisal team for full validation by each person, but then pulled together at the end for final QC and then chart production requirements.
  • For Pipeline and cable surveys where the data can be divided into an alignment sheet per data processor. All of the separate projects can be brought together into one for the senior data processor to quality control the data and create the final product.
  • Processing can be divided offshore into one processor per day.  The mathematical processing is done in the daily project and is limited to the data and ancillary information to deal with the single day only.  This reduces the complexity of managing several tens or hundreds of additional ancillary files that may accrue over the span of a project.  The daily processing project only needs the ancillary data for that day, making this experience much less prone to error.
  • All merging operations are performed by the software NOT by humans, therefore eliminating error.

The series of images below show two separate sets of data being processed to get from raw sensor data to georeferenced soundings.  The third image shows the QPD results from the first two small projects being merged into an assembly project, with the Slice Editor being used to verify the line up between the two different data sets.  It's important to note that the QPDs are shared between the processing project and the main project and it is up to you to ensure that you do not attempt to write to QPDs at the same time.  The workflows for which this is meant to be used largely protect against this since data should not be submitted for inclusion in the master project until the mathematical processing is done, i.e the mathematical processing project is done and is closed.  The main processor then pulls the data into the main project with the understanding that the mathematical processing project will not be re-opened unless they surveyor is directed to do so, which should only be necessary if problems occur.  A little bit of human coordination goes a long way in orchestrating this and avoids complex resource locking schemes in other software packages which sometimes lock users out of their data.  Humans can be smart and can coordinate, we've made just enough functionality to let you coordinate and work together.