Diving into dangerous tides: The impact of galaxy cluster tidal environments on satellite galaxy mass densities

Open Access

Table 1.

Measurements of ℜ_⋆ in nearby environments and simulations.

System	[i] ℜ_⋆ [kpc] (R_vir)	[ii] ℜ_⋆ [kpc](R_vir)
Fornax cluster	$380_{- 8}^{+ 16} (0.35)$ $380^{+16}_{-8}\,(0.35)$	$392_{- 6}^{+ 7} (0.36)$ $392^{+7}_{-6}\,(0.36)$

Virgo cluster (A)	$612_{- 55}^{+ 127} (0.39)$ $612^{+127}_{-55}\,(0.39)$	$612_{- 22}^{+ 21} (0.39)$ $612^{+21}_{-22}\,(0.39)$

Milky way	$78_{- 1}^{+ 38} (0.36)$ $78^{+38}_{-1}\,(0.36)$	$118_{- 4}^{+ 3} (0.54)$ $118^{+3}_{-4}\,(0.54)$

Andromeda (M31)	$102_{- 12}^{+ 24} (0.49)$ $102^{+24}_{-12}\,(0.49)$	$95_{- 7}^{+ 14} (0.46)$ $95^{+14}_{-7}\,(0.46)$

Fornax-type (TNG50) (2D)	$481_{- 58}^{+ 86} (0.45)$ $481^{+86}_{-58}\,(0.45)$	$462_{- 9}^{+ 7} (0.42)$ $462^{+7}_{-9}\,(0.42)$

Fornax-type (TNG50) (3D)	$595_{- 19}^{+ 74} (0.54)$ $595^{+74}_{-19}\,(0.54)$	$542_{- 18}^{+ 35} (0.49)$ $542^{+35}_{-18}\,(0.49)$

Virgo-type (TNG100) (2D)	$846_{- 20}^{+ 66} (0.41)$ $846^{+66}_{-20}\,(0.41)$	$889_{- 19}^{+ 19} (0.43)$ $889^{+19}_{-19}\,(0.43)$

Virgo-type (TNG100) (3D)	$828_{- 68}^{+ 50} (0.40)$ $828^{+50}_{-68}\,(0.40)$	$914_{- 11}^{+ 11} (0.44)$ $914^{+11}_{-11}\,(0.44)$

Virgo-type (EAGLE) (2D)	$747_{- 74}^{+ 96} (0.51)$ $747^{+96}_{-74}\,(0.51)$	$707_{- 17}^{+ 20} (0.50)$ $707^{+20}_{-17}\,(0.50)$

Virgo-type (EAGLE) (3D)	$823_{- 59}^{+ 59} (0.58)$ $823^{+59}_{-59}\,(0.58)$	$745_{- 14}^{+ 16} (0.52)$ $745^{+16}_{-14}\,(0.52)$

Notes. The adopted virial radii for each system are: Fornax 1075 kpc (Schuberth et al. 2010), Virgo A 1550 kpc (McLaughlin 1999), M31 207 kpc (Tamm et al. 2012), MW 216 kpc (Bland-Hawthorn & Gerhard 2016; Shen et al. 2022), Fornax-type TNG50 cluster 1115 kpc, Virgo-type cluster TNG100 2079 kpc, and Virgo-type cluster EAGLE 1442 kpc.

Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.

Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.

Initial download of the metrics may take a while.