| a4ffd976 | 04-Apr-2016 |
Shri Abhyankar <abhyshr@mcs.anl.gov> |
Update-TSEvent: Removed the limit on events recorded.
Removed the limit on events recorded. The initial array sizes in the event recorder is set to 12 (changed by option -ts_event_recorder_initial_s
Update-TSEvent: Removed the limit on events recorded.
Removed the limit on events recorded. The initial array sizes in the event recorder is set to 12 (changed by option -ts_event_recorder_initial_size) Each time limit is reached, the array sizes are doubled (see TSEventRecorderResize)
show more ...
|
| e2cdd850 | 04-Apr-2016 |
Shri Abhyankar <abhyshr@mcs.anl.gov> |
Update-TSEvent: Major overhaul of the event location logic.
Modified the code to use the Anderson-Bjorck variant of the regular falsi method for event location. Preliminary tests show this variant t
Update-TSEvent: Major overhaul of the event location logic.
Modified the code to use the Anderson-Bjorck variant of the regular falsi method for event location. Preliminary tests show this variant takes less iterations than pure regular falsi (previously implemented)
show more ...
|
| 7dbe0728 | 23-Mar-2016 |
Lisandro Dalcin <dalcinl@gmail.com> |
TSEvent: Fix time step resetting to play well with adaptivity
* After finishing with event handling, the time step has to be reset to some previous value. Instead of using the initial time step, u
TSEvent: Fix time step resetting to play well with adaptivity
* After finishing with event handling, the time step has to be reset to some previous value. Instead of using the initial time step, use the time step that was current before entering the event handling business.
show more ...
|
| 9e12be75 | 19-May-2015 |
Shri Abhyankar <abhyshr@mcs.anl.gov> |
TSEvent: Major fix to the TSEvent code to handle multiple events located within an interval.
The previous TSEvent code did not properly handle cases where multiple events were located within an inte
TSEvent: Major fix to the TSEvent code to handle multiple events located within an interval.
The previous TSEvent code did not properly handle cases where multiple events were located within an interval. For instance, if two events were located in an interval with the first one expected to cross zero at an earlier time compared to the second one, TSEvent would incorrectly detect the second one if the second event function value was within the tolerance earlier. To avoid this issue, the logic for TSEvent has been reorganized now to locate other events even if a single (or multiple) events have been detected.
show more ...
|
| db84a1fe | 11-May-2015 |
Shri Abhyankar <abhyshr@mcs.anl.gov> |
TSEvent: Fix TSEvent when an event occurs at the last time-step.
TSEvent used to not work correctly when the event was detected at the final TS time step. This was because TS set TS_CONVERGED_TIME f
TSEvent: Fix TSEvent when an event occurs at the last time-step.
TSEvent used to not work correctly when the event was detected at the final TS time step. This was because TS set TS_CONVERGED_TIME flag causing the time-loop to exit inspite of the event being detected. A reproducible example for this scenario (pointed by Hong) was ./ex40 -ts_final_time 4.1 -ts_exact_final_time MATCHSTEP. An event occured at the last step that was not getting correctly processed by TSEventMonitor.
Fixed this issue by setting ts->reason to TS_CONVERGED_ITERATING whenever a step is rollbacked in TSEventMonitor.
show more ...
|