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

GSoC Project Solar Inverters: collecting the last 30 mins average power #120

Closed
aryanbhosale opened this issue May 29, 2024 · 3 comments · Fixed by #129
Closed

GSoC Project Solar Inverters: collecting the last 30 mins average power #120

aryanbhosale opened this issue May 29, 2024 · 3 comments · Fixed by #129
Assignees
Labels
enhancement New feature or request priority-high

Comments

@aryanbhosale
Copy link
Member

The Open Source Quartz Solar Forecast requires the following variables:

  1. recent_power: The mean power over the last 30 minutes
  2. h_mean: The mean of the recent pv data over the last 7 days
  3. h_median: The median of the recent pv data over the last 7 days
  4. h_max: The max of the recent pv data over the last 7 days

For the time being, gathering the last 30 mins average power and feeding it to this model and testing it is our priority

Context

This will allow the user to get the most recent data from their enphase system

Possible Implementation

Hitting the /api/v4/systems/{system_id}/telemetry/production_micro endpoint of the v4 API of enphase and calibrating it by testing different start /end times with the correct granularity(5 or 15mins for this) and converting it to a particular data format (as needed by pv-site-prediction)

@aryanbhosale aryanbhosale added enhancement New feature or request priority-high labels May 29, 2024
@aryanbhosale aryanbhosale self-assigned this May 29, 2024
@aryanbhosale
Copy link
Member Author

aryanbhosale commented May 30, 2024

image

the end_at is calculated as min(time_of_req, (start_time + granularity))
So if the granularity is set to day , it automatically takes the former i.e. time_of_req

Hence, the start time has to be taken as 30mins before the current time and granularity should be set to day(or week), so that the minimum of the 2 calculated variables is always the time_of_req

@aryanbhosale
Copy link
Member Author

aryanbhosale commented Jun 4, 2024

  • To Do List
  • change variable name in enphase.py file from live_generation_wh to live_generation_kw
  • change the return type of get_enphase_data function in enphase.py file from float to pd.DataFrame
  • Remove the existing code which adds the values from the last 30mins and instead of that make a pd.DataFrame

@aryanbhosale
Copy link
Member Author

Comparing #47 with the code in the main branch currently here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-high
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant