RADIANCE simulations & Output files

57 views
Skip to first unread message

Chingiz Asadzade

unread,
Mar 29, 2023, 10:48:34 AM3/29/23
to VI-Suite
Dear Dr. Southall, 
I hope you are doing well. 

I am tryinh to use VI-Suite for Radiance lighting simulations for Photovoltaics applications and have several challenges.

- As I know gendaylit function can take input parameters such as Perez parameters (epsilon, delta) and direct and diffuse solar irradiances/illuminances. As I understand basic context doesn't use any data from EPW file except coordinates. In LiVi context node's basic form only epsilon and delta parameters can be defined. Is there a way of using irradiance values for gendaylit function?  

- There is an alternative option of Radiance sky. I was thinking of generating sky with irradiance values in Radiance itself and using the text file in VI-Suite. Will it be possible to have a context animation with different timesteps in this case? I have tried to do it with gensky Radiance sky description script, but the results were same as for previous simulation I did with animation, however in Radince sky I made an input for a specific hour.

- While using CBDM context's Hourly Irradiance function, the results for diiferent sensor points are displayed in Blender, but in the .csv file the whole plane is taken as a sensor point. How can I get the results with X,Y,Z coordinates for each senor as in other functions using Hourly Irradiance? I will attach the screenshots below.

I apologize for many question, would be happy if you could help me.
Thanks in advance.

Best Regards,
Chingiz Asadzade
carrof_CBDM_hourly_irradiance_output.PNG
carrof_CBDM_hourly_irradiance.PNG

VI-Suite

unread,
Apr 3, 2023, 8:04:33 AM4/3/23
to VI-Suite
Not in version 0.7. I may add it for 0.8.

If you set a up a LiVi Context basic animation and look at the text output with a text edit node you will see sky entries for each frame are separated by a "# Frame X" line. You just replace these entries with the output from gendaylit that you want for each frame.

If doing CBDM, result data volumes can get very large when doing 8760 hourly simulations so it defaults to per object results rather than per face/vertex. Just convert your sensor faces into separate objects to get per 'face' results.
Ryan
Reply all
Reply to author
Forward
0 new messages