Replace interface towards eclrun and flow using fmstep_config#9108
Replace interface towards eclrun and flow using fmstep_config#9108berland merged 1 commit intoequinor:mainfrom
Conversation
33a19a8 to
2cafdf4
Compare
272dc33 to
a771236
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9108 +/- ##
==========================================
- Coverage 91.74% 91.72% -0.02%
==========================================
Files 426 426
Lines 26518 26509 -9
==========================================
- Hits 24328 24316 -12
- Misses 2190 2193 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
a71adc2 to
9b2377a
Compare
236da1f to
a1452e3
Compare
433974a to
a5663d5
Compare
CodSpeed Performance ReportMerging #9108 will not alter performanceComparing Summary
|
92fa474 to
87124b2
Compare
8a627e1 to
9768644
Compare
| - well_constraints -i files/well_readydate.json -c files/wc_config.yml -rc well_rate.json -o wc_wells.json | ||
| - add_templates -i wc_wells.json -c files/at_config.yml -o at_wells.json | ||
| - schmerge -s eclipse/include/schedule/schedule.tmpl -i at_wells.json -o eclipse/include/schedule/schedule.sch | ||
| - myflow r{{ eclbase }} --enable-tuning |
There was a problem hiding this comment.
In this PR, support for arbitrary options forwarded to flow is not included (yet?)
There was a problem hiding this comment.
This is now fixed. But --enable-tuning was changed to --enable-tuning=true as the former was not supported by todays version of flow.
d04533b to
34e64cd
Compare
|
TODO: |
60affca to
42b2df8
Compare
Fixed. |
0402921 to
3c75afd
Compare
This replaces the yaml configuration file for Eclipse100/300 with a set of environment variables set through the plugin system. Ert cannot any longer start the raw Eclipse binary itself, it depends on the vendor supplied wrapper binary called "eclrun". Similarly, for OPM flow, Ert will now support a wrapper script "flowrun" if it is present, assuming it has a similar command line API as eclrun. If flowrun is not present, it will look for a binary "flow" in $PATH which can be used, but then only with single-cpu possibilities. Users can point to a custom location of eclrun by adding SETENV to the configuration file.
3c75afd to
caa16b6
Compare
sondreso
left a comment
There was a problem hiding this comment.
This is very nice, excellent job! 👏
I think we should add documentation for the forward_model_configuration under https://ert.readthedocs.io/en/latest/getting_started/howto/plugin_system.html, could you create an issue for this? This is fine to address in a separate PR!
Issue
Resolves #8925
git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')When applicable