You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A year ago (pre-HPXML), results.csvs were sorted by building_id. They aren't anymore, and in fact the order seems to be re-randomized in each upgrade. It would be great to have them sorted again.
e.g. on a recent test run using the buildstock-2022.10.1 bsb environment, results_up00.csv started with building_id 4249, and results_up01.csv started with building_id 3152. This breaks a lot of old python code that looked at annual savings by just subtracting the columns from different upgrades.
The text was updated successfully, but these errors were encountered:
A year ago (pre-HPXML), results.csvs were sorted by building_id. They aren't anymore, and in fact the order seems to be re-randomized in each upgrade. It would be great to have them sorted again.
e.g. on a recent test run using the buildstock-2022.10.1 bsb environment, results_up00.csv started with building_id 4249, and results_up01.csv started with building_id 3152. This breaks a lot of old python code that looked at annual savings by just subtracting the columns from different upgrades.
The text was updated successfully, but these errors were encountered: