[Pacific Power] FindClosest Function Bug with Frontend Graph Logic

[solderq35]

Reference from last year

https://github.com/OSU-Sustainability-Office/energy-dashboard/issues/191 https://github.com/OSU-Sustainability-Office/energy-dashboard/pull/216

• original purpose of findClosest function - fix weatherford hall in kilowatt campaign 2022 (https://dashboard.sustainability.oregonstate.edu/#/campaign/8). Same issue since weatherford had daily uploaded once a day

https://github.com/OSU-Sustainability-Office/energy-dashboard/pull/220

• remove redundant data from findClosest function

resultDataObject is an array of objects, e.g.

[
{
  value: <measurement, e.g. kwh>
  time_seconds: <unix>
},
{...}
]

There is a getter function in accumulated_real, energy_change, etc. that expects the elements in the array of objects to be at regular intervals. findCloset rounds the indices to nearest valid, e.g. 7 PM original query rounds to 11:59 PM if that's only valid option.

Other Tips

• Add up to 2 weeks of fake data either actually in SQL database (go back in time 2 weeks I guess), or just add to resultDataObject directly in frontend accumulated_real file

Current related PacificPower Issues:

• https://github.com/OSU-Sustainability-Office/energy-dashboard/pull/302
• https://github.com/OSU-Sustainability-Office/energy-dashboard/issues/272