Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • O Open VDS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Upcoming Change to GitLab Pages The GitLab Pages URL is planned to migrate from the current *.pages.community.opengroup.org to a simpler domain: *.pages.opengroup.org. At the same time, HTTPS will be enabled for the server. This change is planned for May 21, 2022.

If you have questions or concerns, please email forum-support@opengroup.org.

  • Open Subsurface Data Universe Software
  • Platform
  • Domain Data Mgmt Services
  • Seismic
  • Open VDS
  • Issues
  • #103

Closed
Open
Created Dec 15, 2021 by Paal Kvamme@kvamme3

Dimension and Produce

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.

Assignee
Assign to
Time tracking