Skip to content
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.

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

Issue with ' #5615

Open
user151617181910 opened this issue Sep 17, 2024 · 2 comments
Open

Issue with ' #5615

user151617181910 opened this issue Sep 17, 2024 · 2 comments

Comments

@user151617181910
Copy link

user151617181910 commented Sep 17, 2024

Hi!

In the run of the model there was an error:

[/mnt/e/RS/CB/CB03/opm-common/src/opm/io/eclipse/EclUtil.cpp:365] Header name and type should be enclosed with '
[/mnt/e/RS/CB/CB03/opm-common/src/opm/io/eclipse/EclUtil.cpp:365] Header name and type should be enclosed with '

An error occurred while creating the reservoir properties
Internal error: [/mnt/e/RS/CB/CB03/opm-common/src/opm/io/eclipse/EclUtil.cpp:365] Header name and type should be enclosed with '

Unrecoverable errors while loading input: [/mnt/e/RS/CB/CB03/opm-common/src/opm/io/eclipse/EclUtil.cpp:365] Header name and type should be enclosed with '

Can you help me to solve this issue? What could be the reason of it? If it needs, I can attach the .zip of the model.

@bska
Copy link
Member

bska commented Sep 17, 2024

Hi,

I'm guessing that your model has an IMPORT or GDFILE statement that tries to load a formatted result file, e.g., a grid file with the extension .FEGRID or a property array like PORO or SOWCR. The diagnostic you're seeing is typically emitted when we're trying to load such arrays and we can't quite match the expected structure to the actual input. This could be a problem in our formatted array readers–those don't really get exercised a whole lot–or it could be a problem with the input files. Without more information it's hard to know exactly what the underlying cause is here.

If it needs, I can attach the .zip of the model.

That might indeed help. If the model is confidential you can share it by e-mail or through other means if you'd like. My e-mail address is Bard.Skaflestad@sintef.no.

@bska
Copy link
Member

bska commented Sep 18, 2024

Thank you for sharing the model. As far as I can tell there are two main problems, one smaller and one larger

  1. Our input reader fails to recognise that the .GRID input file used in the GDFILE keyword is unformatted/binary. This is the direct cause of the "Header name and type should be enclosed with '" diagnostic since the reader then expects formatted/text input and that should have a certain structure involving quote characters.
  2. The simulator does not have a grid constructor for the .GRID format.

Problem 1 is the smaller of these two, and we address that in PR OPM/opm-common#4210. I expect the fix will be available in the next public release of the simulator. Problem 2, however, is bigger. It manifests through diagnostics like

Creating grid from: CASE_GRID.GRID 

Error: 
An error occurred while creating the reservoir properties
Internal error: file: CASE_GRID.GRID is not a valid egrid file, GRIDHEAD not found

Error: Unrecoverable errors while loading input: file: CASE_GRID.GRID is not a valid egrid file, GRIDHEAD not found

If you're able to re-export your grid geometry in corner-point format, i.e., as a .EGRID file containing COORDS and ZCORN keywords then that would be my suggested workaround for the problem. Sadly, I don't expect we'll have the resources to implement a construction procedure for our simulation grid based on .GRID-style inputs in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants