Skip to content
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

Gallery examples of ModelChains for the DOE Solar Data Bounty Prize systems #1952

Open
1 of 5 tasks
kandersolar opened this issue Jan 24, 2024 · 12 comments
Open
1 of 5 tasks
Milestone

Comments

@kandersolar
Copy link
Member

kandersolar commented Jan 24, 2024

The U.S. Department of Energy sponsored a Solar Data Bounty Prize that resulted in publication of detailed monitoring data and system configuration specs for five commercial PV systems. I think we should create a section in the example gallery containing "reference models" for these systems. This section could be expanded over time to have models corresponding to other public PV datasets too (RTC, NIST, etc).

System descriptions:

Data available for download here: https://data.openei.org/s3_viewer?bucket=oedi-data-lake&prefix=pvdaq%2F2023-solar-data-prize%2F

It would be great to get these pages created and merged before March 21 so that they can be mentioned in the Modeling Tools webinar, so I'm tagging this for v0.10.4 (scheduled for mid-March).

@kandersolar kandersolar added this to the v0.10.4 milestone Jan 24, 2024
@AdamRJensen
Copy link
Member

Did DOE put funds aside for such work (seems like that would've made sense)?

@kandersolar
Copy link
Member Author

To my knowledge, no special funding is currently available for this work.

@williamhobbs
Copy link
Contributor

I really like this idea.

SR_CO looks like thin-film with true-tracking, and I think Simon Solar Farm is fixed tilt 2P crystalline, so both could be good for validation of self-shade models.

@kandersolar

This comment was marked as outdated.

@williamhobbs
Copy link
Contributor

@kandersolar these look like CdTe modules that have vertical scribe lines when mounted in landscape (all cells in a shaded module are shaded uniformly), so modeling linear shade losses should be ok.

@kandersolar
Copy link
Member Author

Here is a rough example model page for one system (SR_CO): https://gist.github.com/kandersolar/2ab973ea0b5d8cd45531a38c6e1fd06f

Feedback is welcome.

One general consideration for including this kind of example page in the docs is that to actually run the model and perform the comparison requires a lot of i/o (fetching PSM3 data and fetching the measured power data). So far we have managed to avoid performing significant i/o in the example gallery, and it would be great to keep it that way. I suggest we configure these particular examples to not be executed during the docs build, and just include the comparison plots as static PNGs. We could also just omit the plots entirely, but IMHO the figures make the example page a lot more engaging.

@adriesse
Copy link
Member

adriesse commented Mar 6, 2024

Looks good to me. I'm surprised that you have to guess at metadata given that that these are presumably the five winners. Are they?

If we settle on a way to deal with large data in examples, then we could migrate some examples from DuraMAT to pvlib as well.

@williamhobbs
Copy link
Contributor

Regarding guessing metadata, I think that a lot of array geometry info (pitch, collector width, GCR, tracker height) was left off of the list of requested metadata for the bounty prize. And manufacturer/model info was optional to provide.

@kandersolar: all of your assumptions look reasonable to me.

@mikofski
Copy link
Member

mikofski commented Mar 7, 2024

Why not move the gallery to it’s own repo?

@kandersolar
Copy link
Member Author

Why not move the gallery to it’s own repo?

I guess these models could be a repository alongside the other tutorial repositories, but (1) I don't envision these to really be tutorials, just examples, and (2) I don't think that would completely solve the i/o problem anyway -- the Data Prize datasets are pretty large (some 100s of MB), which is a lot to be downloading or storing no matter what repository the code lives in.

given that that these are presumably the five winners. Are they?

Yep, those are the winners. It's too bad that more detailed design information wasn't collected, but at least it's possible to cobble together estimates for enough missing pieces to make a simple but still reasonable model.

@adriesse
Copy link
Member

adriesse commented Mar 7, 2024

Perhaps we don't really need those examples for pvlib purposes, but in your opener you also called them "reference models". I think it would be a great open source/open data/open science achievement to run with the partial published data; scrape, glean and reverse engineer the missing bits and meta-bits; and then publish a complete reference model with documentation for each!

@kandersolar
Copy link
Member Author

I like that idea a lot! That would be a fun and useful project.

For now, #1985 is open for discussion. Rendered example page here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants