Cliff Hansen
Cliff Hansen
Cool idea. I can't really comment on the cost (if any) of distributing another relatively large data file. Some thoughts: the technical improvement to modeling would be minor: the only...
> Accuracy is not so important Good point. Altitude rounded to 100m increments is probably good enough.
This discussion suggests there are two, perhaps complementary, enhancements: - provide a low-resolution, low-accuracy altitude to supplement the current default of 0. for clearsky and solar position calculations. - via...
> I wonder if folks will start to cannibalize pvlib for elevation data, and then send issues complaining that it's only accurate to 35m 🤣 Assuredly, yes.
I agree that albedo can change with e.g., precipitation or season, but it is also a property of the bare ground surface, and it is that perspective that put albedo...
> Does anyone know if including time-specific albedo this has been shown to be even more important with bifacials? > > (I would think yes.) Yes, it is more important...
Which is the better course of action? 1. Leave `albedo` on `PVsystem` or `Array`. Edit the docstrings and add tests to make it explicit that `PVSystem.albedo` or `Array.albedo` can be...
I'm in favor of moving it to iotools. I'd like to consider splitting that function into two, to read module and inverter parameters separately.
So far we've named `iotools` functions for the source of the data being read; that patterns suggests `read_sam` (I've never liked `retrieve`). I agree if we keep `sam` in the...
@abhisheksparikh Thanks!