You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to properly support ERT ordering, I recommend:
Add a TimeType field to the SysData class and add an accessor for get_ert_time().
Have the GDS record ERT at some point.
Preserve the use of the fsw_order argument in the test API's constructor and sub-history functions by passing the fsw_order argument to the chronological history constructor.
Modify chronological history to choose whether to use get_time() or get_ert_time() for its ordering/returning operations:
As part of the work to add ERT and have chronological histories work for both ERT and FSW orders, histories should be updated to have a get_current_marker() method. This will allow the histories to specify the best way to mark a position with respect to their own implementations. For reference: ChronologicalHistories should use a TimeType, Ram and Test History should use an index.
Feature Description
In order to properly support ERT ordering, I recommend:
get_ert_time()
.fsw_order
argument in the test API's constructor and sub-history functions by passing the fsw_order argument to the chronological history constructor.get_time()
orget_ert_time()
for its ordering/returning operations:__insert_chrono()
helper__get_index()
helperThe text was updated successfully, but these errors were encountered: