Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to access time-series resutls? #26

Open
UGuntupalli opened this issue May 26, 2020 · 4 comments
Open

How to access time-series resutls? #26

UGuntupalli opened this issue May 26, 2020 · 4 comments

Comments

@UGuntupalli
Copy link

@rconcep & @wilchesf :
When an analysis has been run and I want to access the time-series results of my simulation run in Quest, how can I do that ? When I go to Results Viewer, it does not allow me to access more than 0 to 744, when I try to export as .csv, it only is exporting hours 0 to 744. I am running a BTM simulation with 1 year of data and would like to access the entire years worth of data. I couldn't find a relevant section for this in the documentation either. Can you kindly help ? If there is a way to extract this data by writing a small script, happy to do that as well.

@rconcep
Copy link
Contributor

rconcep commented May 27, 2020

Hi Uday,

In the Results Viewer, each month of simulation is listed separately in the solved model list. You will need to select each month before using the export .csv option. Whichever models are selected at the time will be exported to a separate .csv file.

@UGuntupalli
Copy link
Author

@rconcep : Thank you

@UGuntupalli
Copy link
Author

UGuntupalli commented Jun 3, 2020

@rconcep : When I look at each monthly time-series export, most of the financial columns like energy_charge_with_es, total_bill_with_es , energy_charge_without_es etc. all seem to be pre-aggregated (summed I presume) at the monthly level. Is there a way to have the data export without that aggregation ? Because, I am interested in hourly results ?

image (1)

One other suggestion is:

  • While exporting the data as a .csv, it would be beneficial to export it with a pd.DateTime column instead of a "time" column which stores hour numbers. The DateTimeIndex or DateTime would allow users to easily concatenate the data and sort without having to worry about which month a particular hour came from if that makes sense.

@UGuntupalli
Copy link
Author

@rconcep & @wilchesf & @dacopp :
Can you please advise ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants