Closed Martin-Molinero closed 3 months ago
Some notes about discussed potential work flow and API changes:
AddUniverse(Resolution/TimeSpan)
-> AddUniverse(Func<DateTime, DateTime>)
AddUniverse(IDateRule)
-> AddUniverse(Func<DateTime, DateTime>)
AddUniverse(Func<DateTime, DateTime?>)
a func that could rely on the algorithms state, determines when selection should happen, if it doesn't know could return null
-> tricky because backtest runs in a separate worker thread, ahead of time
Any updates/movement on this? This could really help for situations where universe selection is done based on stock behavior when the market opens or during pre-market. i.e. Small cap stocks that run up during pre-market, or stocks that break out of an opening market range during market open. I understand the challenge though, as you'd potentially need to monitor real-time price streams for 8,000 equities.
Yes, I really need this one, too
+1 for this ask. I'm also looking for this
I am also looking to use this ability. Can an update be provided? or a target date for completion?
Hi all / @TateLinzel, thank you for the interest in this feature.
This is probably technically possible, but would consume an enormous amount of data - further slowing down LEAN (as @cnaccio said - we'd need to monitor 8k assets prices every minute of the day). We're addressing many challenges now to get the next 10x improvement in speed but will soon be able to expand on this future feature further. Note that its not a simple challenge and we appreciate your patience and support as we continue grinding =)
+1 for me , this would be awesome :) Thanks for your hard work folks.
Expected Behavior
Actual Behavior
ITimeTriggeredUniverse
which creates data points based on a schedule but this can't be used with other universe selection data sources. Users currently have to add logic in their selection method to skip selection stepsPotential Solution
Reproducing the Problem
N/A
System Information
N/A
Checklist
master
branch