Hi,
Originally I was outputting something like 17 or 18 columns of attributes of my ellipsoids associated with the haloes, but I've ripped them out to the bare essential of just out putting the mass of halo and a "0" for attribute to narrow down the problem. So in this script I did nothing with the ellipsoids.
For each halo, the output should have for the first column the halo DM particle mass, the second column a zero.
The output when using
for halo in haloes:
The output when using
for sto, halo in parallel_objects(haloes, num_procs, storage = my_storage):
The original halo list from parallelHOP:
So there's agreement of the number of haloes with the "for halo in haloes" method and disagreement with the parallel_objects() method.
From
G.S.
in the DD0273_z5.00_halo_list.out file I have 24 lines, first two
On Fri, Mar 23, 2012 at 8:24 AM, Stephen Skory
<s@skory.us> wrote:
Hi Geoffrey,
>> haloes = LoadHaloes(pf, HaloListname)
>>
>> for sto, halo in parallel_objects(haloes, num_procs, storage = my_storage):
Can you paste the whole script? Thanks.
> Stephen might be able to shed some light on this, but I think
> LoadHalos will pre-assign processors to the halo objects, whereas
> parallel_objects will operate independently of that, distributing
> halos first come, first server.
In fact, LoadHaloes should not work that way. Each task should have a
full copy of the halos data, but initially only the data in the
HopAnalysis.out file, of course, the particles are loaded on demand.
I've been using something like what Geoffrey's trying to do for a
while with no issue. I'm hoping maybe there's something in Geoffrey's
script... but I've been wrong before.
--
Stephen Skory
s@skory.us
http://stephenskory.com/
510.621.3687 (google voice)