[TrilinosApplication] Enforce non-zeros values in graph when doing BtDBProductOperation
during constraint computation
#12046
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.
📝 Description
This update introduces a critical improvement in the constraint computation process, specifically during the BtDBProductOperation. Previously, the computation faced failures in certain scenarios due to the absence of values within the graph. This was a consequence of Epetra's default behavior, which removes null values from the graph to conserve memory. While this approach is memory-efficient, it has been identified as a potential source of errors during assembly and the equation solving phases.
To address this issue, we have implemented a mechanism to enforce the presence of non-zero values in the graph during the BtDBProductOperation. This enhancement is aimed at preventing the computation failures by ensuring that the graph maintains the necessary values for a successful assembly and system solving process. By doing so, we enhance the robustness of the computation and eliminate the errors associated with missing graph values.
🆕 Changelog
BtDBProductOperation
during constraint computation