opm-common icon indicating copy to clipboard operation
opm-common copied to clipboard

Support UDA and restart for RESV control in GCONPROD

Open vkip opened this issue 9 months ago • 1 comments

vkip avatar Mar 04 '25 09:03 vkip

jenkins build this failure_report please

vkip avatar Mar 04 '25 09:03 vkip

jenkins build this please

vkip avatar May 09 '25 14:05 vkip

jenkins build this failure_report please

GitPaean avatar May 10 '25 06:05 GitPaean

The single test failure is to be expected (due to now writing the RESV value in GCONPROD).

vkip avatar May 12 '25 08:05 vkip

The single test failure is to be expected (due to now writing the RESV value in GCONPROD).

Thanks. The simulation results are untouched by the PR, while it is indeed more restart data was written in the RST file,

I am not following where the value 1.0000000e+20 comes from, @vkip , do you have a understanding?

	SGRP: Restart, sequence 11
		Fails for 2 entries
		Largest absolute error: 1.0000000e+20
		Largest relative error: 1.0000000e+00

Others probably can review the PR more efficiently than me, so I am delegating this to @bska . I will review this if it does not work.

GitPaean avatar May 12 '25 10:05 GitPaean

am not following where the value 1.0000000e+20 comes from

1.0e+20 is a sentinel value that, in SGRP and a few other arrays, means "no limit". Prior to this PR we did not emit targets/limits for GCONPROD/RESV so we would always write this sentinel value for the RESV limit at the group level. This PR ensures that we write the correct value of 1000 for the RESV limit. In other words, the regression failure is expected.

bska avatar May 12 '25 11:05 bska

jenkins build this update_data please

bska avatar May 12 '25 11:05 bska

Prior to this PR we did not emit targets/limits for GCONPROD/RESV so we would always write this sentinel value for the RESV limit at the group level. This PR ensures that we write the correct value of 1000 for the RESV limit. In other words, the regression failure is expected.

Thanks for pointing to the following,

   'F'    'RESV'  4* 'RATE'  NO 5* 1000 /

I did not spot it. But I did not see the 1000 showing up in the regression failure report. https://ci.opm-project.org/job/opm-common-PR-builder/8384/testReport/(root)/mpi/compareECLFiles_flow_SPE9_CP_GROUP_RESV/ or it is too small against 1.e+20 to show up?

GitPaean avatar May 12 '25 11:05 GitPaean

I did not see the 1000 showing up in the regression failure report.

It's there, but you need to read the full comparison, not just the summary at the end:

[...]

Unified restart files, sequence  11

Comparing SEQNUM ...  done.
Comparing INTEHEAD ...  done.
Comparing LOGIHEAD ...  done.
Comparing DOUBHEAD ...  done.
Comparing IGRP ...  done.
Comparing SGRP ... 

Keyword: SGRP, origin Restart, sequence 11

Value index                 = 147
(first value, second value) = (1e+20, 1000)

Keyword: SGRP requires strict tolerances.
[...]

bska avatar May 12 '25 11:05 bska

I did not see the 1000 showing up in the regression failure report.

It's there, but you need to read the full comparison, not just the summary at the end:

[...]

Unified restart files, sequence  11

Comparing SEQNUM ...  done.
Comparing INTEHEAD ...  done.
Comparing LOGIHEAD ...  done.
Comparing DOUBHEAD ...  done.
Comparing IGRP ...  done.
Comparing SGRP ... 

Keyword: SGRP, origin Restart, sequence 11

Value index                 = 147
(first value, second value) = (1e+20, 1000)

Keyword: SGRP requires strict tolerances.
[...]

That is correct. Thanks.

GitPaean avatar May 12 '25 11:05 GitPaean

jenkins build this update_data please

bska avatar May 12 '25 11:05 bska

jenkins build this opm-tests=1340 please

bska avatar May 12 '25 13:05 bska