dcslagel / las-util-cpp Goto Github PK

Remove Las3 files for now because the goals for this tool are currently to focus on the Las2 specification.

Currently the compiler is hard-coded in the makefile.

• Change so individuals can set up various compiler configurations and control which one is used in a build action.

Current compilers are clang and gcc.

Complete in commit d730aa0

Use LasHeader for parsing ~Well, ~Curve and ~Param. Replace LasWell and LasParam with LasHeader.

Description:

Currently lasUtil -h displays Las 3.0 options, change it to display Las 2.0 options because Las 2.0 is the current roadmap focus.

Current display:

Usage: lasUtil -f <las_filename> [-p <sections_to_print>]
 
- Sections to print:
  Specify which sections to display by listing the letters following '-p'
  Example:
  lasUtil -f myfile -p vw
    Letter  : Section
    v       : Version Information Section
    w       : Well Information Section
    p       : Log Parameter Section
    d       : Log Definition Section
    e       : Drilling Definition Section
    a       : Drilling Data Section

Proposed display:

Current display:

Usage: lasUtil -f <las_filename> [-p <sections_to_print>]
 
- Sections to print:
  Specify which sections to display by listing the letters following '-p'
  Example:
  lasUtil -f myfile -p vw
    Letter  : Section
    v       : Version Information Section
    w       : Well Information Section
    c       : Curve Section
    p       : Parameter Section
    o       : Other Section
    a       : Drilling Data Section

Resolved 58397f2 Update roadmap, add info on 0.0.3 planning

Explore options for adding a simple alpha level gui interface:

• import file
• display metadata

• Design a structure to hold the ~A data section information.
• Add basic data section parsing
• Add basic data section tests

Add a REPL/server loop.

Example

$ las-util-cpp --repl
> help
...
> read examples/sample_2.0.las
> version
"VERS", "", "2.0", "CWLS LOG ASCII STANDARD -VERSION 2.0"
> quit
$

Currently we don't have any testing or test automation.

• Research test tools.
• Adopt one or write something simple.
• Add initial test

• Create build dir with build/rel targets
• Create a project local bin for initial install command.
• Document Makefile sections
• Rename makefile to Makefile

Adopt Petroware's Apache-2 open-source licensed Log-Ascii-Standard to Json schema.
https://jsonwelllogformat.org
https://jsonwelllogformat.org/schemas/JsonWellLogFormat.json
https://github.com/JSONWellLogFormat/JSONWellLogFormat

• Create a command flag for outputting parsed LAS into LAS-JSON.
• Make Initial output functions to output simply the VERSION section.