Issue211 refactor heat transfer #322
Open
Conversation
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
This was referenced Apr 29, 2025
MassimoCimmino
force-pushed
the
issue211_refactorHeatTransfer
branch
from
6d614d4 to
3cf8b33
Compare
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.
Closes #211. To be reviewed after #320.
The PR introduces the refactoring of the
heat_transfermodule. TheBorefieldclass is integrated into theSolverclasses but they are not refactored. This will come in other sub-issues of #210.An
_EquivalentBorefieldclass is implemented for use in theEquivalentsolver. It is likely that both the_EquivalentBoreholeand_EquivalentBorefieldclasses can be removed with refactoring of theEquivalentsolver.