You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an example when we have an undefined branch exists in Case (or input file). An example here the YO well is defined as two branches in input file, but the schedule file only defined one branch.
This happens when running uncertainty analysis, one branch is not produced by pre-processor but the user expects it to be produced while making Completor case file.
To Reproduce
Rerun Completor with attached files
Expected behavior
Described below
The text was updated successfully, but these errors were encountered:
Case file: input_test.txt
Schedule file: test_1.txt
Expected behavior: Completor will exit and give error message saying that the case file defines 2 branches and schedule file only has 1 branch. Missing branch number 2.
Another example is the inverse from first case within the same case_file input_test.txt test_2.txt
In this example, the schedule file defines only Branch number 2, where the branch number 1 is missing.
Expected behavior: Completor will exit and give error message saying that the case file defines 2 branches and schedule file only has 1 branch. Missing branch number 1.
hrsut
changed the title
Proper error message on undefined branch
Proper error message on missing branch in schedule files
May 13, 2024
hrsut
changed the title
Proper error message on missing branch in schedule files
Error message on missing branch in schedule files
May 13, 2024
This is an example when we have an undefined branch exists in Case (or input file). An example here the
YO
well is defined as two branches in input file, but the schedule file only defined one branch.This happens when running uncertainty analysis, one branch is not produced by pre-processor but the user expects it to be produced while making Completor case file.
To Reproduce
Rerun Completor with attached files
Expected behavior
Described below
The text was updated successfully, but these errors were encountered: