Hi Andrew,

I'm not sure about that. One thing that this requires is building rockstar-galaxies instead of the old rockstar. If you follow the instructions in yt-astro-analysis.readthedocs.io and just substitute rockstar-galaxies, hopefully that will do the trick. Otherwise, we'll have to fish through it.

Britton

On Tue, Jul 7, 2020 at 5:53 AM Andrew Emerick <aemerick11@gmail.com> wrote:
Hey Britton,

Thanks for this! Either method of doing this is fine with me. Though I just tried pulling your PR and installing with the usual `pip install -e .` and got an immediate error:

    ValueError: 'yt_astro_analysis/halo_finding/rockstar/rockstar_interface.pyx' doesn't match any files

If there isn't a quick fix for this then I'll ping you on slack (direct message or in one of the channels?)



Best,
Andrew
---
Pasadena Fellow in Theoretical Astrophysics
Carnegie Observatories
California Institute of Technology


On Mon, Jul 6, 2020 at 9:37 PM Britton Smith <brittonsmith@gmail.com> wrote:
Hi Andrew,

Currently, running Rockstar through the HaloCatalog interface doesn't support analyzing the whole simulation as a time series, which is what you need for it to increment the output number. This is also what you'll need if you want to make merger trees. The way to do this is by calling the RockstarHaloFinder directly. I can share a script to do that. However, I have an open PR to yt_astro_analysis that enables just what you're looking for. It works fine, but is just missing tests and docs. If you'd like to try it, it's here:
If you're interested, I can share scripts on the slack channel.

Britton

On Tue, Jul 7, 2020 at 3:48 AM Andrew Emerick <aemerick11@gmail.com> wrote:
Hello all,

I'm just getting into running halo finders (namely rockstar) using yt's astro analysis package and cannot figure out how to have it such that each successive run on of rockstar does not overwrite previous runs.

I've been following the "Running Rockstar to Find Halos on Multi-Resolution-Particle Datasets" and both the HaloCatalog.create() and the RockstarHaloFinder.run() methods seem to overwrite everything in the output directory. One obvious fix here is to just have a different output directory for each dataset, but I had thought the indexes in the rockstar output files (e.g. "halos_0.0.ascii") and the list in "datasets.txt" were there to have the results from multiple datasets housed in the same directory.

And I didn't see any obvious parameters I could pass either of the above functions to specify a desired output index. 

Is this possible? Or should I just write to separate folders for each dataset?



Best,
Andrew
---
Pasadena Fellow in Theoretical Astrophysics
Carnegie Observatories
California Institute of Technology
_______________________________________________
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: aemerick11@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: brittonsmith@gmail.com