allow custom clock other than just wall clock

[jasonbourne13]

I think it would be beneficial to allow custom clock in csp.run other than just wall clock?

For example, I'm analyzing the 1-minute aggregated traffic of an online live streaming event that only happens 2:00pm to 4:00pm every day. My goal is to combine past historical data with live traffic data to generate signal and predict future traffic. I'm using past 5 days data. Now I have to do csp.run for starttime=pd.Timestamp('2025-03-15 2:00pm') and endtime=pd.Timestamp('('2025-03-20 4:00pm''), which involves running through each minute grid for the full period. If we can run on only 2:00pm to 4:00pm every day, we would save running over 90% of the ticks. This could significantly improve the historical testing speed. Does csp currently support this in some way that I'm not aware of?

[AdamGlustein]

In historical mode, if there is no data between -1:4:00pm and 2:00pm then the engine will automatically skip to the next event, so there's no additional cost. If there are events in that window that you are filtering out, I'd recommend to just do multiple csp.run calls per day between 2-4pm. The engine always runs continuously in simulation so there's no way to do a single run on a non-continuous interval.