Opened 4 years ago

Closed 4 years ago

#4579 closed enhancement (fixed)

Add logging for max_step_ratio after range limitations

Reported by: aramle Owned by: aramle
Priority: major Milestone:
Component: FMU/JMU runtime Version: trunk
Keywords: #4602. Cc:

Description (last modified by Iakov Nakhimovski)

This is a part of #4602.

Currently, there is no easy way to see if max_step_ratio is smaller than min_step_ratio after range limitations of the step Max_step_ratio is not logged after this step. It could, however, happen that the range limits is the factor that decrease the step length the most. Therefore, it would be wise to log this and add a letter to the solve trace logging indicating what causes lambda_max to be smaller than one.

Change History (6)

comment:1 Changed 4 years ago by aramle

r8037 Logging added for max_step_ratio after range limitations of the step.

comment:2 Changed 4 years ago by aramle

r8038 Removed warning for max_step_ratio to small, better to add letter in solver trace.

comment:3 Changed 4 years ago by aramle

Description: modified (diff)

comment:4 Changed 4 years ago by aramle

r8042 Added letter to solve trace in case range limitations limit the step length the most.

comment:5 Changed 4 years ago by Iakov Nakhimovski

Description: modified (diff)
Keywords: #4602. added

comment:6 Changed 4 years ago by Iakov Nakhimovski

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.