Opened 4 years ago

Closed 4 years ago

#4582 closed defect (fixed)

Make sure that min_step_ratio is smaller than or equal to 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, if max_step_ratio is reduced so much by range limitations that it becomes smaller than min_step_ratio, we are actually sometimes taking longer steps for the by bounds projected IVs. To avoid this min_step_ratio should be adjusted so that it is always smaller than or equal to max_step_ratio after range limitations.

Change History (3)

comment:1 Changed 4 years ago by aramle

r8045 Adjusted min_step_ratio after range limitations so that it is always smaller than or equal to max_step_ratio.

comment:2 Changed 4 years ago by Iakov Nakhimovski

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

comment:3 Changed 4 years ago by Iakov Nakhimovski

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