Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • Wellbore Domain Services Wellbore Domain Services
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • 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
  • Open Subsurface Data Universe Software
  • Platform
  • Domain Data Mgmt Services
  • Wellbore
  • Wellbore Domain ServicesWellbore Domain Services
  • Issues
  • #4
Closed
Open
Created Feb 21, 2020 by Stephen Whitley (Invited Expert)@stephenwhitley

[Wellbore DDMS] Deliver the WellBore DDMS

Objective:

  • Define the Wellbore Domain Management Service (DDMS) to cover the well, wellbore, LogSet, Log data objects initially available in R2 and provide type-safe APIs and optimized bulk accessors for array data (logs, trajectories).

Detailed Scope: The Wellbore Domain Data Management Service will deliver type-safe entity access and optimized accessors for bulk data such as logs, trajectories, checkshots. The scope for the R3 delivery will be API's for the following data entities: Wellbore, Logset and Log.

  • A valid Logset is a group of logs with a common reference. The values for the reference need to be in decreasing order.
  • A valid Log is a series of numerical values (no support today for alphanumeric logs) in n columns.
Edited Mar 30, 2020 by Dror Dahan
Assignee
Assign to
Time tracking