TRANSFER execute_on is only ever called for conservative transfers, when any postprocessor transfer could want such an option #28981
Labels
C: Framework
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: defect
An anomaly, which is anything that deviates from expectations.
Bug Description
When trying to transfer PPs in fixed point iterations, there is no insertion point at time step begin that fits nicely for the "number of fixed point iterations". This made me look into using EXEC_TRANSFER, which is actually silently ignored even though the PP is transferred!
Steps to Reproduce
this shows it
Impact
Lagged reason for the first fixed point iteration
No result at all if only executing on TRANSFER
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered: