-
Notifications
You must be signed in to change notification settings - Fork 23
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
Discretizing ground surfaces and variable albedos #120
Comments
Sorry for the delayed reply @renegacitua, I went a bit MIA for a couple of months because of travels and professional constraints but I'm back now! |
For this task I can recommend bifacial_radiance, though the learning curve is steeper than pvfactors. You can define the reflectors area using the makeCustomObject() function. The reflector's properties can be defined in the Ground.Rad file. |
@anomam Thanks for your reply, a couple of months ago i was working with pvfactors, as you mention it wont allow the discretization of the terrain, so i start to work with bifacial_radiance. But to what you mention, after using the library, I think that the program could implement, without so much work, the function of creating an extra surface(s) on the axis generated at y = 0 and therefor fix the value of the albedo to each particular surface. It would be similar to adding a shaded surface and calculating the view factor between the different surfaces. In this way, a number of variables equal to the number of added surfaces would be added to the view factor resolution matrix. |
@nicorie thanks for the reply. Yes i've been using bifacial_radiance since a while and obtaining some results for the reflectives surfaces. Anyway i haven't been able to import my own TMY file, the one that the software downloads based on the latitude and longitude. |
Hello @renegacitua,
I'm creating a Github issue for the question you asked in #119 so that I can better keep track of things, and so that other people with similar questions may easily find it.
The text was updated successfully, but these errors were encountered: