|
<< Click to Display Table of Contents >> Navigation: MultiFocusing > MF DBs merge |
MF DBs merge combines the results stored in a source Multi-Focusing (MF) database file into a destination MF database file. The module reads all bins (for ZO-MF) or all bin-trace pairs (for CO-MF) from the source database that have been flagged as successfully calculated, and copies their wave collection data and vertical parameters into the corresponding locations in the destination database. This allows processing results produced in separate runs or on separate nodes to be consolidated into a single unified database.
Use this module when a Multi-Focusing search has been executed in distributed mode across multiple cluster nodes, each writing results to its own partial database file. After all nodes complete, run MF DBs merge to assemble the partial results into the master database before proceeding to imaging or attribute extraction steps.
The path to the destination MF database file (.kdb format) into which the source results will be merged. This file must already exist and must have been created with the same bin grid geometry as the source file. The module writes calculated wave collection data and vertical parameters from the source into this destination, preserving any results already present in the destination that are not overwritten by corresponding source entries.
The path to the source MF database file (.kdb format) containing the calculated results to be copied into the destination. Only entries flagged as having state STORAGE_CALCULATED are transferred; incomplete or uncalculated bins are skipped. The source and destination files must have the same bin grid geometry for the merge to produce consistent results.
Specifies the type of Multi-Focusing database being merged. Select the option that matches the database format of both the source and destination files. Available options:
3D COMF (default) — 3D Common-Offset Multi-Focusing database. Results are stored per bin and per offset (trace), so the merge iterates over all bin-trace pairs in the source database.
3D ZOMF — 3D Zero-Offset Multi-Focusing database. Results are stored per bin only, so the merge iterates over all bins in the source database. Use this option when merging results from a ZO-MF search workflow.
2D COMF and 2D ZOMF — 2D variants of the above. Select the appropriate 2D option when working with 2D Multi-Focusing surveys.
This parameter group contains advanced options for controlling how the merge handles database header compatibility checks.
When enabled, the module skips the comparison of database header metadata between the source and destination files before performing the merge. Default: off. Under normal circumstances, both databases should have identical headers (same bin grid, same acquisition parameters) and this option should remain disabled. Enable this option only when you are certain the two databases are geometrically compatible but differ in non-critical header fields — for example, when databases were created on different versions of the software with minor metadata differences. Enabling this option when the databases have genuinely different geometries will produce incorrect results.