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

Create a new section for cloud factor #105

Closed
micahjohnson150 opened this issue Aug 26, 2019 · 3 comments
Closed

Create a new section for cloud factor #105

micahjohnson150 opened this issue Aug 26, 2019 · 3 comments

Comments

@micahjohnson150
Copy link
Contributor

Per #98 we are separating out cloud factor from solars section to create a more verbose description of the section for cloud factor. We are not separating out this in the code so there will be a bit of monkeying around with configs. This will also create an extra set of min and max fas we need them for solar and CF.

@scotthavens How do you like the descriptions for these cloud factor items:

HEADER
Cloud Factor - Fraction used to limit solar radiation Cloudy (0) - Sunny (1)

stations - Stations to use for distributing cloud factor as a decimal representing full clouds (0) to full sun (1).

min and max will follow a similar description as stations.

@scotthavens
Copy link
Contributor

Cloud factor - ratio of measured incoming solar radiation to clear sky solar radiation that will range from cloudy (0) to sunny (1)`

Since these are probably stations that have solar radiation measurements that might be good to clarify. Does it need to have the 0-1 description if it's in the header? Probably doesn't hurt to be verbose since it's a calculated value. Something like:

stations - Stations with estimated cloud factor from measured solar radiation ranging from cloudy (0) to sunny (1)

@micahjohnson150
Copy link
Contributor Author

The only reason I would add it to the description is so folks could still request help from inicheck --details or for the config documentation online. If I had to pick one to leave one out I would probably leave out the header's prescribed 0-1 but I agree verbose is great!

@scotthavens
Copy link
Contributor

It makes sense to have it as many places as needed.

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

2 participants