Skip to content

Conversation

@arng40
Copy link
Contributor

@arng40 arng40 commented Feb 6, 2026

Before the modification :

------------------------------------------------------------
|     Well 'WATER.INJECTOR' Perforation Table              |
|-----------------------------------------------------------
|  Perforation no.  |   Coordinates   |  Well element no.  |
|-------------------|-----------------|--------------------|
|                0  |  [5, 0, -2005]  |                 0  |
------------------------------------------------------------

After

------------------------------------------------------------------------------------------------------------
|                                 Well 'WATER.INJECTOR' Perforation Table                                  |
|----------------------------------------------------------------------------------------------------------|
|  Perforation no.  |  Well element no.  |   Coordinates   |  Cell region  |  Cell sub-region  |  Cell ID  |
|-------------------|--------------------|-----------------|---------------|-------------------|-----------|
|                0  |                 0  |  [5, 0, -2005]  |    reservoir  |        hexahedra  |        0  |
------------------------------------------------------------------------------------------------------------

@arng40 arng40 self-assigned this Feb 6, 2026
@arng40 arng40 added type: feature New feature or request flag: no rebaseline Does not require rebaseline labels Feb 6, 2026
@arng40 arng40 marked this pull request as ready for review February 6, 2026 15:12
@arng40 arng40 requested a review from MelReyCG February 6, 2026 15:18
Comment on lines 565 to 570
/// The reservoir element that contains the perforation
globalIndex m_reservoirElementID;
/// the target region name for the reservoir element
string m_regionName;
/// the target sub region name for the reservoir element
string m_subRegionName;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A WellElementSubRegion can only have one communicating region cell element?
Isn't this data already stored somewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep I revert wellElementSubRegion cpp & hpp

Comment on lines 497 to 499
localIndex & esrMatched,
localIndex & eiMatched,
globalIndex & giMatched,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you may have a lot of parameters here, maybe a functor with a structured parameter would be simpler to call than a lot of in-out parameters.
Also, the return type is not documented, it is a EOF-style-bool, right? With a functor you could have the loop inside of the search method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: no rebaseline Does not require rebaseline type: feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants