AWS R3M9 - SegY to oVDS converter
@Wibben - Please connect me with respective Support person on Monday to follow up.
I did a quick pass.
See steps here - R3M9-test-oVDS-steps.txt
See notes inside various steps. I get the impression that a few values are hard-coded and not dynamically linked to freshly loaded data.
In addition, I did not see either suitable work-product component (SeismicTraceData) nor Dataset (FileCollection,.SegY) being created.
What will the new Dataset (File Collection Bluware) be linked to?
Somehow there should be option to guide the converter with byte location of SegY header (when they are non-standard). Right?
Finally, can you please add to collection a step to retrieve the converted files (for oVDS there are many, as compared to single zgy file in the other converter)?