run on custom clocks not wall clocks #492
Closed
jasonbourne13
started this conversation in
Ideas
Replies: 1 comment
-
Thats an interesting problem. I think the best you can do at this point is to csp.filter your input source right at the start so it only ticks into your graph between the times that you want. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Does csp support using custom clocks instead of wall clocks? I haven't found it. But if it does, I think it would be very helpful. Here's a specific use case that could be very common.
Say we are using csp to analyze traffic data of an online streaming event that only goes live 2:00pm to 4:00pm every day. And our goal is to read back several days of traffic data + using live data to generate signals to help increase live traffic. Currently, I think we can only just do csp.run for the full wall clock of past, for example, 5 days to calculate features. Most of the ticks will be NaN since there's no data. If we could define 2:00pm~4:00pm to be a day and csp engine only runs on these time range, that would save lots of trouble and speed up calculations as well. I would love to hear about your thoughts on this.
Beta Was this translation helpful? Give feedback.
All reactions