[Radiance-general] strange artifacts in rendering (and Yosemite bug)

[Greg Ward]

Many thanks for the quick turn-around on that, Rob!  This mostly applies to Mac OS X 10.10 (Yosemite) users, but anyone who cares to do a before/after timing, that would also be useful.

Cheers,
-Greg

> From: "Guglielmetti, Robert" <Robert.Guglielmetti at nrel.gov>
> Subject: Re: [Radiance-general] strange artifacts in rendering (and Yosemite bug)
> Date: August 21, 2015 2:47:03 PM PDT
> 
> To that end, I just moved the NREL 5.0.a.4 release tag up to Greg's latest
> commit, and have posted a fresh Mac installer on there, so now you don't
> even have to be able to compile from source to help Greg test this out!
> Come and get it:
> 
> https://github.com/NREL/Radiance/releases/tag/5.0.a.4
> 
> Windows (including 32-bit!) and Linux packages will be re-made and
> re-posted to this release page shortly.
> 
> - Rob
> 
> 
> On 8/21/15, 2:19 PM, "Greg Ward" <gregoryjward at gmail.com> wrote:
> 
>> I have not tested all the programs fully under Yosemite to make sure
>> there are no more deadlocks.  I would appreciate help on that from the
>> user community ahead of the official 5.0 release, which I'm hoping to get
>> out in the next week or so.  That means getting a 5.0a installer out or
>> getting volunteers who don't mind compiling from source to run rvu,
>> rtrace, rcontrib, genBSDF, etc. in -n >1 mode....
>> 
>> Cheers,
>> -Greg
>> 
>>> From: "Guglielmetti, Robert" <Robert.Guglielmetti at nrel.gov>
>>> Subject: Re: [Radiance-general] strange artifacts in rendering (and
>>> Yosemite bug)
>>> Date: August 21, 2015 1:06:40 PM PDT
>>> 
>>> This is fantastic news! (Roland/Lars, take note...)
>>> 
>>> I don't recall, is there a concrete test for the fork() thing? I was
>>> just in the midst of re-making the Radiance packages (we need to support
>>> 32-bit Windows still), but I will *happily* reset the release tag to
>>> this commit and start over again, if it means I get to re-enable
>>> OpenStudio-Radiance multithreading on Yosemite!
>>> 
>>> On 8/21/15, 12:59 PM, "Gregory J. Ward"
>>> <gregoryjward at gmail.com<mailto:gregoryjward at gmail.com>> wrote:
>>> 
>>> In any event, I checked in a change that I'm hoping fixes this issue
>>> under Yosemite, while not costing us too much on all the other Unix
>>> platforms that don't have this issue.