GregWard's profile - activity

If you have a function describing the retroreflective behavior of your material, i.e., a BRDF, then you can use this fun

If you have a function describing the retroreflective behavior of your material, i.e., a BRDF, then you can use this fun

I'm not sure which post included this document or who authored it, but they misspoke when they said that the hemispheric

Assuming this switch corresponds to the "-u" option in Radiance, it rarely makes a big difference. If you are generatin

I don't know that there's a good rule of thumb, but in general your ground plane should be large enough to capture any s

Yes, you are correct. The -lr -N is a hard upper limit on reflections, though setting -lr 0 is pure RR limited only by

Technically, Russian roulette happens between when you reach the lower weight limit set by -lw and the number of bounces

The code is always the ultimate reference, and your understanding of it is correct. It is the man page you are using th

The most comprehensive resource to understand Radiance is still "Rendering with Radiance," which is available as a $7 US

You start from www.radiance-online.org, click on the Download/Install link near the top, then the "Radiance Installers"

The "-5" option to gendaymtx is special to the 5-phase method, and puts all the solar energy into a single patch, re-nor

Yes, that is correct.

I think you may be confusing the "up" direction with the hemisphere normal, which is determined from the surface normal,

I think you may be confusing the "up" direction with the hemisphere normal, which is determined from the surface normal

The "up" direction for the hemisphere orients the coordinate system. In this case, setting "up" to +Y is the same as "n

Yes, you should set -ab N -lr -N if you want to increase the maximum number of reflections, which can be as high as you

It's complicated. The -ab parameter sets a hard limit on the number of indirect diffuse bounces, so you should set thi

It's complicated. The -ab parameter sets a hard limit on the number of indirect diffuse bounces, so you should set thi

Hi Steph, What is your reason for running a 3-phase (or 5-phase) method in this instance? Are you planning to replace

While it is true that you can only have one sender object per rfluxmtx calculation, you can specify as many "receiver" o

Technically, you can specify as many "receiver" objects as you like in one run of rfluxmtx, in this case windows. You n

Parallel operation requires memory sharing, which Windows does not support in the same way as Unix. There are still a f

There is a bug in the dgi calculation of glarendx when sources are behind the viewer. Raphael Compagnon wrote this part

There is a bug in the dgi calculation of glarendx when sources are behind the viewer. Raphael Compagnon wrote this part

I went ahead and updated the eplus_adduvf code to work with EnergyPlus 9.x. You can get the source from https://www.rad

Thanks for sending me the IDD files in an e-mail, this is probably all I need.

I don't know how to install EnergyPlus. Is it Windows-only? I know it's lame, but I don't have access to a Windows box

Developer here. This is really helpful -- thanks! What else has changed affecting the following IDF object types? Zon

Developer here. This is really helpful -- thanks! What else has changed affecting the following IDF object types? Zone

I don't know what could be causing this -- the "-v" option means that it dies before getting to the rcontrib call. Coul

I've not seen this error -- suspicious that it has something to do with your VM. Try running rfluxmtx with the "-v" mod

I have no idea, unfortunately...

Our plan over the next months is to develop a tool that will help figure out the resolution needed for window matrix and

Different by how much? Is it a systematic error, where one or the other is consistently greater, or have you noticed so

rcontrib can only recover from binary output formats, not ASCII.

Sort of. Radiance doesn't compute or maintain surface temperatures, which you need to compute longwave radiation in a c

Hi Lasse, You already started a thread on this on Discourse. I recommend we keep this information together there. In

It looks right to me. You should not be getting this error. Perhaps you could package together your files and list of

Best to follow standard practice of dividing photometry by 179 on the way in and multiplying by 179 on the way out. Oth

Read the gensky man page to be sure. The -b option expects radiance, which is roughly luminance/179. Similarly, the -R

I noticed the issue with the window as well, but assumed William was hand-editing the output of genbox for the room to c

Your ground plane is simply too large. At most, I would use something 10x as big as your space. Yours is 4000 times bi

Yes, it's sort of like a mystery where you've been handed only a single clue, the implication being there is a dead body

If the two surfaces are actually coincident, not just close to each other, then which surface is "hit" will be (somewhat

If the two surfaces are actually coincident, not just close to each other, then which surface is "hit" will be (somewhat