Skip to content
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

Add Connection Fracturing Statistics Summary Vectors #4388

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bska
Copy link
Member

@bska bska commented Dec 18, 2024

This commit adds support for collecting and reporting the following set of connection level fracturing statistics measures

  • CFR<Q>MAX – Maximum value of connection level fracturing quantity <Q>
  • CFR<Q>MIN – Minimum value of connection level fracturing quantity <Q>
  • CFR<Q>AVG – Arithmetic average of connection level fracturing quantity <Q>
  • CFR<Q>STD – Unbiased standard deviation of connection level fracturing quantity <Q>

The currently supported quantities (<Q>) are

  • P – Fracture pressure
  • IR – Injection flow rate
  • WD – Fracture width

These vectors adhere to the common connection level summary vector specification whence

CFRPMAX
  'I1' 16 16 6 /
/

CFRIRAVG
  'I1' * /
/

CFRWDSTD
  * * /
/

will report the maximum pressure across all cells intersected by a fracture originating in connection (16,16,6) of well I1, one average value for each connection of well I1 with the average being taken over all cells intersected by the fraction originating at that connection and, finally, the standard deviation of the fracture width for each connection of each well with each standard deviation being calculated over all cells intersected by the fracture originating at that connection.

@bska
Copy link
Member Author

bska commented Dec 18, 2024

I am creating this PR in a draft state for two reasons

  1. It depends on, and contains, the earlier PR Add Infrastructure for Geomechanical Simulations and Formation Damage #4381.
  2. The new data member data::Connection::fract must be properly populated, through downstream PR Report Connection Level Fracturing Statistics to I/O Layer opm-simulators#5811, before it is usable as a summary vector value backend.

I will keep the PR in draft mode until such time as it is ready for review.

@bska
Copy link
Member Author

bska commented Dec 18, 2024

jenkins build this opm-simulators=5811 please

@bska
Copy link
Member Author

bska commented Dec 19, 2024

jenkins build this opm-simulators=5811 please

@bska bska force-pushed the geomech-conn-smry-vec branch 6 times, most recently from 7b35fba to 5855647 Compare December 20, 2024 10:02
This commit adds support for collecting and reporting the following
set of connection level fracturing statistics measures

  - CFR<Q>MAX -- Maximum value of connection level fracturing
    quantity <Q>
  - CFR<Q>MIN -- Minimum value of connection level fracturing
    quantity <Q>
  - CFR<Q>AVG -- Arithmetic average of connection level fracturing
    quantity <Q>
  - CFR<Q>STD -- Unbiased standard deviation of connection level
    fracturing quantity <Q>

The currently supported quantities (<Q>) are

  - 'P'  -- Fracture pressure
  - 'IR' -- Injection flow rate
  - 'WD' -- Fracture width

These vectors adhere to the common connection level summary vector
specification whence

    CFRPMAX
      'I1' 16 16 6 /
    /

    CFRIRAVG
      'I1' * /
    /

    CFRWDSTD
      * * /
    /

will report the maximum pressure across all cells intersected by a
fracture originating in connection (16,16,6) of well 'I1', one
average value for each connection of well 'I1' with the average
being taken over all cells intersected by the fraction originating
at that connection and, finally, the standard deviation of the
fracture width for each connection of each well with each standard
deviation being calculated over all cells intersected by the fracture
originating at that connection.
@bska bska force-pushed the geomech-conn-smry-vec branch from 5855647 to a018412 Compare December 20, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant