-
Notifications
You must be signed in to change notification settings - Fork 31
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
Capillary entry pressure #298
Comments
The first issue should probably be solved elsewhere, as it is hard for pyscal to correctly error hard on input that gives extreme output. Emitting a warning has probably no effect (?). Pyscal only handles numerical values, it does not know which units are in use. For the second issue, I don't get precisely what you mean. Example input and output? |
I have tried to illustrate in the pptx enclosed. The issue is that for Sw=1 the Pc should be zero (but not always). Pc-curves get scaled and what looks like a negligible entry pressure becomes large after initialization. Regarding the first issue: you are probably right that a warning among zilion other warnings in Eclipse and FMU will not make an impression on the users. However, you have some assumption about units since you use gravity in SI units, as a standard- or? |
The simplified J-function does not yield zero at |
The documentation of the |
Should this issue be kept open? |
When I open simulation projects, especially in FMU settings, that has used pyscal to generate saturation table the Pc-curves is often quite unrealistic. and contains large entry pressures. This seems to have become a company challenge.
The first issue is maybe a user fault, but isn't it possible to create a test so that PC doesn't go to hundreds of bars.
The second issue is that Pc <> 0 bar @ Sw=1. There might be entry pressures in the system but often its just a result of automatic workflow.
The text was updated successfully, but these errors were encountered: