# strange artifacts in rendering (and Yosemite	bug)

**URL:** <https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302>\
**Category:** radiance-general\
**Created:** [August 21, 2015, 6:59pm UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302 "2015-08-21T18:59:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg\_Ward](https://discourse.radiance-online.org/user_avatar/discourse.radiance-online.org/greg_ward/32/471_2.png) [@Greg\_Ward](https://discourse.radiance-online.org/u/Greg_Ward)\
**Post date:** [August 21, 2015, 6:59pm UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/1 "2015-08-21T18:59:41Z")

</div>

As it turns out, this appears \*not\* to be a problem with Yosemite after all, but an issue with the last official release (4.2.2), whose accuracy isn't quite as good as the latest (HEAD or 5.0a) with respect to its Hessian interpolation method. The artifacts MJ noticed were due to inaccuracies in the interreflection calculation, for which this scene is something of a worst case. Decreasing the -aa parameter while increasing -ad seems to resolve these issues, especially with the latest code.

While playing around with Yosemite trying to reproduce these artifacts, I discovered that the problems I thought I was having with the system select() call were in fact due to a bug in the way Yosemite handles application-level file locking. This was a complete surprise, but it turns out not to be so difficult to work around.

Without getting too much into the details, the stdio library has these lock/unlock calls to make the library thread-safe, which of course I don't care about because I don't use threads, but they severely impact performance even on unthreaded code. In some cases, it requires a mutex lock/block/unlock procedure for every character that is input or output, completely defeating the purpose of i/o buffering that is the purpose of stdio in the first place. Therefore, I had some workarounds in place to reduce or eliminate this overhead, basically locking the files once at the outset to avoid the per-call mutex overhead.

This all worked fine up until the latest release of Mac OS X (10.10), when Apple changed the behavior of fork() such that it preserves application-level i/o locking for no conceivable reason. Since these locks are designed to negotiate between threads sharing memory (i/o buffers), and separate processes don't share memory, the locks should sever on fork(). Every Unix out there does this, except Mac OS X 10.10.x. Therefore, when I made a call to flockfile() at the start of rvu or rtrace, then forked its children, each child would deadlock the instant it tried to use a shared file pointer (i.e., the ambient file).

You could say I was being cavalier about the use of flockfile(), but I was just trying to work around a horrible performance bottleneck introduced with automatic application-level locking in stdio. It's one thing to introduce a new feature and suggest that people using multi-threading take advantage of it. It's another thing to implement locking as the new default behavior, while decreasing i/o performance by about 90% (no exaggeration) even when it is not needed, then not even offer a means to disable it.

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.

Cheers,  
-Greg

> **···**
>
> > From: "Gregory J. Ward" \<gregoryjward@gmail.com\>  
> > Subject: Fwd: [Radiance-general] strange artifacts in rendering  
> > Date: August 20, 2015 9:14:23 AM PDT
> > 
> > Just forwarding this to the mailing list in case as an additional warning against installing Mac OS X Yosemite (10.10.x). As if the multi-processing bug were not enough, there seem to be other problems with instances and/or textures (not sure) on that platform.
> > 
> > I may try investigating this on the weekend, but I don't hold out much hope for a resolution.
> > 
> > -Greg
> > 
> > > From: Minjung Kim \<mkim85@gmail.com\>  
> > > Subject: Re: [Radiance-general] strange artifacts in rendering  
> > > Date: August 19, 2015 4:58:24 PM PDT  
> > > To: "Gregory J. Ward" \<gregoryjward@gmail.com\>
> > > 
> > > Hi Greg,
> > > 
> > > I think the problem might indeed be with OS 10.10. None of the 20 scenes that I rendered on OS 10.9 had any issues, whereas more than half of the 20 on OS 10.10 did. Please see attached files for examples.
> > > 
> > > Thanks for your help!
> > > 
> > > MJ
> > > 
> > > On Wed, Aug 19, 2015 at 4:33 PM, Minjung Kim \<mkim85@gmail.com\> wrote:  
> > > I'm going to render a bunch of other blobby objects on 10.9, and see if I get the problem here. I'll let you know what I find out.
> > > 
> > > Thanks!
> > > 
> > > MJ
> > > 
> > > On Wed, Aug 19, 2015 at 4:30 PM, Gregory J. Ward \<gregoryjward@gmail.com\> wrote:  
> > > Thanks, Minjung.
> > > 
> > > I guess we can add this to the list of bugs under Mac OS X 10.10, which to me has been a disastrous release. I seriously doubt I will be able to fix problems on this platform, but I'll give it a try when I have some time.
> > > 
> > > Cheers,  
> > > -Greg
> > > 
> > > > From: Minjung Kim \<mkim85@gmail.com\>  
> > > > Subject: Re: [Radiance-general] strange artifacts in rendering  
> > > > Date: August 19, 2015 4:16:50 PM EDT
> > > > 
> > > > Hi Greg,
> > > > 
> > > > Thanks for your help! I am still unable to get the artifacts to come back -- but only on my current machine (late-2013 iMac, 21.5 in., OS X 10.9). If I run the same code on a different machine (late-2013 iMac, 21.5 in., OS X 10.10), I reliably get the artifact. Isn't that strange?
> > > > 
> > > > Attached are the files that I used. To run, please use the following commands:
> > > > 
> > > > oconv square.rad \> square.oct  
> > > > oconv scene.rad \> scene.oct  
> > > > rpict -x 1024 -y 1024 -vh 12.018 -vv 12.018 -vp 0 -0.57 0 -vd 0 1 0 -vu 0 0 1 -av 0 0 0 -vtv -ab 1 scene.oct \> scene.pic  
> > > > pfilt -1 -x 512 -y 512 -e 1 -r 0.6 scene.pic \> scene.hdr
> > > > 
> > > > In scene.rad, the square is incorporated as an instance. I know that I don't really need to instance the square since I only have one, but the scene with the artifacts was using instances, so I thought it would be better to send you the code as is.
> > > > 
> > > > If anything is unclear, please let me know. Thanks again!
> > > > 
> > > > Regards,
> > > > 
> > > > MJ
> > > > 
> > > > On Tue, Aug 18, 2015 at 7:00 PM, Minjung Kim \<mkim85@gmail.com\> wrote:  
> > > > Hi Greg,
> > > > 
> > > > Thanks! I'm putting together the files, but I'm unable to replicate the problem using my latest code, though I don't think I've changed anything substantial. I'll get back to you once I can reliably replicate the artifacts.
> > > > 
> > > > MJ
> > > > 
> > > > On Mon, Aug 17, 2015 at 9:04 PM, Greg Ward \<gregoryjward@gmail.com\> wrote:  
> > > > Hi MJ,
> > > > 
> > > > Can you send me your model & rendering parameters off-list. I won't know what's going on until I play with it.
> > > > 
> > > > Thanks,  
> > > > -Greg
> > > > 
> > > > > From: Minjung Kim \<mkim85@gmail.com\>  
> > > > > Subject: [Radiance-general] strange artifacts in rendering  
> > > > > Date: August 17, 2015 5:30:37 PM EDT
> > > > > 
> > > > > Hi everyone,
> > > > > 
> > > > > I am getting strange artifacts in my renderings, and am wondering which parameters to tweak in order to get rid of them. The artifacts look like a white, or sometimes half-black and half-white, patch at random locations. See below for examples:
> > > > > 
> > > > > [http://minjung.ca/tmp/artifacts1.png](http://minjung.ca/tmp/artifacts1.png)  
> > > > > [http://minjung.ca/tmp/artifacts2.png](http://minjung.ca/tmp/artifacts2.png)
> > > > > 
> > > > > I've tried (1) setting ad = 4096, as = 1024, and (2) setting aa = 0, ar = 0, but neither of these two settings fixed the problem. Do you have any idea what might be happening? Here are some possibly relevant factors:
> > > > > 
> > > > > - The object is completely Lambertian.  
> > > > > - The only light source in the scene is a glow source that is positioned behind the camera, and covers as much of the sky as possible.  
> > > > > - I don't think I've ever encountered such artifacts with untextured stimuli. I could be wrong, though.
> > > > > 
> > > > > Thanks in advance!
> > > > > 
> > > > > MJ

---

<div class="post-metadata">

**Author:** ![Greg\_Ward](https://discourse.radiance-online.org/user_avatar/discourse.radiance-online.org/greg_ward/32/471_2.png) [@Greg\_Ward](https://discourse.radiance-online.org/u/Greg_Ward)\
**Post date:** [August 21, 2015, 8:19pm UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/2 "2015-08-21T20:19:16Z")

</div>

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@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@gmail.com\<mailto:gregoryjward@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.

---

<div class="post-metadata">

**Author:** ![Greg\_Ward](https://discourse.radiance-online.org/user_avatar/discourse.radiance-online.org/greg_ward/32/471_2.png) [@Greg\_Ward](https://discourse.radiance-online.org/u/Greg_Ward)\
**Post date:** [August 21, 2015, 11:45pm UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/3 "2015-08-21T23:45:09Z")

</div>

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@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:
> > 
> > [Release 5.0.a.4 · NREL/Radiance · GitHub](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@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@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@gmail.com\<mailto:gregoryjward@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.

---

<div class="post-metadata">

**Author:** ![Randolph\_Fritz4](https://discourse.radiance-online.org/letter_avatar_proxy/v4/letter/r/c6cbf5/32.png) [@Randolph\_Fritz4](https://discourse.radiance-online.org/u/Randolph_Fritz4)\
**Post date:** [August 24, 2015, 11:53pm UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/4 "2015-08-24T23:53:04Z")

</div>

Sigh. I think in a few more years, anyone who is interested in  
scientific computing, rather than business functions or social  
networking, is going to be running ChromeOS.

> **···**
>
> --  
> Randolph M. Fritz, Lighting Design and Simulation  
> +1 206 659-8617 || rmfritz3@gmail.com
> 
> On Fri, Aug 21, 2015 at 4:45 PM, Greg Ward \<gregoryjward@gmail.com\> wrote:
> 
> > 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@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:
> > > 
> > > [Release 5.0.a.4 · NREL/Radiance · GitHub](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@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@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@gmail.com\<mailto:gregoryjward@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.
> > 
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > Radiance-general mailing list  
> > Radiance-general@radiance-online.org  
> > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)

---

<div class="post-metadata">

**Author:** ![Greg\_Ward](https://discourse.radiance-online.org/user_avatar/discourse.radiance-online.org/greg_ward/32/471_2.png) [@Greg\_Ward](https://discourse.radiance-online.org/u/Greg_Ward)\
**Post date:** [August 25, 2015, 4:15am UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/5 "2015-08-25T04:15:10Z")

</div>

It will be interesting to see what ChromeOS develops into. Right now, it's more of a browser manager for accessing online tools, and doesn't have much in the way of compilers or a runtime environment to speak of. Kind of a waste of a laptop, if you ask me....

-Greg

> **···**
>
> > From: "Randolph M. Fritz" \<rmfritz3@gmail.com\>  
> > Subject: Re: [Radiance-general] strange artifacts in rendering (and Yosemite bug)  
> > Date: August 24, 2015 4:53:04 PM PDT
> > 
> > Sigh. I think in a few more years, anyone who is interested in  
> > scientific computing, rather than business functions or social  
> > networking, is going to be running ChromeOS.  
> > --  
> > Randolph M. Fritz, Lighting Design and Simulation  
> > +1 206 659-8617 || rmfritz3@gmail.com
> > 
> > On Fri, Aug 21, 2015 at 4:45 PM, Greg Ward \<gregoryjward@gmail.com\> wrote:
> > 
> > > 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@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:
> > > > 
> > > > [Release 5.0.a.4 · NREL/Radiance · GitHub](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@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@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@gmail.com\<mailto:gregoryjward@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.
> > > 
> > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > > Radiance-general mailing list  
> > > Radiance-general@radiance-online.org  
> > > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)
> > 
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > Radiance-general mailing list  
> > Radiance-general@radiance-online.org  
> > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)

---

<div class="post-metadata">

**Author:** ![Randolph\_Fritz4](https://discourse.radiance-online.org/letter_avatar_proxy/v4/letter/r/c6cbf5/32.png) [@Randolph\_Fritz4](https://discourse.radiance-online.org/u/Randolph_Fritz4)\
**Post date:** [August 26, 2015, 4:43pm UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/6 "2015-08-26T16:43:19Z")

</div>

Google offers the "Native Client" SDK  
([https://developer.chrome.com/native-client\](https://developer.chrome.com/native-client%5C)), which supports  
compilation and download of code with gcc (wince) and a set of  
non-Unix APIs (double wince.) Also, of course, one can just work with  
the base Linux on ChromeOS, bypassing the browser completely.

So far as I can see, these tools aren't much used yet; ChromeOS is not  
a major development platform. But they are there and at the rate the  
major platforms are diverging from general computing applications,  
they may be all that will be left in a few years. ☹

> **···**
>
> --  
> Randolph M. Fritz, Lighting Design and Simulation  
> +1 206 659-8617 || rmfritz3@gmail.com
> 
> On Mon, Aug 24, 2015 at 9:15 PM, Greg Ward \<gregoryjward@gmail.com\> wrote:
> 
> > It will be interesting to see what ChromeOS develops into. Right now, it's more of a browser manager for accessing online tools, and doesn't have much in the way of compilers or a runtime environment to speak of. Kind of a waste of a laptop, if you ask me....
> > 
> > -Greg
> > 
> > > From: "Randolph M. Fritz" \<rmfritz3@gmail.com\>  
> > > Subject: Re: [Radiance-general] strange artifacts in rendering (and Yosemite bug)  
> > > Date: August 24, 2015 4:53:04 PM PDT
> > > 
> > > Sigh. I think in a few more years, anyone who is interested in  
> > > scientific computing, rather than business functions or social  
> > > networking, is going to be running ChromeOS.  
> > > --  
> > > Randolph M. Fritz, Lighting Design and Simulation  
> > > +1 206 659-8617 || rmfritz3@gmail.com
> > > 
> > > On Fri, Aug 21, 2015 at 4:45 PM, Greg Ward \<gregoryjward@gmail.com\> wrote:
> > > 
> > > > 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@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:
> > > > > 
> > > > > [Release 5.0.a.4 · NREL/Radiance · GitHub](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@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@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@gmail.com\<mailto:gregoryjward@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.
> > > > 
> > > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > > > Radiance-general mailing list  
> > > > Radiance-general@radiance-online.org  
> > > > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)
> > > 
> > > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > > Radiance-general mailing list  
> > > Radiance-general@radiance-online.org  
> > > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)
> > 
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > Radiance-general mailing list  
> > Radiance-general@radiance-online.org  
> > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)

---

<div class="post-metadata">

**Author:** ![Thomas\_Bleicher2](https://discourse.radiance-online.org/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@Thomas\_Bleicher2](https://discourse.radiance-online.org/u/Thomas_Bleicher2)\
**Post date:** [August 27, 2015, 12:35am UTC](https://discourse.radiance-online.org/t/strange-artifacts-in-rendering-and-yosemite-bug/4302/7 "2015-08-27T00:35:10Z")

</div>

And I thought app containers were today's next big thing for tomorrow ...

But then, I'm usually behind on those things.

> **···**
>
> On Wed, Aug 26, 2015 at 11:43 AM, Randolph M. Fritz \<rmfritz3@gmail.com\> wrote:
> 
> > Google offers the "Native Client" SDK  
> > ([https://developer.chrome.com/native-client\](https://developer.chrome.com/native-client%5C)), which supports  
> > compilation and download of code with gcc (wince) and a set of  
> > non-Unix APIs (double wince.) Also, of course, one can just work with  
> > the base Linux on ChromeOS, bypassing the browser completely.
> > 
> > So far as I can see, these tools aren't much used yet; ChromeOS is not  
> > a major development platform. But they are there and at the rate the  
> > major platforms are diverging from general computing applications,  
> > they may be all that will be left in a few years. ☹  
> > --  
> > Randolph M. Fritz, Lighting Design and Simulation  
> > +1 206 659-8617 || rmfritz3@gmail.com
> > 
> > On Mon, Aug 24, 2015 at 9:15 PM, Greg Ward \<gregoryjward@gmail.com\> wrote:  
> > \> It will be interesting to see what ChromeOS develops into. Right now,  
> > it's more of a browser manager for accessing online tools, and doesn't have  
> > much in the way of compilers or a runtime environment to speak of. Kind of  
> > a waste of a laptop, if you ask me....  
> > \>  
> > \> -Greg  
> > \>  
> > \>\> From: "Randolph M. Fritz" \<rmfritz3@gmail.com\>  
> > \>\> Subject: Re: [Radiance-general] strange artifacts in rendering (and  
> > Yosemite bug)  
> > \>\> Date: August 24, 2015 4:53:04 PM PDT  
> > \>\>  
> > \>\> Sigh. I think in a few more years, anyone who is interested in  
> > \>\> scientific computing, rather than business functions or social  
> > \>\> networking, is going to be running ChromeOS.  
> > \>\> --  
> > \>\> Randolph M. Fritz, Lighting Design and Simulation  
> > \>\> +1 206 659-8617 || rmfritz3@gmail.com  
> > \>\>  
> > \>\>  
> > \>\> On Fri, Aug 21, 2015 at 4:45 PM, Greg Ward \<gregoryjward@gmail.com\> \> wrote:  
> > \>\>\> 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@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:  
> > \>\>\>\>  
> > \>\>\>\> [Release 5.0.a.4 · NREL/Radiance · GitHub](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@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@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@gmail.com\<mailto:gregoryjward@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.  
> > \>\>\>  
> > \>\>\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > \>\>\> Radiance-general mailing list  
> > \>\>\> Radiance-general@radiance-online.org  
> > \>\>\> [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)  
> > \>\>  
> > \>\> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > \>\> Radiance-general mailing list  
> > \>\> Radiance-general@radiance-online.org  
> > \>\> [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)  
> > \>  
> > \> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > \> Radiance-general mailing list  
> > \> Radiance-general@radiance-online.org  
> > \> [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)
> > 
> > \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_  
> > Radiance-general mailing list  
> > Radiance-general@radiance-online.org  
> > [http://www.radiance-online.org/mailman/listinfo/radiance-general](http://www.radiance-online.org/mailman/listinfo/radiance-general)
