Repository navigation
Document that __setitem__ leaves ghost regions unchanged - #626
Merged
Merged
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 3 |
🟢 Coverage ∅ diff coverage · -0.03% coverage variation
Metric Results Coverage variation ✅ -0.03% coverage variation Diff coverage ✅ ∅ diff coverage Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (e520f53) 52327 33599 64.21% Head commit (b1af8b9) 104654 (+52327) 67162 (+33563) 64.18% (-0.03%) Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#626) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
yguclu
marked this pull request as ready for review
October 11, 2026 19:17
yguclu
requested review from
a team and
campospinto
and removed request for
a team
October 11, 2026 19:30
yguclu
marked this pull request as draft
October 21, 2026 07:09
yguclu
marked this pull request as ready for review
October 21, 2026 07:09
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document how
__setitem__interacts with the ghost regions of distributed vectors and matrices (see #613).Writing through
__setitem__updates neither the ghost regions nor the flagghost_regions_in_sync. This is intentional: the flag decides whether the collective methodupdate_ghost_regionsis called, hence it must have the same value on all processes, while writes are often performed on a subset of the processes only (e.g. inapply_essential_bc). Resetting the flag automatically could therefore make some processes enter the collective update alone, and hang. Issue #613 was closed as not planned for this reason.__setitem__and to the propertyghost_regions_in_syncofStencilVector,StencilMatrix, andStencilInterfaceMatrix: after writing the data directly, callupdate_ghost_regionscollectively if the ghost regions are needed__setitem__and to the propertyghost_regions_in_syncofBlockVector: its flag is stored independently of the flags of its blocks, and replacing a block does not change itNo functional change.