Live trading consolidation synchronization #8436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Round time down to the nearest second before calling
SubscriptionManager.ScanPastConsolidators
in theAlgorithmManager
to account for any offset between the consolidation time and the point whereDateTime.UtcNow
is called by the live time provider.This small offset was causing
SubscriptionManager.ScanPastConsolidators
to scan consolidators (which would emit a consolidated bar) even when the time slice carried data that was supposed to be used to feed the consolidators for the current working bar.Example:
DateTime.UtcNow
is called after the data is already in the subscriptions ready to be loaded to the time slice), which could causeSubscriptionManager.ScanPastConsolidators
scan the consolidator which would emit the 9:55:00am-10:00:00am consolidated bar the last minute data was fed to the consolidator.Related Issue
Closes #8363
Motivation and Context
Requires Documentation Change
How Has This Been Tested?
Types of changes
Checklist:
bug-<issue#>-<description>
orfeature-<issue#>-<description>