Open VDS issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues2020-06-18T08:17:39Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/51Fix buffer size calculations for multi-component data2020-06-18T08:17:39ZMorten OfstadFix buffer size calculations for multi-component dataThe buffer size calculation functions do not take the channel as an argument so they assume scalar data.The buffer size calculation functions do not take the channel as an argument so they assume scalar data.Version 1.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/45Compilation fails on centos 7 with recent devtoolset2020-09-01T09:12:54ZMorten OfstadCompilation fails on centos 7 with recent devtoolset> /usr/include/c++/4.8.2/atomic: In instantiation of 'struct std::atomic<std::chrono::time_point<std::chrono::_V2::steady_clock, std::chrono::duration<long int, std::ratio<1l, 1000000000l> > > >':
> /project/open-vds/src/OpenVDS/VDS/Volu...> /usr/include/c++/4.8.2/atomic: In instantiation of 'struct std::atomic<std::chrono::time_point<std::chrono::_V2::steady_clock, std::chrono::duration<long int, std::ratio<1l, 1000000000l> > > >':
> /project/open-vds/src/OpenVDS/VDS/VolumeDataPageAccessorImpl.h:50:67: required from here
> /usr/include/c++/4.8.2/atomic:167:7: error: function 'std::atomic<_Tp>::atomic() [with _Tp = std::chrono::time_point<std::chrono::_V2::steady_clock, std::chrono::duration<long int, std::ratio<1l, 1000000000l> > >]' defaulted on its first declaration with an exception-specification that differs from the implicit declaration 'constexpr std::atomic<std::chrono::time_point<std::chrono::_V2::steady_clock, std::chrono::duration<long int, std::ratio<1l, 1000000000l> > > >::atomic()'
> atomic() noexcept = default;
> ^
>
I don't think we need to use atomic for the m_lastUsed timestamp -- either that or we can just convert it to a plain int64_t which has milliseconds after startup (using the steady_clock).Version 1.0Jørgen Lindjorgen.lind@3lc.aiJørgen Lindjorgen.lind@3lc.aihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/40SEGYImport is generating faster than network2020-05-29T12:02:39ZJørgen Lindjorgen.lind@3lc.aiSEGYImport is generating faster than networkVersion 1.0Jørgen Lindjorgen.lind@3lc.aiJørgen Lindjorgen.lind@3lc.aihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/39Azure make sure id uses the blob key2020-05-28T07:30:40ZJørgen Lindjorgen.lind@3lc.aiAzure make sure id uses the blob keyVersion 1.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/32SEGYImport should be able to import SEG-Y from S3 or Azure Blob Storage2020-03-10T10:26:24ZMorten OfstadSEGYImport should be able to import SEG-Y from S3 or Azure Blob StorageThis requires making it possible to instantiate and use an IOManager from a client of the OpenVDS API (in this case the SEGYImport command-line tool). It also requires adding command line options to provide the required OpenOptions to th...This requires making it possible to instantiate and use an IOManager from a client of the OpenVDS API (in this case the SEGYImport command-line tool). It also requires adding command line options to provide the required OpenOptions to that IOManager to the SEGYImport command and matching the input files to a pattern so s3:// is recognized as a file in an S3 Blob and getting some advice from Microsoft on how to refer to data on Azure Blob Storage.Version 1.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/27Metadata Page download race2020-02-19T14:31:44ZJørgen Lindjorgen.lind@3lc.aiMetadata Page download raceWhen receiving an invalid metadata page there is a race leading to a deadlock.When receiving an invalid metadata page there is a race leading to a deadlock.Version 1.0Jørgen Lindjorgen.lind@3lc.aiJørgen Lindjorgen.lind@3lc.aihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/26Make IO tests for Error situations2020-03-10T10:27:10ZJørgen Lindjorgen.lind@3lc.aiMake IO tests for Error situationsWe need to be able to handle errors in the IO stack more gracefully. This needs some unit tests.
Make a facade IOManager to be able to fake IO errors and then create tests to verify behaviour for scenarios that include:
- Invalid Meta d...We need to be able to handle errors in the IO stack more gracefully. This needs some unit tests.
Make a facade IOManager to be able to fake IO errors and then create tests to verify behaviour for scenarios that include:
- Invalid Meta data Page data
- Invalid Mata data Page http request
- Invalid Data chunk data
- Invalid Data chunk http download
- Invalid Meta data Page upload
- Invalid Data chunk upload
- Invalid VolumeDataPage upload
- Invalid VolumeDataPage download
- Invalid TraceHeaders upload
- Invalid TraceHeaders downloadsVersion 1.0Jørgen Lindjorgen.lind@3lc.aiJørgen Lindjorgen.lind@3lc.aihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/25SEGYImport should create ImportInformation metadata2020-04-08T09:57:24ZMorten OfstadSEGYImport should create ImportInformation metadataThe ImportInformation metadata category was recently added to include more information about original file name and time of import, SEGYImport should generate this metadata.The ImportInformation metadata category was recently added to include more information about original file name and time of import, SEGYImport should generate this metadata.Version 1.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/20Document tools2020-05-27T09:58:20ZMorten OfstadDocument toolsThe SEGYImport and SEGYExport tools need to be documented in the Sphinx documentation (including usage examples and explanation of the whole import/export process), not just through the --help option.The SEGYImport and SEGYExport tools need to be documented in the Sphinx documentation (including usage examples and explanation of the whole import/export process), not just through the --help option.Version 1.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/18Document Python API2020-06-03T14:05:55ZMorten OfstadDocument Python APINeed to set up Sphinx autodoc to make separate sections for the C++ and Python APIs since they are not identical.Need to set up Sphinx autodoc to make separate sections for the C++ and Python APIs since they are not identical.Version 1.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/13Create a slice server example2020-01-27T14:05:48ZMorten OfstadCreate a slice server exampleCreate an example code that serves PNG images of slices of seismic over HTTP using Python and Flask. This shows off the Python API and is a realistic use-case for the technology.Create an example code that serves PNG images of slices of seismic over HTTP using Python and Flask. This shows off the Python API and is a realistic use-case for the technology.Version 1.0Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/9SEGYScan and SEGYUpload tools should be merged2020-01-27T14:06:35ZMorten OfstadSEGYScan and SEGYUpload tools should be mergedThere is no need to have two separate tools for scanning and uploading SEG-Y files, the command line options of both should be available and an additional --scan-only parameter can be added to tell it to only scan the file and write the ...There is no need to have two separate tools for scanning and uploading SEG-Y files, the command line options of both should be available and an additional --scan-only parameter can be added to tell it to only scan the file and write the results of the scanning to a JSON file. The merged command-line tool should be named SEGYImport to be consistent with the naming of the SEGYExport tool.Version 1.0https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/3VolumeDataAccessor Clone() method is not implemented2020-01-03T14:48:54ZMorten OfstadVolumeDataAccessor Clone() method is not implementedThis method is used to clone a VolumeDataAccessor e.g. when used in a firstprivate() clause of an OpenMP parallel construct. It implements ref-counted shared access to the underlying VolumeDataPageAccessor while maintaining the pinned pa...This method is used to clone a VolumeDataAccessor e.g. when used in a firstprivate() clause of an OpenMP parallel construct. It implements ref-counted shared access to the underlying VolumeDataPageAccessor while maintaining the pinned page state separately for each thread. A test needs to be added to ensure that this works as intended.Version 1.0Morten OfstadMorten Ofstad