Skip to content

Function to fit Faiman temperature model to measurements #1877

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

Closed
adriesse opened this issue Sep 28, 2023 · 5 comments
Closed

Function to fit Faiman temperature model to measurements #1877

adriesse opened this issue Sep 28, 2023 · 5 comments

Comments

@adriesse
Copy link
Member

adriesse commented Sep 28, 2023

Is your feature request related to a problem? Please describe.
Many people struggle with fitting the popular temperature models to field data, or in other words, to determine the model parameters from field data.

Describe the solution you'd like
An effective method of fitting has been described and demonstrated in Jupyter Notebook published by Sandia Labs on DuraMAT data hub along with an open data set of field data for demonstrating and testing temperature model fitting methods. It would be great to make this method available through a function in PVLIB so that it can be more easily used.

Additional context
There is fast-growing interest in fitting temperature models because of the unique conditions in floating and agri-PV, therefore this capability is needed sooner rather than later. The method is also simple enough to be a candidate for IEC-61853-2.

References
The Notebook was uploaded to Zenodo for archival purposes on October 14, 2023, and can be cited as:

@adriesse adriesse changed the title Function to fit temperature model to measurements Function to fit Faiman temperature model to measurements Oct 5, 2023
@adriesse
Copy link
Member Author

adriesse commented Nov 2, 2023

This feature is currently blocked. See #1898.

@wholmgren
Copy link
Member

In my opinion, @williamhobbs engagement with the pull request and the reference material demonstrates that the contribution is 1. useful and 2. sufficiently documented.

@cwhanse
Copy link
Member

cwhanse commented Nov 2, 2023

I do not think it is wise to rely on an ipython notebook and files stored on the DuraMAT datahub as archival references. I can relent and not stand in the way of #1878 if there is a commitment to produce a document (journal or conference paper, or technical report) of some kind in the near future.

@adriesse
Copy link
Member Author

adriesse commented Nov 5, 2023

I do not think it is wise to rely on an ipython notebook and files stored on the DuraMAT datahub as archival references.

I uploaded the notebook to Zenodo for archival purposes on October 14, 2023, and updated the references in the doc strings accordingly.

@adriesse
Copy link
Member Author

adriesse commented Nov 5, 2023

I can relent and not stand in the way of #1878 if there is a commitment to produce a document (journal or conference paper, or technical report) of some kind in the near future.

Does anyone following this thread (or not) have extra time and funding available to work on such a document?

@adriesse adriesse closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants