-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fatal error processing COPY keyword. #1115
Comments
OK - I think the problem is that the COPY
'MULTNUM' 'FIPNUM' 1* 1* 1* 1* 1* 1* / CREATE FIPNUM
/ the parser expects the source keyword - i.e. COPY
'PERMX' 'PERMY' /
/ to be a user error if the |
@joakim-hove The MULTNUM keyword is defined in the GRID section, so it should be available in the REGIONS section to duplicate Eclipse's behavior. So this is a bug as the array is defined. I agree the work around is straight forward, but we should try to fix this if we can. Most engineers will just take their existing Eclipse decks and run them with OPM Flow to compare the results, if there are too many issues they will just give up. |
OK - I agree. I understand what the bug is - slightly uncertain about the fix. |
This: #1116 should have fixed the |
How do I to get the binary - I'm not a developer so I don't have a build system. |
continuous deployment is on the road map, but it is not there right now. i can quickly build some packages for you, which platform ? |
DISTRIB_ID=Ubuntu |
took a bit longer than anticipated. due to substantial changes in libecl and opm-parser since last release i had to butcher packaging somewhat. thus these packages have not gone through my usual quality control, but i think they should do the job. for this reason i did not want to push them to a ppa, we do not want others using these by accident. note you have to remove the stable packages before install, it will NOT update cleanly (due to things above and i had to cut some corners). there is no upscaling package as that shouldn't be needed here. i have sent a dropbox link to your gmail with the tarball.
note the packages are unsigned so it may complain about that. you will also have to manually remove these before you can reinstall the stable packages. |
@qkva2: When I go to extract the tar file I get this error:
|
Found it wrong filename, :-) |
heh, sorry about that. doing non-norwegian dates is hard for me ;) |
@akva2: I re-ran my test case with the new version as shown below:
But the run still does not run and still does not produce a PRT or DBUG file. |
OK - I must admit I thought this was more of a simulator problem than anything else; but maybe this is staill about the parser. Good if you can provide any error messages, or run flow in the debugger:
|
Joakim,
|
OK - that was really brutal - can you share the input deck |
Yep, I thought you might say that. Unfortunately, I cannot share the model as it is a client's model and I'm under a CA. If you know where this is happening and you wish to pursue this further, then if you put some debug in the code and send me a new version of Flow then I'll run it with the deck again. If you could write out the messages as the deck is being processed for example, then may be we can find which keywords are causing the problem and then may be I can build a test case with same issue. At the moment I have no idea what is causing this. |
I am afraid it necessary to be able to reproduce the problem in order to fix it. Sharing datasets is always very challenging since they are conceived as valuable and proprietary to the owner. However, I do believe it is possible to get around it. @OPMUSER since you have already identified the offending keyword, are you able to create a dummy deck (which is unproblematic to share) based on that keyword, or combination of keywords, that reproduces the bug? Sorry to impose this burden on you, but I am afraid that will be necessary here. Moreover, such test decks are very welcome to our test-suite. |
Fatal error processing COPY keyword. when trying to copy MULTNUM in REGIONS section, using the following keywords:
Note when running in parallel mode this causes a segmentation fault with no warning messages, if one then runs the same deck in serial mode one sees the message - see the attached file.
PAS-P50-C55.zip
The text was updated successfully, but these errors were encountered: