Open VDS issueshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues2024-02-26T20:09:18Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/188Compressed and Uncompressed size of a VDS2024-02-26T20:09:18ZJørgen Lindjorgen.lind@3lc.aiCompressed and Uncompressed size of a VDSIt would be nice to be able to get the compressed and uncompressed size of a VDS. It would also be very handy if this was exposed in VDSInfoIt would be nice to be able to get the compressed and uncompressed size of a VDS. It would also be very handy if this was exposed in VDSInfohttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/79Consider to rename tag in connections string for S32021-07-09T14:27:36ZAnatoly YanchevskyConsider to rename tag in connections string for S3Right now for S3 connection string, OpenVDS use 'SecretKey'
http://osdu.pages.community.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/getting-started.html#opening-a-vds
But requests to AWS API return 'secretAccessKey'.Right now for S3 connection string, OpenVDS use 'SecretKey'
http://osdu.pages.community.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/getting-started.html#opening-a-vds
But requests to AWS API return 'secretAccessKey'.https://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/117Could you please tell me how to convert SEG-Y files to vds using SEGImport in...2022-05-03T11:58:21ZEddie TuCould you please tell me how to convert SEG-Y files to vds using SEGImport in openVDS?This is my first time with VDS, can you please give me an example about how to convert SEG-Y files to vds using SEGImport? I would be very grateful!This is my first time with VDS, can you please give me an example about how to convert SEG-Y files to vds using SEGImport? I would be very grateful!https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/165Cpython3.11 wheels for linux2022-12-22T08:52:47ZFilip BrzękCpython3.11 wheels for linuxCurrently, the PyPI index has 3.1.2 wheels built for cpython3.11 only for windows, AFAIK latest `manylinux_2014` does have cpython3.11.
```log
docker run -it quay.io/pypa/manylinux2014_x86_64 ls /opt/python
cp310-cp310 cp36-cp36m cp38-...Currently, the PyPI index has 3.1.2 wheels built for cpython3.11 only for windows, AFAIK latest `manylinux_2014` does have cpython3.11.
```log
docker run -it quay.io/pypa/manylinux2014_x86_64 ls /opt/python
cp310-cp310 cp36-cp36m cp38-cp38 pp37-pypy37_pp73 pp39-pypy39_pp73
cp311-cp311 cp37-cp37m cp39-cp39 pp38-pypy38_pp73
```
Thanks!https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/154Crash in Segy import while eject flash drive with segy file (or disconnect la...2023-03-28T15:10:48ZArtem ВCrash in Segy import while eject flash drive with segy file (or disconnect lan/wi-fi with source segy file)It is extremely hard to reproduce, but bug is already exists in all releases of open-vds.
Let's discusse two different cases:
1. Move source segy file to flash drive
2. Import segy file (via SEGImport utils)
3. Eject flash drive while p...It is extremely hard to reproduce, but bug is already exists in all releases of open-vds.
Let's discusse two different cases:
1. Move source segy file to flash drive
2. Import segy file (via SEGImport utils)
3. Eject flash drive while processing
4. Crash without any dump
Another case:
1. Move source segy file to external network drive (google drive, smb or any other)
2. Import segy file (via SEGImport utils)
3. Unplug ethernet cable (disconnect from wifi/lan, close your corporate vpn connection or any other) while processing
4. Crash without any dump
I found, that main reason of crash inside `TraceDataManager`
Crash will be here:
```
const char* header = traceDataManager.getTraceData(trace, error);
if (error.code)
{
outputPrinter.printWarning("IO", "Failed when reading data", fmt::format("{}", error.code), error.string);
break;
}
const void* data = header + SEGY::TraceHeaderSize;
int primaryTest = fileInfo.Is2D() ? 0 : SEGY::ReadFieldFromHeader(header, fileInfo.m_primaryKey, fileInfo.m_headerEndianness),
secondaryTest;
```
![image](/uploads/6b6a1d4b0140865730491d87a35c71da/image.png)
As you can see `TraceDataManager::getTraceData` imp is safe.
```
const char
* basePtr = static_cast<const char *>(pageView->Pointer(error));
```
but... You loose nullptr check while return address.
I added required comparator for MVP:
![image](/uploads/a31740e7589fad71c1f61cea788424e4/image.png)
And yes - `basePtr` is nullptr.
Return ptr with any offset will crash application.
---
Solution: Add code snippet
```
const char *
getTraceData(int64_t traceNumber, OpenVDS::Error & error) const
{
...
// Additional check
if (basePtr == nullptr)
{
error.code = 1;
error.string = "Failed to acquire pageView pointer";
return nullptr;
}
return basePtr + (traceNumber - pageTrace) * m_traceByteSize;
}
```
---
How to 100% reproduce:
0. Start SEGYImport with debug session
1. Copy segy to flash, start importing and waith for 10-20-N% done.
2. Set breakpoint to line: ``` for (int64_t trace(firstTrace); trace <= segment->m_traceStop && error.code == 0; ++trace, ++tertiaryIndex)```
3. Eject flash drive
4. Iterate over loop up to crash :)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/85Crash with IOManagerAWS2021-06-28T08:09:31ZAnatoly YanchevskyCrash with IOManagerAWSTo work with AWS SDK need to call InitAPI/ShutdownAPI:
https://docs.aws.amazon.com/sdk-for-cpp/v1/developer-guide/basic-use.html
This what you do in IOManagerAWS.
But, this mean that we can not use AWS SDK in same process.
Similar probl...To work with AWS SDK need to call InitAPI/ShutdownAPI:
https://docs.aws.amazon.com/sdk-for-cpp/v1/developer-guide/basic-use.html
This what you do in IOManagerAWS.
But, this mean that we can not use AWS SDK in same process.
Similar problem described in:
https://github.com/aws/aws-sdk-cpp/issues/456
Maybe, you can provide flag in AWSOpenOptions, to skip your call InitAPI/ShutdownAPI ?https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/181Create 2d-lod for 3D post-stack data2023-03-31T12:48:06ZXudong DuanCreate 2d-lod for 3D post-stack dataAs the OpenVDS documentation, there is channel named "Fast Slices". I use SEGYImport tool with the "--create-2d-lods" option to translate a 3D post-stack SEGY. When I use the HueList the show the information of the generated VDS file, th...As the OpenVDS documentation, there is channel named "Fast Slices". I use SEGYImport tool with the "--create-2d-lods" option to translate a 3D post-stack SEGY. When I use the HueList the show the information of the generated VDS file, there is no data related to 2d-lod.
I want to ask how to generate 2d lods for 3d post-stack data.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/12Create a custom LOD generation example2023-01-13T07:37:43ZMorten OfstadCreate a custom LOD generation exampleAdd a program to the examples that reads a lower LOD, downsamples and creates a higher LOD. This example will have some value since it 1) shows how to write LODs and 2) can be run in the cloud (e.g. on AWS) after uploading the LOD 0 of t...Add a program to the examples that reads a lower LOD, downsamples and creates a higher LOD. This example will have some value since it 1) shows how to write LODs and 2) can be run in the cloud (e.g. on AWS) after uploading the LOD 0 of the data as a trigger or part of the ingestion service.Morten OfstadMorten Ofstadhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/22Create a frontend for the SliceServer2021-06-16T22:19:46ZMorten OfstadCreate a frontend for the SliceServerThe SliceServer example would be a lot cooler if it had a HTML frontend that let you select slice dimension and drag sliders to change inline/crossline/time position.The SliceServer example would be a lot cooler if it had a HTML frontend that let you select slice dimension and drag sliders to change inline/crossline/time position.https://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/150Create pkg-config configuration (.pc file) for consumption by other projects2022-10-28T07:22:45ZAlexander JaustCreate pkg-config configuration (.pc file) for consumption by other projectsIt would be nice if OpenVDS could generate a [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/) configuration file (`.pc` file) for easy consumption of the OpenVDS project in other projects. This would especially help wi...It would be nice if OpenVDS could generate a [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/) configuration file (`.pc` file) for easy consumption of the OpenVDS project in other projects. This would especially help with projects that are not using CMake as build system. One example would be projects using Go and its build system. Go has explicit support for pkg-config in the [CGO package](https://pkg.go.dev/cmd/cgo#hdr-Using_cgo_with_the_go_command) to obtain the needed flags for compiling and linking of applications to other packages. Would this be something one could add?
I made a quick test with a minimal template for the pkg-config configuration file which worked in my setup. I have attached the patch. It creates a `openvds.pc` file from the `openvds.pc.in` template file stored in `CMake` via a `configure_file` step in the CMake build process. The configuration file is installed into `TARGET_DIR/lib/pkgconfig/`. If the patch would be already acceptable or only small extra work, I would submit it as merge request.
[0001-Add-pkg-config-configuration-file-generation.patch](/uploads/612c2ede69944f24f2e8cb4ec83d8927/0001-Add-pkg-config-configuration-file-generation.patch)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/233CRS - Problem when the data is displayed in different UTM zones at the same p...2024-03-07T09:15:19ZJuliana Fernandesjuliana.fernandes@iesbrazil.com.brCRS - Problem when the data is displayed in different UTM zones at the same project.Hello,
IesBrazil team is testing OpenVDS+ with CRS and one of the steps were to QC the data using Headwave from Bluware.
The team noticed a problem and we did a documentation on the tests that I will present below:
**Goal of the Test...Hello,
IesBrazil team is testing OpenVDS+ with CRS and one of the steps were to QC the data using Headwave from Bluware.
The team noticed a problem and we did a documentation on the tests that I will present below:
**Goal of the Tests:** Check if OpenVDS+ is adding correctly the CRS into the VDS file,<br>
**Methodology:** Convert SEGY to VDS using OpenVDS+/Headwave and QC the data using Headwave,<br>
**Data used:** Volve and Brazilian data (Volve doesn't present any problem). From Brazil we used 4 files from Solimões Basin and 1 file from Amazonas Basin, provided by ANP. The data can find [HERE](https://reate.cprm.gov.br/anp/TERRESTRE), below you can download directly all the files used in this test (from Brazil, that is where we identified the problem):
* [0233_LESTE_URUCU.3D.MIG_FIN.1.sgy](https://reate.cprm.gov.br/arquivos/index.php/s/DKD0oj9FsZAU8tI/download?path=%2FSISMICA_3D%2F0233_LESTE_URUCU%2FTEMPO%2FSISMICA&files=0233_LESTE_URUCU.3D.MIG_FIN.1.sgy) - Solimões Basin, SAD69/UTM 20S, EPSG:29190
* [0237_AEROPORTO.3D.MIG_FIN.1.sgy](https://reate.cprm.gov.br/arquivos/index.php/s/DKD0oj9FsZAU8tI/download?path=%2FSISMICA_3D%2F0237_AEROPORTO%2FTEMPO%2FSISMICA&files=0237_AEROPORTO.3D.MIG_FIN.1.sgy) - Solimões Basin, SAD69/UTM 20S, EPSG:29190
* [0237_IGARAPE_MARTA.3D.MIG_FIN.2.sgy](https://reate.cprm.gov.br/arquivos/index.php/s/DKD0oj9FsZAU8tI/download?path=%2FSISMICA_3D%2F0237_IGARAPE_MARTA%2FTEMPO%2FSISMICA&files=0237_IGARAPE_MARTA.3D.MIG_FIN.2.sgy) - Solimões Basin, SAD69/UTM 20S, EPSG:29190
* [R0300_3D_CHIBATA_PSTM.3D.PSTM.1.sgy](https://reate.cprm.gov.br/arquivos/index.php/s/DKD0oj9FsZAU8tI/download?path=%2FSISMICA_3D%2FR0300_3D_CHIBATA%2FTEMPO%2FSISMICA&files=R0300_3D_CHIBATA_PSTM.3D.PSTM.1.sgy) - Solimões Basin, SIRGAS 2000/UTM 20S, EPSG:31980
* [R0300_2D_AM_URUCARA.3D.PSTM.1.sgy](https://reate.cprm.gov.br/arquivos/index.php/s/IPNA8z7hO1vHsxI/download?path=%2FSISMICA_3D%2FR0300_3D_AM_URUCARA%2FTEMPO%2FSISMICA&files=R0300_3D_AM_URUCARA.3D.PSTM.1.sgy) - Amazonas Basin, SAD69/UTM 21S, EPSG:29191<br>
**Shapefile:** Georeferenced polygons of exploratory blocks in geographic coordinates and datum SAD69, available [HERE](https://geomaps.anp.gov.br/geoanp/),<br>
**Problem:** When the project has a different zone from the data (e.g: the project is located at SAD69/ UTM 20S and the data is located at SAD69/ UTM 21S), the file is wrongly spatially positioned (We used a VDS converted by Headwave and the original SEGY to compare),<br>
**OpenVDS+ Version:** 3.3.0,<br>
**Comparative Scenario:**
* SEGY with Original CRS
* SEGY with WGS84 CRS
* VDS from HW with Original CRS
* VDS from HW with WGS84 CRS
* VDS from OpenVDS+ with WGS84 CRS (only option available)
### First Scenario - SEGY with Original CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.<br>
In this test the team uploaded all the segy files, listed in the "Data used" topic, under the Original CRS (also informed with the data list) and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.<br>
**Result: All the data are at the expected spatial position.**
![SEGY_with_Original_CRS](/uploads/285ab921116f92658bbf43007924bdbb/SEGY_with_Original_CRS.png)
### Second Scenario - SEGY with WGS84 CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.<br>
In this test the team uploaded all the segy files, listed in the "Data used" topic, under the CRS WGS84 and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.<br>
**Result: All the data are at the expected spatial position.**
![SEGY_with_Original_CRS](/uploads/285ab921116f92658bbf43007924bdbb/SEGY_with_Original_CRS.png)
### Third Scenario - VDS from HW with Original CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.<br>
In this test the team converted to vds, using Headwave, all the segy files, listed in the "Data used" topic, under the Original CRS (also informed with the data list) and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.<br>
**Result: All the data are at the expected spatial position.**
![SEGY_with_Original_CRS](/uploads/285ab921116f92658bbf43007924bdbb/SEGY_with_Original_CRS.png)
### Fourth Scenario - VDS from HW with WGS84 CRS
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.<br>
In this test the team converted to vds, using Headwave, all the segy files, listed in the "Data used" topic, under the CRS WGS84 and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.<br>
**Result: All the data are at the expected spatial position.**
![SEGY_with_Original_CRS](/uploads/285ab921116f92658bbf43007924bdbb/SEGY_with_Original_CRS.png)
### Fifth Scenario - VDS from OpenVDS+ with WGS84 CRS (only option available)
The project is under the coordinate reference system CRS SAD69/ UTM 20S (EPSG:29190) that includes most of the data of the test.<br>
In this test the team converted to vds, using OpenVDS+, all the segy files, listed in the "Data used" topic, under the CRS WGS84 and displayed. The polygon in red at the superior right corner in the image is the shapefile for the block R0300_3D_AM_URUCARA.<br>
**Result: The file R0300_3D_AM_URUCARA that is located under a different zone from the project (21S) is wrongly spatially positioned (Should be at the same position that the red polygon is).**
![VDS_with_WGS84_Open](/uploads/fc6638d20fffea098cd2fde1ee44dcac/VDS_with_WGS84_Open.png)
We are available for any additional information needed.
Regards,
Julianahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/216Data retrieval from requestVolumeTraces produces results inconsistent with or...2023-10-23T12:40:13ZDaniel MorganData retrieval from requestVolumeTraces produces results inconsistent with original segy and requestVolumeSubset.Using python libraries built from 3.2.6 to read but SEGYImport is version 3.3.255
We've have been trying to verify the fidelity of segy to vds conversions by comparing individual trace data from the original segy with the resulting VDS f...Using python libraries built from 3.2.6 to read but SEGYImport is version 3.3.255
We've have been trying to verify the fidelity of segy to vds conversions by comparing individual trace data from the original segy with the resulting VDS file. Since we were retrieving individual traces we thought to use VolumeDataAccessManager.requestVolumeTraces but the retrieved data did not match the original in many cases.
Test file was from Volve test set: "/ST0202/ST10010ZC11_MIG_VEL.MIG_VEL.VELOCITY.3D.JS-017527.segy"
Import used no compression, data retrieval LOD 0.
For ease of comparison, we wanted to retrieve the last trace from the file corresponding to inline/crossline 10396, 2800 (trace number 418996 from SEGY). The inline/crossline coordinates convert to inline/crossline indices 435 960 respectively.
Retrieval: `trace = accessManager.requestVolumeTraces([[435, 960]], traceDimension=0, lod=0)`
This is the result when compared with original trace data:
![image](/uploads/abd85b26d19f538913dd687dee607edd/image.png)
Now when we use VolumeDataAccessManager.requestVolumeSubset using min/max tuples narrowed to a single trace, our retrieved data matches the original segy perfectly.
```
minTup = (0, 960, 435, 0, 0, 0)
maxTup = (236, 961, 436, 0, 0, 0)
trace = accessManager.requestVolumeSubset(minTup, maxTup)
```
![image](/uploads/6494e54698f8d841b853b93bcefa953c/image.png)
My assumption is that we may be misusing requestVolumeTraces, but am unclear in what way.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/197Deadlock in VolumeDataRequestProcessor::WaitForCompletion after cancel loadin...2023-08-25T07:48:49ZAnatoly YanchevskyDeadlock in VolumeDataRequestProcessor::WaitForCompletion after cancel loading one of LODsWe create several LODs in OpenVDS container. When our viewer display data, some time need to cancel loading one of the LODs.
It produce deadlock in open-vds library.
Two threads that are in the deadlock: [stack_1.txt](/uploads/25ff1d9f8...We create several LODs in OpenVDS container. When our viewer display data, some time need to cancel loading one of the LODs.
It produce deadlock in open-vds library.
Two threads that are in the deadlock: [stack_1.txt](/uploads/25ff1d9f89d453a9b1a11eec99dcb5ab/stack_1.txt) and [stack_2.txt](/uploads/8dfb70257b51f09f3f6c8df050abdc5b/stack_2.txt)
To fix that, we do next changes: [VolumeDataRequestProcessor.patch](/uploads/9ddab5fc678d95834df15a07fc5874d9/VolumeDataRequestProcessor.patch)
Problem occurred on Linux, open-vds 3.0.3. But we found that in latest version function VolumeDataRequestProcessor::WaitForCompletion did not changed.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/163Default behaviour of SEGYImport --sample-unit2022-12-15T15:04:09ZErlend HårstadDefault behaviour of SEGYImport --sample-unitHi!
I recently noticed that the default value of SEGYImport --sample-unit is "ms". This seams like a dangerous default. I think it's reasonable to assume that a lot of people (including myself :smile:) will mess up by trusting the defau...Hi!
I recently noticed that the default value of SEGYImport --sample-unit is "ms". This seams like a dangerous default. I think it's reasonable to assume that a lot of people (including myself :smile:) will mess up by trusting the default here. Would a better default be the value of the Trace Value Measurement Unit (byte 203-204) in the SEGY? Or if that might not be trusted and/or rarely present, then another good default could unitless?
I would also _love_ a strict option that fails the creation if something is even slightly off.
Related to axis units, I also have a question about the relationship between axis units and axis name. I would expect that the name and unit corresponded. I.e. if unit = m then name (annotation) = Depth and so forth. However, SEGYImport seams to always write "Sample" as the axis namehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/103Dimension and Produce2022-09-03T00:48:52ZPaal KvammeDimension and ProduceI have been using OpenVDS for a while to read 3d seismic data and I have accumulated several questions. My apologies if I did not read the documentation closely enough.
## What is DimensionsND and DimensionsGroup?
I suspect that Dimens...I have been using OpenVDS for a while to read 3d seismic data and I have accumulated several questions. My apologies if I did not read the documentation closely enough.
## What is DimensionsND and DimensionsGroup?
I suspect that DimensionsND is OpenVDS, DimensionsGroup is the corresponding VDS type. That doesn't help me much because I don't really understand why either is needed. It looks to be that these are enums used to extract e.g. 3d data from a 4d, 5d, or 6d cube by skipping some dimensions but not re-ordering or transposing them.
DimensionsND extracts two or three dimensions, e.g. Dimensions_01 or Dimensions_012. DimensionsGroup extracts 1 to all 6 dimensions.
But why are these needed at all when I read data? If skipping a dimension, why not set min==max instead for the "constant" indices and min=max=0 for the unused ones?
Can you confirm the following: If I want to read a 3d sub-cube from a 3d dataset, i.e. layout->GetDimensionality()==3, then DimensionsND can only be Dimensions_012 when i want to read a sub-cube.
How can I handle OpenVDS files having more that three dimensions, that are really just multiple 3d cubes packed together with the fourth dimension being the cube number? I suspect the answer to the previous question might shed some light in this.
## What is a multi-component file?
And how should it be handled? Is this the same as a 4d cube or is this a different feature?
## What is ProduceStatus?
Can you confirm that I can ignore this when reading full resolution data? I am guessing that "Unavailable" tells me I might get an error later and the difference between "Normal" and "Remapped" is I suspect just a hint about the cost. I am also guessing that Remapped is only relevant for LOD > 0.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/225DmsDataset class is using resources that have been moved from2024-01-29T13:47:01ZDeepa KumariDmsDataset class is using resources that have been moved fromThe vector containing response is moved here: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/blob/master/src/OpenVDS/IO/DmsIoFactories/DmsIoManagerFactory.cpp#L200
https://community.opengroup....The vector containing response is moved here: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/blob/master/src/OpenVDS/IO/DmsIoFactories/DmsIoManagerFactory.cpp#L200
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/blob/master/src/OpenVDS/IO/DmsIoFactories/DmsIoManagerFactory.cpp#L223
The same resource which was already moved from, is being used here:
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/blob/master/src/OpenVDS/IO/DmsIoFactories/DmsIoManagerFactory.cpp#L204
and https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/blob/master/src/OpenVDS/IO/DmsIoFactories/DmsIoManagerFactory.cpp#L227
Resources that have been moved from should not be used, that is the objective of move. More ref: https://en.cppreference.com/w/cpp/utility/moveM23 - Release 0.26Deepa KumariDeepa Kumarihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/106DMS token callback2022-01-06T12:59:13ZPaal KvammeDMS token callbackI would very much like to have a token callback in DMSOpenOptions, to be used as an alternative to supplying fixed strings.
I only need this for C++. Where I believe it is trivial to implement.
My application already uses the DMS for o...I would very much like to have a token callback in DMSOpenOptions, to be used as an alternative to supplying fixed strings.
I only need this for C++. Where I believe it is trivial to implement.
My application already uses the DMS for other purposes, and has proprietary code to manage tokens. Including refreshing them every hour. There isn't really any way of extending that to OpenVDS without exposing SDManager::setAuthProviderCallback().
Suggested implementation in [tokencb.patch](/uploads/f6e86db89db54e8c0c6474d5980c8580/tokencb.patch)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/202[docs][webpage] seems Python API docs are gone2023-09-15T11:30:27ZFilip Brzęk[docs][webpage] seems Python API docs are gone[Python API Link](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/python-api.html)
![image](/uploads/5fc6bed0cd3a145846b921ac6d2221c1/image.png)[Python API Link](https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/python-api.html)
![image](/uploads/5fc6bed0cd3a145846b921ac6d2221c1/image.png)