Timeframe is normally unrelated to algos
It is normal for components in a portfolio to trade different time frames.
I understand that the current architecture of Zorro requires the use of one common bar period for all the systems in a portfolio, but TimeFrame is set per algo and so can be stored per algo.
must be set by script anyway
Yes. But if there is a need to have another loop through the algos(e.g.for money mngt purposes), calculating some meta statistics/performance measures, then for maximum efficiency one would only make calculations on frame-end of each algo. So, TimeFrame calculated and set in each algo function should be visible in an umbrella run() and available for evaluation through the standard frame() function.
And this is impossible now.
