On Saturday, I spent about an hour and a half setting up the test for the new Weekly Report and testing the warm and cold spreadsheet.
I adapted the test I had used before, which included test rooms with made-up temperature and CO2 values to reflect a variety of test cases, to fit into the historical report. Since the report produced was comprehensive, I decided to focus on temperature for that day -- everything checks out with the values I determined manually with a calculator (a process which took a decent amount of time even with the few data points I had -- that's why automation is so helpful). Next, I will test the report on carbon dioxide values and then start deploying to the server. This new version will only make use of cron for the fifteen-minute logging and the two programs (task_zero and generate_historical_report) run at the end of each week. Additionally, since school is closed, the values collected will not be meaningful; they are simply a test of the capabilities of this new report. I also have a bit of functionality to add to the final piece of the new report, based on what I was told by Facility members in January. In the automated email, I should include the top 5 or so rooms that need attention, so that the Facility members can look at them. This is an easily reachable goal as it simply requires the method DataFrame.head() to return the top 5 rows of each DataFrame in sorted order. Comments are closed.
|
AuthorI'm a high school senior and programming enthusiast. Archives
March 2022
Categories |