Bård Skaflestad 6e8da2309b Delay UDQ Assignments Until After Summary Output ... Commit 0aaa69c6e (PR #5330) was a little too eager in its effort to handle UDQ ASSIGN operations after action processing[%]. In particular, the assignments, which alter the internal structures of the SummaryState and UDQState objects, would happen prior to writing summary files. In turn, this would make it appear as if the assignment happened too early. This commit defers UDQ assignments triggered by action processing until FlowProblem<>::endEpisode() for two reasons 1. The problem originally addressed in 0aaa69c6e only presented when the assignment was triggered on the final time step of an episode (report step), so handling this situation here is a more targeted approach. 2. Member function FlowProblem<>::endEpisode() is called after we write the summary file output so any alterations to the internal structures of the SummaryState will not be visible in the summary output until the next time step. This is the expected behaviour. [%] Insufficient testing by: [at]bska.		2024-05-28 18:16:30 +02:00
..
core/props	add cartesianCoordianteLevel in ALUCartIdxMapp, used in RelperDiag	2023-11-28 15:47:00 +01:00
simulators	Delay UDQ Assignments Until After Summary Output	2024-05-28 18:16:30 +02:00