-
Notifications
You must be signed in to change notification settings - Fork 19
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
DisableControl() and compute_well_qoi #73
Comments
I think there might be a subtle issue here where the disabled control will return a zero value for BHP. I think if you retrieve the BHP manually it will work: bhp = first(state[:Observation_1].Pressure) Going via the QOI code is not necessary in this case, since it does not make too much sense for observational wells. You could also skip adding the observation well and instead do |
Thank you for your response. My main point was that using the L2 norm as an objective function for observation wells helps to match more observed data, which is why I’m using the I found a workaround by setting the observation well as a producer and disabling the rate (idk if this is more appropriate), which allows me to obtain the gradient values (and not just zero values). However, as you suggested, accessing something like Thanks again! |
I think both approaches will yield the same result, the main issue is that |
Hi Olav,
I'm trying to create an observation well to later use in an objective function alongside
BottomHolePressureTarget
. Based on previous discussions (in the issues thread with other user), you suggested usingDisabledControl()
to set up an observation well. However, when I implement the following and attempt to obtain the gradients, they come out as zero:On the other hand, if I set the observation well with
ProducerControl
andDisabledTarget()
(or set the target to zero), my gradient values are non-zero following the same objective function as before.Could you please comment on whether the objective function is correctly set when using an observation well? or Are there any other potential issues or considerations I should be aware of?
The text was updated successfully, but these errors were encountered: