-
Notifications
You must be signed in to change notification settings - Fork 47
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
pyRadiance integration #533
Comments
Ah, @cdeline this would be amazing! (If you already have some pointers or Dockerfiles that installs Radiance (I understand it would have to be the full Radiance (core+extra) in docker, I would greatly appreciate that as well :D ) |
Thanks for response @shirubana ! From what I understood from this Dockerfile (I assume it is this: https://github.com/NREL/bifacial_radiance/blob/main/docker/Dockerfile), it does not take the entire Radiance code (i.e both core and extra). And this would be required to run certain commands in bifacial_radiance, such as gencumsky. Please correct me if Ive misunderstood. (however, I can maybe use the gendaymtx from pyradiance instead of gencumsky). |
Kinda. That dockerfile uses an older version of Radiance; it adds the Jaloxa executables as part of the process that are now part of the newer Radiance releases. Otherwise it's the same. The docker file also adds the gencumsky function as part of the internal workings, so you don't need to switch to gencumsky yet.
S.
From: fredrbl ***@***.***>
Sent: Wednesday, September 25, 2024 11:17 AM
To: NREL/bifacial_radiance ***@***.***>
Cc: Ovaitt, Silvana ***@***.***>; Mention ***@***.***>
Subject: Re: [NREL/bifacial_radiance] pyRadiance integration (Issue #533)
CAUTION: This email originated from outside of NREL. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thanks for response @shirubana<https://github.com/shirubana> !
From what I understood from this Dockerfile (I assume it is this: https://github.com/NREL/bifacial_radiance/blob/main/docker/Dockerfile), it does not take the entire Radiance code (i.e both core and extra). And this would be required to run certain commands in bifacial_radiance, such as gencumsky. (however, I can maybe use the gendaymtx from pyradiance in stead).
But I will give it a go and test! Thanks again for the tip.
-
Reply to this email directly, view it on GitHub<#533 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFOEOZWGGXXAZT4OYKS7MNDZYLVZ5AVCNFSM6AAAAABNG4RFXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUGY4TMOJYGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
LBNL has a new python wrapper around RADIANCE binaries. This may improve integration and eliminate issues users are having with properly installing RADIANCE and setting RAYPATH, etc.
It appears that the underlying C binaries are still being used, just with a more pythonic wrapper, so there should be no performance issues.
Repo: https://github.com/LBNL-ETA/pyradiance
Reference pages: https://lbnl-eta.github.io/pyradiance/reference/
The text was updated successfully, but these errors were encountered: