[FLASH-USERS] Strange discrepancy in Dark Matter structure of cosmological simulation

[Stöckl, Josef]

Hi John,

Thanks for your suggestions!

1) We excluded the Hydro for two reasons: the Hydro has usually basically no effect on the DM particles (especially not on the positions where matter concentrates), and we used both split/PPM and unsplit/StaggeredMesh without any change in the outcome.

2) We used the unsplit and split driver by choosing split/PPM or unsplit/StaggeredMesh. Unfortunately I already deleted the PPM data, but I have setup another simulation with split/PPM, which should be finished by tomorrow.

3) We will try this and report back.

4) I've attached and uploaded the setup_call and setup_units files.

Cheers,
Josef

________________________________
Von: John ZuHone [jzuhone at milkyway.gsfc.nasa.gov]
Gesendet: Sonntag, 08. September 2013 15:48
An: Stöckl, Josef
Cc: flash-users at flash.uchicago.edu
Betreff: Re: [FLASH-USERS] Strange discrepancy in Dark Matter structure of cosmological simulation

Josef,

First, thank you for the very thorough investigation you've done of this problem.

I did have a few thoughts on maybe how to try to weed this one out:

1) I wonder a little bit about this:

Since this simulation basically only includes cosmology, self-gravity, active particles and hydro, we can only make out three possible points, which could influence the DM evolution: the cosmology, the gravity or the LeapfrogCosmo unit.

Why not hydro? Certainly the baryonic component is very small by mass, but in some collapsed regions the effect would not be completely insignificant. I'm guessing you're right, but I would just throw that one out there for consideration.

2) Which Driver unit are you using? Split or Unsplit? Have you tried this with the other one?

3) Could you try setting up the Zeldovich pancake problem (without hydro) in all three codes? This should provide a clean, unambiguous point of comparison.

4) Thanks for sending the flash.par, but could you also send along the setup_units and setup_call files? I'd like to see what units are being employed.

I think that somewhere between these we could get to the bottom of this.

Best,

John

On Sep 7, 2013, at 10:20 AM, Stöckl, Josef <Josef.Stoeckl at uibk.ac.at<mailto:Josef.Stoeckl at uibk.ac.at>> wrote:

Dear FLASH users and devs,

We have been conducting some comparisons of cosmological simulations conducted with FLASH 4.0.1, Gadget-2 and Enzo. We set up a cosmological volume of 60 Mpc/h box size with Planck cosmological parameters and evolve these initial conditions in all three codes. For the grid based codes (FLASH, Enzo) we used 256^3 resolution, and for Gadget-2 we used 256^3 DM particles and 256^3 gas particles.

In doing so we noticed that the dark matter structure FLASH shows a significant difference to both Enzo and Gadget-2, while those two codes show practically perfect agreement. I have attached some projection plots at redshift z=0 to show you the differences. As you can see, it seems as if the DM structure is less evolved in FLASH. To see, if this is discrepancy is specific to FLASH 4.0.1, we also tried FLASH 3.1, but there is no change to be seen there.

Since this simulation basically only includes cosmology, self-gravity, active particles and hydro, we can only make out three possible points, which could influence the DM evolution: the cosmology, the gravity or the LeapfrogCosmo unit.

We tried to check the cosmology unit by comparing the dt/dz, z, t and tend values and the timesteps that the simulation takes, but everything is in very good agreement with our calculations and also Enzo. So at least in terms of general cosmology there doesn't seem to be a problem there.

For checking the gravity unit, we switched from Multigrid to bhtree, but this did change absolutely nothing - the agreement between the two gravity units is very good. So we are inclined to exclude the gravity unit as the culprit.

This leaves us basically with the LeapFrogCosmo unit as the only point left, where things could go wrong.

I have checked everything that I can think of in terms of reading the ICs wrongly into FLASH, but all my checks turn out well (overall mass, min/max/avg density, particle masses, crit dens,...). To further exclude me as a source of error, a colleague also started with a FLASH 4.0.1 vanilla version from scratch and implemented the IC reading himself, but this also leads to the same results. The ICs have been filled in by assuming both distances and masses to be comoving cgs, but with the configured cosmology (aka not "over h").

Since the structures seemed less evolved to us, we decided to try running the simulation into the future and set redshift z = -0.5 as the final z. The result is given as the sim1-future* attachment, and to our surprise, at this point the FLASH structures match the other two codes structures (with those at z=0).

We would be thankful for any insights into this, since we are at our wits end.

Cheers,
Josef

The attachments can also be found at http://astro-staff.uibk.ac.at/~josef/work/comparison/flash-users/ together with the initial condition gadget-2 snapshot file ics_* and the resulting FLASH checkpoint 0000 file for simulation 1.

Attachments:
sim1_*   ... the simulation 1 comparison projection plots
sim2_*   ... the simulation 2 comparison projection plots
sim1-future_*   ... simulation 1 evolved until z = -0.5
flash.par   ... simulation 1 flash.par with comments removed


----------------------------------------------
Dr. Josef Stöckl
Institute of Astro- and Particle Physics
Technikerstrasse 25/8
6020 Innsbruck
Austria

Phone:  +43 512 507 52020
E-Mail: josef.stoeckl at uibk.ac.at<mailto:josef.stoeckl at uibk.ac.at>
<sim1_enzo_Projection_z_Density.png><sim1_enzo_Projection_z_dm_density.png><sim1_flash4_Projection_z_Density.png><sim1_flash4_Projection_z_pden.png><sim1_gadget_Projection_z_Density.png><sim1_gadget_Projection_z_dm_density.png><sim1-future_flash4_Projection_z_Density.png><sim1-future_flash4_Projection_z_pden.png><sim2_enzo_Projection_z_Density.png><sim2_enzo_Projection_z_dm_density.png><sim2_flash4_Projection_z_Density.png><sim2_flash4_Projection_z_pden.png><sim2_gadget_Projection_z_Density.png><sim2_gadget_Projection_z_dm_density.png><flash.par>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20130908/eb9f1d48/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: setup_call.txt
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20130908/eb9f1d48/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: setup_units.txt
URL: <http://flash.rochester.edu/pipermail/flash-users/attachments/20130908/eb9f1d48/attachment-0001.txt>