Skip to content
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

Emulate ERT/FMU runtime #42

Closed
wants to merge 1 commit into from
Closed

Emulate ERT/FMU runtime #42

wants to merge 1 commit into from

Conversation

perolavsvendsen
Copy link
Member

@perolavsvendsen perolavsvendsen commented Feb 28, 2024

A possible solution to #41

Adding a development option/tool that emulates ERT, by setting key environment variables.

sim2sumo runs as a subprocess of an FMU workflow, invoked by ERT. ERT sets some key environment variables, which fmu-dataio (and potentially others) use to determine if context is FMU runtime or not. This feature enables a developer to recreate the same environment during development, i.e. when invoking sim2sumo directly from the command line.

The feature is invoked with the --emulate_ert flag.

(Also fixed some typos.)

Copy link
Contributor

@equinor-ruaj equinor-ruaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I'm fully on board with adding this as part of the main script.
For us as Sumo, if we do not want users to manually upload data, then I think --emulate-ert should be moved to a separate tool. Could still be in the same repo, but not a direct part of sim2sumo.

Copy link
Contributor

@daniel-sol daniel-sol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I at least partially agree with @equinor-ruaj's comment, but end of the day it depends on two things:

  1. There are situations when a developer might want to run sim2sumo without ert, how should that be run without too much fuss?
  2. Are there situations when the nightly testing that we are running/want to run need some sort of functionality like this. What is required in such a situation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants