Comments (7)
I understand now what Anders said about having "WSTAT" in the summary anyhow, I can add a warning there specifying that the default value will be imposed. So we want "CLOSED" as the default?
from flownet.
Maybe we should simply throw a RuntimeError
in FlowNet if WSTAT
is not in the given input model (since we basically depend on it existing)? Then it will be clear for the user how to fix the input model, and get FlowNet to proceed (with correct behavior of well status).
from flownet.
I agreed,
from flownet.
I'm able now to determine if there any WSTAT = NaN by asking
if df_production_data["WSTAT"].isna().any():
raise RuntimeError(f"The status of each well must be define (OPEN, SHUT, STOP). Please add keyword WSTAT in the SUMMARY section of eclipse case.")
else:
df_production_data["WSTAT"] = df_production_data["WSTAT"].map(
{
1: "OPEN", # Producer OPEN
2: "OPEN", # Injector OPEN
3: "SHUT",
4: "STOP",
5: "SHUT", # PSHUT
6: "STOP", # PSTOP
np.nan: "STOP",
}
)
However, I add WSTAT inside the summary section of my eclipse file and flownet doesn't read the corresponding well status WSTAT :( Where do I add WSTAT on my eclipse file?
from flownet.
Adding WSTAT
in SUMMARY
should be enough, however, Flow does not support it as of today so the input case has to be run with Eclipse. Could that be the reason?
from flownet.
Yes that's the reason then
from flownet.
I now ran into the same problem with Norne it looks like.
from flownet.
Related Issues (20)
- Unexpected behaviour for very simple box-type models
- Layer-based attribution of water and oil phase volumes to FlowNet HOT 2
- Add well connection factors as HM parameter HOT 4
- Refactor _simulation_keywords.py
- Problems running Norne with tracers with OPM-Flow
- Support I,J,K-based definition of fault segment orientation
- Brine should be better specified under phases item in input yml file
- Treatment of duplicate wells HOT 3
- Valid FlowNet without additional nodes and removal of well nodes
- Export FlowNet predictions required for ML workflow
- Check if FlowNet still runs smoothly with LSF
- Processing of schedule information taking too long
- Incorrect initialization of saturations
- Allow for specifying grid properties
- Coarse 3D grids: a general discussion
- combine options for additional node placement
- Support ert option ensemble_experiment
- Read existing network and schedule from file
- Possible inconsistency in region numbering
- Zero-rate measurements not used
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flownet.