[Radiance-general] rcontrib malloc error

Rob Guglielmetti rob.guglielmetti at gmail.com
Thu Mar 17 16:30:05 PDT 2016


Thanks man! I did mean rmtxop, and I will give that dctimestep idea a go!

- Rob 

> On Mar 17, 2016, at 3:45 PM, Greg Ward <gregoryjward at gmail.com> wrote:
> 
> Hi Rob,
> 
> I don't think rfluxmtx reads large matrices into memory.  It could write a too-large matrix to disk as the output of rcontrib, but neither process holds the matrices in memory.  Maybe you meant rmtxop?  That will hold two double (64-bit) color (x3) matrices in memory at a time, which could be a problem for certain very large matrices.  You might try dctimestep for matrix multiplication.  It uses float (32-bit) color (x3) arrays, so half as much memory is required.  Also, it's more clever about skipping zero rows and columns in your matrix, which is good for daylight calculations that include nighttime hours.
> 
> -Greg
> 
>> From: "Guglielmetti, Robert" <Robert.Guglielmetti at nrel.gov>
>> Subject: Re: [Radiance-general] rcontrib malloc error
>> Date: March 17, 2016 1:57:36 PM PDT
>> 
>> I'm currently struggling with memory issues -- of the volatile and non-volatile kind -- trying to get Radiance to play nicely on a server-based optimization framework, and making it Windoze-friendly. As a result of that last bit, I'm writing view/daylight matrices in ASCII, and they get large in a hurry. 7500 points worth of matrix, for a presumably annual (8760) input, is a BAF (big a** file).
>> 
>> I'm not seeing your errors specifically Galen, mine are all downstream; I either run out of disk space or hit memory errors when rfluxmtx tries to read these BAFs into memory for merging. But maybe we're both barking up the same tree in a sense? I dunno. But now you know why I have a headache today.
>> 
>> 
>> On 3/17/16, 2:39 PM, "Galen Burrell" <Galen.Burrell at arup.com<mailto:Galen.Burrell at arup.com>> wrote:
>> 
>> I'm running view matrix calculations using rfluxmtx/rcontrib for the 3-phase method and keep getting one of two errors:
>> 
>> 1)
>> rcontrib(2346) malloc: *** mmap(size=a really big number) failed (error code=12)
>> *** error: can't allocate region
>> *** set a breakpoint in malloc_error_break to debug
>> rcontrib: system - out of memory in samp_hemi: Cannot allocate memory
>> rcontrib: system - read error from render process
>> Killed: 9
>> 
>> 2)
>> rcontrib: system - read error from render process
>> Killed: 9
>> 
>> I can't establish a pattern for why/when these two errors occur.
>> 
>> Oddly, I don't always get the error with some gridpoint files (with 5900 points), but I consistently get it with another gridpoint file (with 7500 points).  I don't understand why grid size would influence memory though...?
>> 
>> System is Mac OS 10.7.5 (2 x 6-core); error repeats on my laptop with Yosemite installed
>> Latest Radiance HEAD release; although the error repeats on older versions from 6 months ago
>> rcontrib settings are: -n 12 -ab 12 -ad 100000 -lw 1e-5 -I+
>> 
>> Any clues on why I'm getting these errors?
>> 
>> Thank you!
>> 
>> Galen
>> 
>> 
>> ____________________________________________________________
>> Electronic mail messages entering and leaving Arup  business
>> systems are scanned for acceptability of content and viruses
>> 
>> _______________________________________________
>> Radiance-general mailing list
>> Radiance-general at radiance-online.org
>> http://www.radiance-online.org/mailman/listinfo/radiance-general
> 
> _______________________________________________
> Radiance-general mailing list
> Radiance-general at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-general



More information about the Radiance-general mailing list