You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to move the Linke turbidity look up code out of clearsky.ineichen and into its own function. The clearsky.ineichen API can remain the same, and it can call the new function to automatically pull in the turbidity data. Two advantages: you can easily access the turbidity data that is driving your pv models, you can cache the result so that you don't have to read and process the file over and over.
The text was updated successfully, but these errors were encountered:
I agree. There are other data sources for turbidity and it would be useful to have the option to supply turbidity as input to the Ineichen (or other) models.
I'd like to move the Linke turbidity look up code out of clearsky.ineichen and into its own function. The clearsky.ineichen API can remain the same, and it can call the new function to automatically pull in the turbidity data. Two advantages: you can easily access the turbidity data that is driving your pv models, you can cache the result so that you don't have to read and process the file over and over.
Reply to this email directly or view it on GitHubhttps://github.com//issues/95.
I'd like to move the Linke turbidity look up code out of
clearsky.ineichen
and into its own function. Theclearsky.ineichen
API can remain the same, and it can call the new function to automatically pull in the turbidity data. Two advantages: you can easily access the turbidity data that is driving your pv models, you can cache the result so that you don't have to read and process the file over and over.The text was updated successfully, but these errors were encountered: