Seismic issueshttps://community.opengroup.org/groups/osdu/platform/domain-data-mgmt-services/seismic/-/issues2021-02-23T04:26:36Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/19e2e test: getGCSAccessToken API validates token type2021-02-23T04:26:36ZRucha Deshpandee2e test: getGCSAccessToken API validates token typeThe getGCSAccessToken API test script validates the return token type to be 'Bearer'.
For AWS the return type could be 'STS token'.
This validation should be removedThe getGCSAccessToken API test script validates the return token type to be 'Bearer'.
For AWS the return type could be 'STS token'.
This validation should be removedRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/20e2e test: Subproject Get New - checks return child length2021-02-23T04:24:39ZRucha Deshpandee2e test: Subproject Get New - checks return child lengthSubproject get new test script validates response child length. It is hardcoded to 8.
The length of the response can vary per CSP.
pm.expect(child.length).to.eql(8);Subproject get new test script validates response child length. It is hardcoded to 8.
The length of the response can vary per CSP.
pm.expect(child.length).to.eql(8);Rucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/21e2e test - Dataset exist / Dataset sizes validates a hardcoded list2021-03-04T22:50:06ZRucha Deshpandee2e test - Dataset exist / Dataset sizes validates a hardcoded listThis test validates a hardcoded list. Must change to environment variables OR the test script must be updated.
{
"datasets":[
"/async/dsx01",
"/a/b/c/dsx02",
"async/dsx03",
"test/dsx01",
"{{path01}}/{{dataset01}}"
]
}
Simil...This test validates a hardcoded list. Must change to environment variables OR the test script must be updated.
{
"datasets":[
"/async/dsx01",
"/a/b/c/dsx02",
"async/dsx03",
"test/dsx01",
"{{path01}}/{{dataset01}}"
]
}
Similarly, the Dataset Sizes test also validates the sizes for a hardcoded listRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/22e2e test script needs to run from repository root only2023-03-27T19:28:43ZRucha Deshpandee2e test script needs to run from repository root onlyThe run-e2e-tests.sh script has the following check. This will not work in internal pipelines where the distribution folder structure is different.
if [ ! -f "tsconfig.json" ]; then
printf "\n%s\n" "[ERROR] The script must be cal...The run-e2e-tests.sh script has the following check. This will not work in internal pipelines where the distribution folder structure is different.
if [ ! -f "tsconfig.json" ]; then
printf "\n%s\n" "[ERROR] The script must be called from the project root directory."
exit 1
fiRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/23createQuery and createKey - generalize structure2023-03-27T19:27:48ZRucha DeshpandecreateQuery and createKey - generalize structureThe following 2 methods
createQuery(namespace: string, kind: string): IJournalQueryModel;
createKey(specs: any): object;
The structure of the parameter should be abstracted to be s
AWS wants to be able to pass information such as
{...The following 2 methods
createQuery(namespace: string, kind: string): IJournalQueryModel;
createKey(specs: any): object;
The structure of the parameter should be abstracted to be s
AWS wants to be able to pass information such as
{
table_name:
tenant_name
subproject_name
..etc
}
of type 'any'.
This is required for AWS,as we are restricted to parse and use the 'Namespace', 'kind' which does not work in all scenarios for the models we have.Rucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-cpp-lib/-/issues/1devops: Dockerfiles do not have AWS SDK built in the base image2021-05-25T12:51:52ZRucha Deshpandedevops: Dockerfiles do not have AWS SDK built in the base imageThe base image required to build AWS artifacts do not include AWS SDKThe base image required to build AWS artifacts do not include AWS SDKRucha DeshpandeDiego MolteniRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/issues/1e2e tests: setup step must create the subproject2023-03-30T16:57:09ZRucha Deshpandee2e tests: setup step must create the subprojectThe e2e tests assume that a subproject exists. Just as some files are uploaded in the 'setup' step, the subproject must also be created as part of the setup step here.
https://community.opengroup.org/osdu/platform/domain-data-mgmt-servic...The e2e tests assume that a subproject exists. Just as some files are uploaded in the 'setup' step, the subproject must also be created as part of the setup step here.
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/blob/master/test/e2e/conftest.pyRucha DeshpandeDiego MolteniYunhua KoglinRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/24Azure Tests Failing for SDMS2021-03-09T22:02:01ZSumra ZafarAzure Tests Failing for SDMSTests are failing for AzureTests are failing for AzureSumra ZafarSumra Zafarhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/25Code linting AWS2021-03-23T16:43:04ZDiego MolteniCode linting AWScode linting to apply on aws code.
``$ tslint -c tslint.json 'src/cloud/providers/aws/**/*.ts'``code linting to apply on aws code.
``$ tslint -c tslint.json 'src/cloud/providers/aws/**/*.ts'``Rucha DeshpandeYunhua KoglinRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/26Code linting IBM2023-03-27T19:26:57ZDiego MolteniCode linting IBMcode linting to apply on ibm code.
``$ tslint -c tslint.json 'src/cloud/providers/ibm/**/*.ts'``code linting to apply on ibm code.
``$ tslint -c tslint.json 'src/cloud/providers/ibm/**/*.ts'``Walter DWalter Dhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/27AWS seismic store service ci cd testing yaml needs to be in ci cd repo2023-03-27T19:26:25ZDaniel PerezAWS seismic store service ci cd testing yaml needs to be in ci cd repoI have noticed that gitlab yaml for AWS testing has been included in seismic store service (https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/tree/master/devops/aws...I have noticed that gitlab yaml for AWS testing has been included in seismic store service (https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/tree/master/devops/aws), this file needs to be in CI CD repo https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/tree/master/
Please also follow standard and integrate in same yaml inside of cloud providers as we do for other providers https://community.opengroup.org/osdu/platform/ci-cd-pipelines/-/tree/master/cloud-providersRucha DeshpandeRucha Deshpandehttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/issues/2OAUTH ISSUE with SdUtil CLI2021-04-16T10:27:54ZAnuj GuptaOAUTH ISSUE with SdUtil CLIIn order to run this CLI app locally I had to do couple of minor changes as listed below to make it running successfully:
1. config.py -> to remove error for redirect_url not found, I added self.redirect_url to pick from config.yaml fil...In order to run this CLI app locally I had to do couple of minor changes as listed below to make it running successfully:
1. config.py -> to remove error for redirect_url not found, I added self.redirect_url to pick from config.yaml file.
1. login.py ->
* Error in os.chmod because of path wasnt present. token_file_name is replaced with token_file.
* during runtime key \['rv'\] was not found, replaced with \['url'\] which has the full constructed url.
have anyone tried running? & Did you face same errors? let me know If you have better suggestion so that it can be corrected.
MR: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/merge_requests/7Anuj GuptaYogesh ChinthaAnuj Guptahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/issues/3error: The "default" implementation has not been found.2021-06-02T13:55:59ZMikhail Davydenkoerror: The "default" implementation has not been found.I am trying to run seismic dms suite locally. While seismic-store-service runs correctly, I am not sure how to proceed with sdutil.
README file suggests to run the following command first:
`python3.8 sdutil config init`
But then it p...I am trying to run seismic dms suite locally. While seismic-store-service runs correctly, I am not sure how to proceed with sdutil.
README file suggests to run the following command first:
`python3.8 sdutil config init`
But then it produces the following message:
`The "default" implementation has not been found.`
Should I modify config.yaml manually? appreciate any information on how to configure it properlyhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-sdutil/-/issues/4IBM Documentation to configure and use sdutil python cli2022-08-23T11:19:20ZAnuj GuptaIBM Documentation to configure and use sdutil python cliIBM Documentation update to configure and use sdutil python cli
FYI @wladmirf @jingdongsunIBM Documentation update to configure and use sdutil python cli
FYI @wladmirf @jingdongsunAnuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-cpp-lib/-/issues/2Setting up and integrating SDAPI with IBM implementation2021-08-23T10:53:21ZWalter DSetting up and integrating SDAPI with IBM implementationTo continue discussion in the issue # 4 created in the deprecated project Seismic DMS. Lint to the old issue -
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms/-/issues/4To continue discussion in the issue # 4 created in the deprecated project Seismic DMS. Lint to the old issue -
https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms/-/issues/4https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/1vanilla checkout build fails on linux2019-12-20T08:47:12ZJackie Livanilla checkout build fails on linuxfails with:
```
open-vds/src/IO/IOManagerAzure.cpp:20:10: fatal error: was/common.h: No such file or directory
#include <was/common.h>
^~~~~~~~~~~~~~
compilation terminated.
src/CMakeFiles/openvds_objects.dir/build.make:127: ...fails with:
```
open-vds/src/IO/IOManagerAzure.cpp:20:10: fatal error: was/common.h: No such file or directory
#include <was/common.h>
^~~~~~~~~~~~~~
compilation terminated.
src/CMakeFiles/openvds_objects.dir/build.make:127: recipe for target 'src/CMakeFiles/openvds_objects.dir/IO/IOManagerAzure.cpp.o' failed
```https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/home/-/issues/1[Seismic DDMS] Deliver Seismic DDMS2021-06-15T21:24:53ZStephen Whitley (Invited Expert)[Seismic DDMS] Deliver Seismic DDMS**Objective**:
- Deliver an optimized bulk/brick accessor for seismic data to include open formats such as SEGY, OpenVDS and open ZGY formats.
- Provide type-safe accessors to seismic header entities.
**Details**:
- Integration with...**Objective**:
- Deliver an optimized bulk/brick accessor for seismic data to include open formats such as SEGY, OpenVDS and open ZGY formats.
- Provide type-safe accessors to seismic header entities.
**Details**:
- Integration with system services and impact of reference systems in particular – CRS, units, elevation references (including SRD). This is key to nail down even if we cant do conversions in R3, so the interfaces expose and consume standard FoR.
- Seismic DMS and bulk data handling rationalization with Schlumberger and Bluware – important that we can land one DMS for both Open VDS and ZGY.
- [Schlumberger] to complete contribution the ZGY specification and source code as an extension to the library and API documentation contributed in R2.M1 - Release 0.1CyrilPhil HodgsonCyrilhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/2Build Fixes for Fedora 312019-12-20T08:46:37ZAndrew KBuild Fixes for Fedora 31Add this as an issue since I don't appear to have access to submit a merge request.
I ran into a few problem when trying to build OpenVDS in Fedora 31. I've fixed the issues locally and have submitted my patch file for the master branch...Add this as an issue since I don't appear to have access to submit a merge request.
I ran into a few problem when trying to build OpenVDS in Fedora 31. I've fixed the issues locally and have submitted my patch file for the master branch get rid of the problems. These should still be ok for other distributions as well
[openvds_build.diff](/uploads/46da01da49937d8912060330583602de/openvds_build.diff)
- Set CMAKE_INSTALL_LIBDIR to lib${LIBSUFFIX} for Azure Storage SDK
* Azure Storage SDK does not use GNUInstallDir cmake include to
set the CMAKE_INSTALL_<dir> variables resulting in invalid LIBDIR
paths for distributions that use lib64. However, they provide a way
to override it which is what this change uses to set the correct path
- Add WERROR=OFF for cpprestsdk
* Warning about deprecated-copy when building with gcc 9. Causes
the build to fail if werror is enabled
- Remove const from dimensionDistribution
* uniform_real_distribution<float> call operator is not const which
causes an error when building with gcc 9https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/home/-/issues/2[Seismic DMS] to provide coverage for metadata2020-04-03T19:57:59ZCelina Marcolinocsilva10@slb.com[Seismic DMS] to provide coverage for metadataCreate proper metadata coverage to contemplate the following: survey/geometry definition, survey type, acquisition/processing headers, dataset header information, ...
Ensure we check datamodel from https://gitlab.opengroup.org/osdu/json...Create proper metadata coverage to contemplate the following: survey/geometry definition, survey type, acquisition/processing headers, dataset header information, ...
Ensure we check datamodel from https://gitlab.opengroup.org/osdu/json-schemas.https://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