Open VDS issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues2021-03-10T15:00:48Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/73Python VDS creation doesn't work2021-03-10T15:00:48ZMorten OfstadPython VDS creation doesn't workThere are two problems:
* The VolumeDataAxisDescriptors created by Python end up pointing their names and units to temporary copies of strings that are then destructed. This leads to invalid strings for names and units for the created VD...There are two problems:
* The VolumeDataAxisDescriptors created by Python end up pointing their names and units to temporary copies of strings that are then destructed. This leads to invalid strings for names and units for the created VDS.
* The GetBuffer()/GetWritableBuffer() calls on VolumeDataPage don't create buffer views that actually work with Python and you just get a raw pointer that you can't use for anything.Version 2.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/71Add command-line parameters to SEGYImport tool for overriding specific header...2021-03-03T15:41:36ZMorten OfstadAdd command-line parameters to SEGYImport tool for overriding specific header fieldsWhen SEGYImport is being called from a script/in a container it can be inconvenient to create a header format JSON file, so we should provide the option to override header fields directly on the command line.When SEGYImport is being called from a script/in a container it can be inconvenient to create a header format JSON file, so we should provide the option to override header fields directly on the command line.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/66Add start time/depth determination and override to SEGYImport2021-01-21T13:41:52ZMorten OfstadAdd start time/depth determination and override to SEGYImportWe need to read the start time trace header field to create the axis descriptor for the time/depth axis and we need to provide a command-line parameter with an override if the information in the trace header is wrong.We need to read the start time trace header field to create the axis descriptor for the time/depth axis and we need to provide a command-line parameter with an override if the information in the trace header is wrong.Version 2.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/64Add options for adaptive streaming2021-03-05T10:41:04ZMorten OfstadAdd options for adaptive streamingAll the code to do the adaptive requests and decompression is there, we need to add the options to actually use it...All the code to do the adaptive requests and decompression is there, we need to add the options to actually use it...Version 2.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/58Refactor SEGY importer read strategy2020-09-01T09:10:43ZMorten OfstadRefactor SEGY importer read strategyThe SEGY importer currently reads entire inline-groups, split into multiple requests if they come from blob store. It is more efficient if we can start the import process before the entire inline-group is populated and instead read from ...The SEGY importer currently reads entire inline-groups, split into multiple requests if they come from blob store. It is more efficient if we can start the import process before the entire inline-group is populated and instead read from the input SEGY in "pages" of a fixed number of traces that are needed to make the next column of cubes.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/16Convert asserts to std::runtime_error where it makes sense2021-06-16T22:19:48ZMorten OfstadConvert asserts to std::runtime_error where it makes senseAny calls to the public API with invalid parameters should result in std::runtime_error, not in an assert triggering (which will only happen in debug builds). We will continue using error codes for errors that are not caused by an invali...Any calls to the public API with invalid parameters should result in std::runtime_error, not in an assert triggering (which will only happen in debug builds). We will continue using error codes for errors that are not caused by an invalid program (e.g. IO errors), and will use asserts for checking preconditions/postconditions and class invariants.Version 2.0Jørgen Lindjorgen.lind@3lc.aiJørgen Lindjorgen.lind@3lc.aihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/14Add IOManagerCurl2021-03-11T12:41:38ZJørgen Lindjorgen.lind@3lc.aiAdd IOManagerCurlTo maintain a predictable performance between IOManagers there should exist a IOManager utilising curl on both Windows and Linux that communicates with a server without any authentication. This can then be referenced as a benchmark for p...To maintain a predictable performance between IOManagers there should exist a IOManager utilising curl on both Windows and Linux that communicates with a server without any authentication. This can then be referenced as a benchmark for performance characteristics the other IOManagers should achieve. The IOManager should be written in such a way that it should be "trivial" for other IOManagers to utilise the http transfer code and add its own signing headers etc.Version 2.0Jørgen Lindjorgen.lind@3lc.aiJørgen Lindjorgen.lind@3lc.aihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/8File backend2020-08-07T12:37:29ZMorten OfstadFile backendA file backend based on the huebds library for manipulating data-store files should be added. This needs to have a compatibility layer so it can read files written with the commercial library (translating the serialized objects into JSON...A file backend based on the huebds library for manipulating data-store files should be added. This needs to have a compatibility layer so it can read files written with the commercial library (translating the serialized objects into JSON that is similar to the objects found in an object store version of VDS). The handling of chunk-metadata and metadata-pages is done quite differently for the file format, so there is some refactoring work to be done to make this backend possible.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/6Support for unbinned prestack seismic2021-02-04T09:19:15ZMorten OfstadSupport for unbinned prestack seismicThis includes shot, receiver and CMP/CDP/CRP gathers. The axis information needs to be correct according to the KnownMetadata.h, no bingrid metadata should be added.This includes shot, receiver and CMP/CDP/CRP gathers. The axis information needs to be correct according to the KnownMetadata.h, no bingrid metadata should be added.Version 2.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/5Support for prestack-migrated seismic2021-02-04T09:20:14ZMorten OfstadSupport for prestack-migrated seismicThe SEG-Y importer should create 4D volumes with a bin-grid for these data types.The SEG-Y importer should create 4D volumes with a bin-grid for these data types.Version 2.0