Hi Salome,
Great to hear that's solved.
When running the halo finders through the HaloCatalog, keyword arguments
meant for the halo finder are passed via the "finder_kwargs" keyword. This
should be a dictionary of all keywords meant to passed on. In your case,
this would look something like:
finder_kwargs={"ptype": "all"}
There is more documentation here:
https://yt-astro-analysis.readthedocs.io/en/latest/halo_catalogs.html#halo-f...
Note, this is for using the yt_astro_analysis, which is an external package
that has replaced the internal yt analysis modules. You can find more
information on installation and modifying your imports in those docs.
Britton
On Thu, May 23, 2019 at 1:07 PM Salome Mtchedlidze
Hi Britton,
Thank you very much, turns out that it was the problem. I have one more question - I wanted to create not only dm halos but visible mass halos as well. I was following these instructions:
http://yt-project.org/doc/reference/api/yt.analysis_modules.halo_finding.hal...
where for HOP halo finder it was said that dm_only is depreciated and I should use ptype =all ifor including all particles. I tried this with the code:
hc = HaloCatalog(data_ds=data_ds, finder_method='hop', ptype=all, output_dir="halo_catalogs/..../")
but it was giving me the error:
__init__() got an unexpected keyword argument 'ptype'
I tried this once I updated the yt version but the result was same. _______________________________________________ yt-users mailing list -- yt-users@python.org To unsubscribe send an email to yt-users-leave@python.org