Current design of dwaco.calculate_power_output_hourly takes "Areas" array as an input.
This means that if the user does any what-if type adjustments, we need to requery the server.
Intent of original spreadsheet design was that we import from NREL the power output of a 1kW panel in each azimuth/tilt, then can do the calculations locally, scaling up the appropriate panels, and zero-ing the others. If we are going to store results in a database for reference this is what we shoud do. This could then be reused not just for that user wanting to retest with different solar array, but for other users in similar location. e.g. weather does not change that much over 5-10 kms, so can give user the option (maybe) to use a pre-prepared result from 5kms away.
Current design of dwaco.calculate_power_output_hourly takes "Areas" array as an input. This means that if the user does any what-if type adjustments, we need to requery the server. Intent of original spreadsheet design was that we import from NREL the power output of a 1kW panel in each azimuth/tilt, then can do the calculations locally, scaling up the appropriate panels, and zero-ing the others. If we are going to store results in a database for reference this is what we shoud do. This could then be reused not just for that user wanting to retest with different solar array, but for other users in similar location. e.g. weather does not change that much over 5-10 kms, so can give user the option (maybe) to use a pre-prepared result from 5kms away.