opm-simulators/opm/simulators/flow/python/Pybind11Exporter.hpp

#ifndef OPM_PYBIND11_EXPORTER_HEADER_INCLUDED
#define OPM_PYBIND11_EXPORTER_HEADER_INCLUDED

#include <pybind11/pybind11.h>
#include <pybind11/numpy.h>
#include <pybind11/stl.h>
//#include <pybind11/embed.h>

namespace py = pybind11;

namespace Opm::Pybind {
    void export_all(py::module& m);
    void export_PyBlackOilSimulator(py::module& m);
}

#endif //OPM_PYBIND11_EXPORTER_HEADER_INCLUDED
Initialize blackoil simulator from schedule shared with Python. Adds a new constructor to Main.hpp that takes shared pointers to Deck, EclipseState, Schedule, and SummaryConfig. This makes it possible to share these variables with Python without worrying about lifetime issues of the underlying C++ objects. For example, a Python script can first create an opm.io.schedule.Schedule object which is modified from Python. Then, assume the same Python script creates an opm.simulators.BlackOilSimulator which is initialized with the same schedule object. Since the underlying C++ object is a shared pointer, the Schedule object in Python may go out of scope (get deleted by Python) without having the C++ schedule object being deleted. And the Python BlackOilSimulator may continue to be used after the Python Schedule object has been deleted since it still has a valid C++ schedule object. 2021-09-20 18:13:39 -05:00			`#ifndef OPM_PYBIND11_EXPORTER_HEADER_INCLUDED`
			`#define OPM_PYBIND11_EXPORTER_HEADER_INCLUDED`

			`#include <pybind11/pybind11.h>`
			`#include <pybind11/numpy.h>`
Get primary variables and fluid state from Python Added methods to Python module opm.simulators.BlackOilSimulator to access primary variables and fluid state variables. 2023-10-26 05:29:06 -05:00			`#include <pybind11/stl.h>`
Initialize blackoil simulator from schedule shared with Python. Adds a new constructor to Main.hpp that takes shared pointers to Deck, EclipseState, Schedule, and SummaryConfig. This makes it possible to share these variables with Python without worrying about lifetime issues of the underlying C++ objects. For example, a Python script can first create an opm.io.schedule.Schedule object which is modified from Python. Then, assume the same Python script creates an opm.simulators.BlackOilSimulator which is initialized with the same schedule object. Since the underlying C++ object is a shared pointer, the Schedule object in Python may go out of scope (get deleted by Python) without having the C++ schedule object being deleted. And the Python BlackOilSimulator may continue to be used after the Python Schedule object has been deleted since it still has a valid C++ schedule object. 2021-09-20 18:13:39 -05:00			`//#include <pybind11/embed.h>`

			`namespace py = pybind11;`

			`namespace Opm::Pybind {`
			`void export_all(py::module& m);`
			`void export_PyBlackOilSimulator(py::module& m);`
			`}`

			`#endif //OPM_PYBIND11_EXPORTER_HEADER_INCLUDED`