This branch now include additional functionality to compress the output halo catalog and use the compressed catalog to load.
An example notebook under sahyadri-sandbox/scripts/post-process/SahyadriCompression.ipynb show how to use the new feature and effect of these on the power spectrum measurements as well as the difference in halo position distribution before and after compression.
This branch also changes the snapshot reader a little bit where it makes it possible to initialise the snapshot reader class without need to have snapshot available on disk. This has no effect on the usual call only add additional argument called read_header.
During this process I realised that the field names in halo reader is not exactly the same as the field name in the halo file header. Currently fits version uses the halo file header so there are differences such as mvir and Mvir_all will mean the same things. It will be good to homogenise these and use consistent names for the field everywhere. Unless there is strong reason, I would vote for using the names in rockstar that will give also unique definition from rockstar documentations late on.
This branch now include additional functionality to compress the output halo catalog and use the compressed catalog to load.
An example notebook under sahyadri-sandbox/scripts/post-process/SahyadriCompression.ipynb show how to use the new feature and effect of these on the power spectrum measurements as well as the difference in halo position distribution before and after compression.
This branch also changes the snapshot reader a little bit where it makes it possible to initialise the snapshot reader class without need to have snapshot available on disk. This has no effect on the usual call only add additional argument called read_header.
During this process I realised that the field names in halo reader is not exactly the same as the field name in the halo file header. Currently fits version uses the halo file header so there are differences such as mvir and Mvir_all will mean the same things. It will be good to homogenise these and use consistent names for the field everywhere. Unless there is strong reason, I would vote for using the names in rockstar that will give also unique definition from rockstar documentations late on.