Jubilee databases

The Jubilee project provides access to the databases which content the result of the Big jubilee simulation. The result of the simulation has been post-processed with the AHF, FOF and SO algorithms. Here we explain the databases layout in order to provide the basic information to work with these catalogs. The approximate size of each table is also provided in order to allow the user figure out how much information is dealing with and the fact that the time required to manage all this data could be very long.

 

AHF catalogs

The AHF database has been created running the AHF code (version XXX) on snapshots at redshifts 0.000, 0.509, 1.000 and 6.000 for the 6Gpc box. Consequently we have the database jubilee6GpcAHF with four different tables for each redshift. These are named AHFz0000, AHFz0509, AHFz1000 and AHF6000.

Available tables and sizes:

DatabaseName.TableNameNumber of RowsSize
jubilee6GpcAHF.AHFz0000 459,100,385 80 GB
jubilee6GpcAHF.AHFz0509 381,971,966 66 GB
jubilee6GpcAHF.AHFz1000 305,292,843 52 GB
jubilee6GpcAHF.AHFz6000 990,672 175 MB


The tables structure is as follow (underline means the column is indexed):

FieldTypeUnitsDescription
HaloId bigint(20) Unique identifier in the table. (Primary key)
npart int(11) Number of particles in halo
fMhires float Halo contamination
Xc float kpc/h Position
Yc float
Zc float
VXc float km/s Peculiar velocity of halo
VYc float
VZc float
Mvir float M(·)/h Mass of halo
Rvir float kpc/h Virial radius
Vmax float km/s Max velocity
Rmax float kpc/h Position of rotation curve maximum
sigV float km/s 3D velocity dispersion
lambda float Spin parameter (Bullock et al. 2001 definition)
Lx float |L|=1 Orientation of angular momentum vector
Ly float
Lz float
Eax float |Ea|=1
Eay float
Eaz float
b float b/a Second largest axis of moment of inertia tensor
Ebx float |Eb|=1
Eby float
Ebz float
c float c/a Third largest axis of moment of inertia tensor
Ecx float |Ec|=1
Ecy float
Ecz float
ovdens float Overdensity at virial radius
nbins int(11) Number of bins used for the profile
Ekin float M(·)/h (km/sec)2 Kinetic energy
Epot float M(·)/h (km/sec)2 Potential energy
mbp_offset float kpc/h Offset between most bound particle and halo centre
com_offset float kpc/h Offset between centre-of-mass and halo centre
r2 float kpc/h Position where ρr2 peaks
lambdaE float Classical spin parameter (Peebles’ definition)
v_esc float km/sec Escape velocity at Rvir
Phi0 float (km/sec)2 ϕ0 (cf. unbinding procedure)

 

 

FOF catalogs

The FOF database has been created running the Friend Of Friends algorithm on snapshots at redshifts 0.000, 0.509 and 1.000 for the 6Gpc box. Consequently we have the database jubilee6GpcFOF with three different tables for each redshift. These are named FOFz0000, FOFz0509 and FOFz1000.

Available tables and sizes:

DatabaseName.TableNameNumber of RowsSize
jubilee6GpcFOF.FOFz0000 542,225,296 19 GB
jubilee6GpcFOF.FOFz0509 510,195,856 18 GB
jubilee6GpcFOF.FOFz1000 445,147,825 16 GB


The tables structure is:

FieldTypeUnitsDescription
HaloId bigint(20) Unique identifier in the table. (Primary key)
Mvir float
x float Position
y float
z float
Vx float Velocity
Vy float
Vz float

 

 

SO catalogs [This section is under construction...]

The SO database has been created running the Spherical Overdensity algorithm on snapshots at redshifts from 0.000 to 9.611 for the 6Gpc box. Consequently we have the database jubilee6GpcFOF with ninety two different tables for each redshift.

Tables are named SOz0000 based on their corresponding redshift as usual. Moreover there is a global table providing access to the hole database named SOglobal. This has been done using MySQL partitioning by range over redshift column (for deeper information use the contact form)

 

Available tables and sizes:

DatabaseName.TableNameNumber of RowsSize
jubilee6GpcSO.SOz0000 542,225,296 19 GB
... ... ...
... ... ...