You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: