You can import getIrradianceDataForPrevYear from firebase.js. It is asynchronous

Edit: no longer the plan, delete getIrradianceDataForPrevYear from firebase.js instead

This issue is trivial once #26 is complete, so it may be easiest to complete that first even though it is low priority

If a day has NaN as its irradiance value:

• omit it from the % efficiency graph and the correlation graph
• omit just the irradiance from the gross efficiency graph

Note omitted days at the bottom of the page

e.g. https://gml.noaa.gov/aftp/data/radiation/solrad/msn/20221/msn221000.dat

It looks like this only sometimes causes a problem, but we should fix it regardless

Instead, there should be one line that spans the whole range of data

Replace all instances of "panel" with "array"

Replace variable names with their meaning:

• beta = Panel slope angle
• gamma = Surface azimuth angle (0° for south-facing panels)
• rho_g = Reflectance (normally 0.2)
• Array area = Same label, but maybe add units of area (we use m2)

A dropdown with checkboxes next to each array. Also would be helpful to have select all and clear all buttons.

Include data for all selected arrays in graphs

For each date where at least one array has data, display the sum over all arrays that have data for that date

Could do this by fetching all data in the App component when it mounts, then pass to children as needed. You can also use localStorage or other methods I think.

You'll need to store an Admin whitelist in Firestore (can be by UID or email), and security rules that only allow writing to the Sollar Arrays collection if you are in the whitelist.

As mentioned in #16 we want to start deleting files after we populate Firestore with their data. Once #18 is done, we should be able to use the aggregated data for a given panel to display what date ranges have data for a given panel. That way, admins can see how recent the data goes up until, and any gaps in the data e.g. they forgot to upload for Sept 2021.

1. Line plot with lines for Irradiance, Output, and Typical Efficiency Output (Irradiance * 0.14)
2. Line plot of Output / Irradiance i.e. percentage efficiency
3. Correlation plot of percentage efficiency vs. precipitation (expected negative correlation)

• Can implement correlation plot by sorting percentage efficiency in ascending order, then sorting the precipitation by percentage efficiency (e.g. the precipitation and % efficiency values at any index correspond to the same date). Use the precipitation values as the x coords, and the % efficiency values as the y coords

Takes input: beta, gamma, rho_g, array area, and list of date-strings in the format that the csv files use
Returns: list of irradiance values, each entry is the irradiance for the day of the date-string at the same index.

Write in its own module and export this function

To fetch the data, make http requests to https://gml.noaa.gov/aftp/data/radiation/solrad/msn/2023/msn[YEAR][DAY-NUMBER].dat

e.g. https://gml.noaa.gov/aftp/data/radiation/solrad/msn/2023/msn23002.dat

Input: 1D array of Date objects
Output: 1D array of precipitation values, where index in array is same as the index of the date that the corresponds to
Function name: fetchPrecipData

Use of Promise.all will probably be helpful here

Function should callable like:

let precipData = await fetchPrecipData( [Date1, Date2, ...] );

Have descriptions under each graph, configurable through a js or json file

For a given day, set it's irradiance to NaN if:

• At least one of the two files does not exist
• At least one of the two files is under 250kB
• The irradiance is greater than the solar constant times the area

Files that are messed up:

• March 30th 2022 is missing
• June 14th 2022 is only 151kB
• May 10th 2019 is only 151kB
• December 23 2022 > solar constat

https://plotly.com/javascript/hover-text-and-formatting/

Store a user collection in Firestore. Each user gets a document when they create their account, the document's id is the user's uid. The document stores the user's email, and a field isAdmin.

The user collection can only be read/written to by admins

The solar arrays collection can be read by anyone, but can only be written to by admins.

Easy Fix - switch to using date string everywhere on the backend, instead of Date objects & timestamps. That way, we don't have to deal with the complexity of getting all the timezone logic right. We can just use date string in CST. Keys in firestore can be some kind of formatted string. Make sure to update the frontend to utilize the new key format.

Callable cloud function named getIrradianceDataForPrevYear

Client calls the function s.t. data object has properties: area, beta, gamma, rho_g

Utilize the calcSolarValues function defined in solarCalc.js.

Return the total irradiance for the whole year previous to current year given the parameters

Make sure to enforce App Check on the function. Check out this page to see how.

As shown in Mockup

Sum output of all arrays

Use average cost of electricity (hardcoded or from some API) in Madison to display $ saved to date

Use average energy/barrel of oil (hardcoded or from some API) to display Oil Barrels avoided to date