8000 binary_parser.py will not work with INTERSECT output · Issue #1 · f0nzie/rEcl · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

binary_parser.py will not work with INTERSECT output #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
SSimonTemplar opened this issue Aug 22, 2022 · 0 comments
Open

binary_parser.py will not work with INTERSECT output #1

SSimonTemplar opened this issue Aug 22, 2022 · 0 comments

Comments

@SSimonTemplar
Copy link
SSimonTemplar commented Aug 22, 2022 •
edited
Loading

In the SMSPEC file, the NAMES keyword is used instead of WGNAMES between Petrel and INTERSECT to support names longer
than 8 characters and extended names (Like networks, branches, multisegmented wells and region properties tied to region families.

To support multiple networks, network node and branch names are prefixed with the network name separated with ":". For properties on named completions and segmented well devices the device or completion name is prefixed by the well name separated with ":". For region properties the region name is prefixed by the region family name separated by ":" — this is addition to the numerical region number.

The current code in binary_parser.py only identifies WGNAMES:

wgnames = byte2str(EclArray(smspec, keyword='WGNAMES', with_fakes=True).array)

Changing the line to 'NAMES' will not fix the issue as the data type for this keyword is 'C0##', where ## is the size of the char field. The current python script only allow for a CHAR type size.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SSimonTemplar
0