( http://code.google.com/p/consistent-trees ). This seems to be another reason to consider using it. Mike has some concerns about the parallelization scheme, which may not scale well he worries. However, Rockstar was run on the Aquarius Level 1 data which has 4.21 billion particles, so it is not completely devoid of scalability (though 4 is obviously different than the 68 that we are working with ).
Vfind/pos is in red, Rockstar in blue, and the blue particles were plotted second. A few things are clear here: Vfind/pos is identifying many more halos as individual halos (1118) than Rockstar (306), especially near the center, despite the fact that Rockstar keeps subhalos >20 particles, and Vfind/Pos subhalos with >30 (I could fix this later, it was a mistake). I am guessing that toward the center, the rockstar halos are identified has having a much bigger "Mass" than the Vfind halos. Possibly there is an adjustable parameter in the olapt step that could bring these into better alignment.
Vfind/pos seems to find nearly all of the Rockstar halos, but the reverse is not quite the case. I decided that Vfind is just plotting way more subhalos, so I first decided to rank them by central density (this is the ONLY quantity I have available in the .cen files, not Npart and not mass either), and plot the first N of them, so that I am plotting the same number of objects for the two finders.
This doesn't look very good, and we can understand why, because the halos toward the center are definitely going to have higher central densities on average, just as a selection effect... we can't find low central density subhalos contrasted against the parent toward the center of the parent. So in the ranking, I am preferentially selecting these central guys, and you can see them all bunched up there at the center. So... I wanted to see if I could make this look a little better. I ranked the Rockstar subhalos by number of particles, and started plotting only the most massive of them, and also plotting some arbitrary number of Vfind/pos halos, tuned to get the best matchup in the outer halos as I could manage. Here's a plot, but keep in mind this has been fiddled with to give visually not so terrible results.
This is starting to look somewhat more reasonable. I have plotted the 50 most massive Rockstar halos, and the 75 halos with highest central density from Vfind/pos. Aside from the weirdness at the center, there are about 35ish outer halos for which there is overlap, and around 10 in each color that the other finder did not identify (above the thresholds I set, they probably did find them overall).
So this tells us that yes, these things are doing approximately the same calculation, but there are non-trivial differences. One possible next step would be to try and match up subhalo "masses" from the olapt files (assuming the halo ids match those in the .cen files, I am not clear on this point). This would be smart because it's likely that central density and "mass" have quite a bit of scatter in their relationship, so these plots compare apples to oranges. However, there is a good bit of evidence in the literature that "mass" is not a good variable for subhalos. It is not stable or reliable, and does not match up well on an inter-algorithm basis, even in terms of rank ordering. There is evidence that vmax (max circular rotational velocity) is a much better variable to use. We do not currently compute this (that I know of) but we do compute a halo center, so it would not be so terrible to add such a calculation it to hproc or hpick. The magnitude of vmax will depend on 1) the center finding algorithm and 2) whether the mass in the background halo is included or not. However, it appears that the rank ordering for vmax is pretty robust according to the literature, so using it for both finders we can do a better side-by-side comparison. Rockstar already outputs this quantity.
Since rockstar appears to run on on this halo with only one processor, it will probably manage to be able (in parallel) to cope with even bigger halos in finite time, and we could consider simply moving forward with the project using Rockstar instead of Vfind/pos, rather than spending a lot of time working out what the origin of the differences may be. This depends on whether we believe there is something fundamentally interesting about the differences and/or we thing Vfind/pos is more well physically motivated than Rockstar.
Feel free to please please give me some feedback, especially on stuff in Red.


































































