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

OBS utility has trouble parsing boundname if it starts with an integer #598

Open
langevin-usgs opened this issue Nov 27, 2020 · 0 comments

Comments

@langevin-usgs
Copy link
Contributor

User reports:
It seems the GitHub version allows either mawno or boundname for ID for the observation package in MWT, as in the documentation. The faster version you sent only allows mawno for ID; it choked on the boundname. I got it to work in both executable versions by changing the ID to mawno.

Then later reports:
The boundnames I was using started with a digits, so perhaps they were being interpreted as mawno in the Intel version, which choked with the first two characters exceeded the number of maw wells.

This suggests that the code for determining if mawno is a string or an integer is compiler dependent when mawno (and probably any boundname anywhere) starts with a number.

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

1 participant