Hi Carla,

It looks like RockstarHaloFinder accepts a keyword called "min_halo_size" which sets the minimum particle number for halos. The RockstarHaloFinder code writes its own config file, which is then passed to rockstar itself, so that's why modifying that file by hand doesn't do anything.

Britton

On Mon, Mar 8, 2021 at 9:29 AM C Bernhardt <bernhardt.phd@gmail.com> wrote:

Dear yt and rockstar users,

I recently installed the newest version of rockstar-galaxies as I had been using a much older version. Although the output reports a particle mass of 1.31418e+05 Msun/h, I don't see any halos smaller than 1e+08 Msun/h. I was expecting to get the minimum masses an order of magnitude lower. 

I see in the config includes MIN_HALO_OUTPUT_SIZE = 25, set as a default. I tried to change this parameter to 10 and restart from the beginning, but I run rockstar within yt with RockstarHaloFinder (yt.extensions.astro_analysis.halo_finding.rockstar.api), but my config file was overwritten by the defaults. Is this even the right approach? If so, how do I restart rockstar (more detailed than just rh.run(restart=True), please) with customized parameters within yt's RockstarHaloFinder?

Thanks in advance,

--

Carla Bernhardt

PhD Student

Universität Heidelberg

ZAH Institut für Theoretische Astrophysik

_______________________________________________
yt-users mailing list -- yt-users@python.org
To unsubscribe send an email to yt-users-leave@python.org
https://mail.python.org/mailman3/lists/yt-users.python.org/
Member address: brittonsmith@gmail.com

_______________________________________________
yt-users mailing list -- yt-users@python.org
To unsubscribe send an email to yt-users-leave@python.org
https://mail.python.org/mailman3/lists/yt-users.python.org/
Member address: bernhardt.phd@gmail.com