because now we have three consecutive date/hour chunks (rows 1:4, 7:9, 5:6) rather than the two that would be correct.
in general solar.time will be in UTC, which is why this problem hasn't surfaced so far, but i'd better do something to either (1) guarantee it's always UTC no matter who's using streamMetabolizer and/or (2) calculate the dates and hours in a more compatible way. i think the date is what actually needs to be corrected, because DST means that 11pm really is 12am in round 24-hour periods since january 1.
convert_date_to_doyhr captures the date bounds i'd expect when tz='UTC' or standard (non-daylight savings) time.
but the first hour of each new day gets assigned to the previous day when tz puts us in daylight savings:
this is a problem for
mm_model_by_ply
where we try to compute dates and hours:because now we have three consecutive date/hour chunks (rows 1:4, 7:9, 5:6) rather than the two that would be correct.
in general solar.time will be in UTC, which is why this problem hasn't surfaced so far, but i'd better do something to either (1) guarantee it's always UTC no matter who's using streamMetabolizer and/or (2) calculate the dates and hours in a more compatible way. i think the date is what actually needs to be corrected, because DST means that 11pm really is 12am in round 24-hour periods since january 1.