Add allow-no-env option in RMS job config

equinor · Oct 23, 2020 · 9b72ec5 · 9b72ec5
1 parent 6d56529
commit 9b72ec5
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 2 deletions.
diff --git a/share/ert/forward-models/docs/examples/RMS.rst b/share/ert/forward-models/docs/examples/RMS.rst
@@ -30,3 +30,9 @@ Optional arguments:
                         the prefix of all relative paths when rms is exporting
   -v, --version VERSION
                         the prefix of all relative paths when rms is exporting
+  -a, --allow-no-env
+                        Boolean flag to allow RMS to run without a site configured
+                        environment. WARNING: This is typically a sign of using an
+                        unsupported version of RMS and the configuration of the
+                        environment is now entirely on the shoulders of the user.
+                        Consider contacting your system administrators.
diff --git a/share/ert/forward-models/old_style/RMS b/share/ert/forward-models/old_style/RMS
@@ -4,7 +4,7 @@ DEFAULT       <RMS_IMPORT_PATH> ./
 DEFAULT       <RMS_EXPORT_PATH> ./
 DEFAULT       <RMS_RUNPATH>     rms/model
 TARGET_FILE   <RMS_TARGET_FILE>
-ARGLIST <IENS>  <RMS_PROJECT> <RMS_WORKFLOW> -r <RMS_RUNPATH> -t <RMS_TARGET_FILE> -i <RMS_IMPORT_PATH> -v <RMS_VERSION> -e <RMS_EXPORT_PATH>
+ARGLIST <IENS>  <RMS_PROJECT> <RMS_WORKFLOW> -r <RMS_RUNPATH> -t <RMS_TARGET_FILE> -i <RMS_IMPORT_PATH> -v <RMS_VERSION> -e <RMS_EXPORT_PATH> <RMS_OPTS>
 
 EXEC_ENV PYTHONPATH <RMS_PYTHONPATH>
 EXEC_ENV PATH_PREFIX <RMS_PATH_PREFIX>
diff --git a/share/ert/forward-models/res/script/rms b/share/ert/forward-models/res/script/rms
@@ -55,7 +55,7 @@ def _build_argument_parser():
     parser.add_argument(
         '-a', '--allow-no-env',
         action="store_true",
-        help='Allow rms to run with out environment specified in rms configuration',
+        help='Allow RMS to run without a site configured environment',
     )
     return parser