That works great. Thanks!
On Thu, Jan 23, 2014 at 8:39 PM, Amit Murthy amit.mur...@gmail.com wrote:
The SharedArray object ha a field loc_shmarr which represents the backing
array. So S.loc_shmarr should work everywhere. But you are right, we need
to ensure that the SharedArray can be used
Thanks! I'm trying out a SharedArray solution now, but wondered if you can
tell me if there's an easy way to reimplement many of the convenience
wrappers on arrays for shared arrays. Eg I get the following errors:
shared_array[1,:]
no method getindex(SharedArray{Float64,2}, Float64,
The SharedArray object ha a field loc_shmarr which represents the backing
array. So S.loc_shmarr should work everywhere. But you are right, we need
to ensure that the SharedArray can be used just as a regular array.
On Fri, Jan 24, 2014 at 9:00 AM, Madeleine Udell
madeleine.ud...@gmail.comwrote:
1. The SharedArray object can be sent to any of the processes that mapped
the shared memory segment during construction. The backing array is not
copied.
2. User defined composite types are fine as long as isbits(T) is true.
On Thu, Jan 23, 2014 at 1:01 AM, Madeleine Udell
# Say I have a list of tasks, eg tasks i=1:n
# For each task I want to call a function foo
# that depends on that task and some fixed data
# I have many types of fixed data: eg, arrays, dictionaries, integers, etc
# Imagine the data comes from eg loading a file based on user input,
# so we can't
I have not gone through your post in detail, but would like to point out
that SharedArray can only be used for bitstypes.
On Wed, Jan 22, 2014 at 12:23 PM, Madeleine Udell madeleine.ud...@gmail.com
wrote:
# Say I have a list of tasks, eg tasks i=1:n
# For each task I want to call a function
