Re: MERGERTREE option with LIGHTCONE output

From: Volker Springel <vspringel_at_MPA-Garching.MPG.DE>
Date: Tue, 15 Jun 2021 15:15:00 +0200

Hi Rob,

Yes, this was an unfortunate dependence ultimately introduced as side-effect of the REARRANGE_OPTION. I have fixed this compilation problem now, i.e. LIGHTCONE_PARTICLES should compile again without MERGERTREE.


> On 13. Jun 2021, at 16:30, Robin Booth <> wrote:
> Hi Volker
> I am attempting a Gadget4 build with the on-the-fly LIGHTCONE_PARTICLES option enabled. The build was failing due to a missing reference to the mergertree class. It would appear that this is necessary because the lightcone_particle_io function definition (in lightcone_particle_io.h) includes a pointer to mergertree as one of its parameters. I am not entirely clear as to why this is required, but assuming that it is necessary, (whether or not sub-halos are required in the lightcone output), then I have to include the MERGERTREE build option in the build config file in order for the appropriate header to be included in the compilation. This being the case, perhaps this could be made explicit in the LIGHTCONE section of the documentation file?
> Regards
> Robin
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> with a subject of: unsubscribe gadget-list
> A web-archive of this mailing list is available here:
Received on 2021-06-15 15:15:01

This archive was generated by hypermail 2.3.0 : 2023-01-10 10:01:32 CET