Fail to compile opm-simulator-202210?

[lj-cug]

I have built opm-simulator-202110 successfully, but I fail to compile opm-simulator-202210. The opm-common (202210), etc. are built successfully. The compilation error showed that:

[ 33%] Building CXX object CMakeFiles/opmsimulators.dir/opm/simulators/linalg/ExtractParallelGridInformationToISTL.cpp.o
/home/lijian/open-geo-modeller-build/OPM/202210/opm-simulators/opm/simulators/linalg/ExtractParallelGridInformationToISTL.cpp: In function ‘void Opm::extractParallelGridInformationToISTL(const Dune::CpGrid&, std::any&)’:
/home/lijian/open-geo-modeller-build/OPM/202210/opm-simulators/opm/simulators/linalg/ExtractParallelGridInformationToISTL.cpp:40:31: **error: ‘ParallelISTLInformation’ is not a member of ‘Opm’**
   40 |         anyComm=std::any(Opm::ParallelISTLInformation(Dune::stackobject_to_shared_ptr(idx),

[bska]

Hi,

That diagnostic message suggests that there's no declaration of class ParallelISTLInformation in scope, but looking at the code the appropriate #include<> statement is in place and has been there since May of 2019. Without some additional information it is hard to speculate on what the underlying problem could be.

On a second note, OPM version 2022.10 is getting a bit out of date by now. We expect to release version 2023.10 in late October of this year, so unless you have a good reason to stick with the older version I suggest you consider using the latest public release–2023.04–and upgrade that to 2023.10 when that release becomes available.

[lj-cug]

Thanks for your reply. I have also installed OPM-202304 using pre-builts binaries in Ubuntu, but it cannot be run with Norne example and my own project from Petrel-2013 software, some keywords cannot be read or run using OPM-202304. Fortunately, I can run Norne and my own project using OPM-202110, although it's obsolete. Actually I check the header and source code for OPM-202210, but the above compilation errors happened to build opm-simulators-202210 after successfully building all the other necessary packages. After considering the input deck file, the solvers can be selected and the functionality of OPM, I decided to use OPM-202110.

[lj-cug]

Thanks for your reply. I have also installed OPM-202304 using pre-builts binaries in Ubuntu, but it cannot be run with Norne example and my own project from Petrel-2013 software, some keywords cannot be read or run using OPM-202304. Fortunately, I can run Norne and my own project using OPM-202110, although it's obsolete. Actually I check the header and source code for OPM-202210, but the above compilation errors happened to build opm-simulators-202210 after successfully building all the other necessary packages. After considering the input deck file, the solvers can be selected and the functionality of OPM, I decided to use OPM-202110.

[bska]

Thanks for your reply. I have also installed OPM-202304 using pre-builts binaries in Ubuntu, but it cannot be run with Norne example and my own project from Petrel-2013 software, some keywords cannot be read or run using OPM-202304.

Hi,

For what it's worth, the simulator's parser became a lot more strict in version 2023.04, and that strictness is likely to continue in future releases of the simulator. We didn't want the simulator to silently accept models and then perform subtly or not-so-subtly different actions to what the engineer expected. If you're getting a lot of "unsupported keyword" diagnostics, followed by a message of the form

Error: Unrecoverable errors while loading input:

then you can try to pass the command line parameter

--parsing-strictness=low

when invoking the simulator. That will tell the simulator to ignore unsupported keywords at the input stage and to continue the run. Please be aware, however, that you still won't get the expected behaviour from those keywords.

[bska]

have also installed OPM-202304 using pre-builts binaries in Ubuntu, but it cannot be run with Norne example

Oh, I didn't pay enough attention to that statement. The NORNE_ATW2013 data set is probably the one that gets used the most in testing and developing the simulator so if that one does not run, then there's a problem somewhere. That said, we did have to disable some unsupported Norne features as part of making the parser more strict, so maybe you just need to do the same on your end. Alternatively, you may just download the data set again and use the new version that we've prepared.