Conventions
This page collects the geometric and shape conventions used throughout MeasureIA, for both the box and the lightcone. The mathematical estimators that use these quantities are defined on the Estimator definitions page.
Separation vector
For every position–shape pair the separation vector is defined as
i.e. pointing from the position (density) object to the shape object. This ordering is used consistently across all backends (box and lightcone, brute-force and tree). The line-of-sight separation \(\Pi\) is the component of \(\mathbf{s}\) along the line of sight and is binned signed over \((-\Pi_\mathrm{max}, +\Pi_\mathrm{max})\); the projected separation \(r_p\) is the perpendicular component.
Binning
The separation bins are fixed at initialisation and shared by every measurement on the object:
- Transverse / 3D separation (\(r_p\) for \(w\), \(r\) for the multipoles):
num_bins_rlogarithmic bins betweenseparation_limits[0]andseparation_limits[1](i.e. \(r_\mathrm{min}\) and \(r_\mathrm{max}\)). - Line of sight \(\Pi\):
num_bins_pilinear bins spanning the signed range \([-\Pi_\mathrm{max}, +\Pi_\mathrm{max}]\), with \(\Pi_\mathrm{max}\) set bypi_max. - \(\mu_r = \Pi/r\) (used for the multipoles):
num_bins_pilinear bins over \([-1, 1]\).
The bin coordinates written to the output (*_rp, *_pi, *_r, *_mu_r) are the bin midpoints.
Separations are in the units of the input coordinates: for a box initialised with the internal simulation
option these are Mpc/\(h\); for the lightcone the comoving distances are computed from the redshifts using the
chosen cosmology and can be converted with the over_h argument.
Radial (\(+\)) and cross (\(\times\)) shape components
The alignment signal is built from the shape components measured relative to the separation vector,
where \(\phi\) is the orientation of the projected separation vector relative to the shape (see below) and \(\epsilon\) is the shape magnitude (the ellipticity of the object).
Sign convention (intrinsic alignment). MeasureIA uses the intrinsic-alignment sign convention in which \(e_+ > 0\) means the major axis of the shape points along the separation vector (radial alignment). Radial alignment therefore produces \(w_{g+} > 0\). Note that this is the opposite sign to the weak-lensing tangential shear: \(e_+ = -\gamma_t\).
Shape input: box vs lightcone
The two entry points differ in how the shapes are supplied, but both end up as \((e_+, e_\times)\) through the relation above.
Box (MeasureIABox)
Shapes are given as a projected axis direction and an axis ratio:
Axis_Direction— the unit vector of the projected semi-major axis of each shape object;q— the projected axis ratio \(q = b/a\) (with \(a > b\)).
Here \(\phi\) is the angle between the projected separation vector \(r_p\) and the semi-major axis direction of the object, computed per position–shape pair. The magnitude \(\epsilon\) follows from \(q\) (see below). This branch is radial-positive by construction.
Lightcone (MeasureIALightcone)
Shapes are given directly as the two ellipticity/shear components e1 and e2. These must follow the
standard survey shear-catalogue convention: the components are defined on the local \((\mathrm{RA}, \mathrm{DEC})\)
axes, exactly as delivered by e.g. lensfit/metacal-style catalogues and as expected by
TreeCorr. Internally the radial and cross components are then
where \(\phi = \operatorname{arctan2}(\text{north}, \text{east})\) is the orientation of the projected separation vector in the internal (east, north) sky frame. As in the box case, the output \(w_{g+}\) is radial-positive (\(e_+ > 0\) for radial alignment).
Relation to TreeCorr
TreeCorr reports the tangential shear \(\gamma_t\), so its \(g\) has the opposite sign to the IA \(e_+\)
(\(e_+ = -\gamma_t\)). Comparing a MeasureIA lightcone \(w_{g+}\) against a TreeCorr NG measurement therefore
needs only the standard IA flip \(g \to -g\); no per-component sign change is applied to e1/e2.
Note also that a wrong chirality (swapping the handedness of e2) does not simply flip the sign of
\(w_{g+}\) — it replaces \(\cos 2(\phi_a - \phi_s)\) with \(\cos 2(\phi_a + \phi_s)\) and washes the signal out
to noise, which is a common cause of a "vague, noisy mismatch" against other codes.
Ellipticity definitions
The shape magnitude \(\epsilon\) is derived from the axis ratio \(q\), so this choice applies to the box only;
it is selected with the ellipticity argument of MeasureIABox.measure_xi_w and
MeasureIABox.measure_xi_multipoles. The lightcone takes e1/e2 directly and has no such argument. The two
definitions are:
'distortion'(default): \(\epsilon = \dfrac{1 - q^2}{1 + q^2}\)'ellipticity': \(\epsilon = \dfrac{1 - q}{1 + q}\)
Responsivity
When shapes are raw distortions/ellipticities (as in the box case, derived from axis ratios), the \(g+\) signal is calibrated by the responsivity factor \(2\mathcal{R}\), with
so that \(S_+D = \sum w_i w_j\, e_+(j|i)/(2\mathcal{R})\) (see Estimator definitions).
The correction is controlled by the responsivity argument: it defaults to True for the box (raw shapes) and
False for the lightcone (where e1/e2 are assumed to be already-calibrated shears). When switched off,
\(\mathcal{R} = 0.5\) so that \(2\mathcal{R} = 1\) and no calibration is applied. Only the \(g+\) correlations are
affected; the clustering (\(gg\)) signal is unchanged.
The differing defaults are deliberate rather than an oversight: they match what each input format usually
contains, so the common case needs no argument. Pass responsivity explicitly whenever your inputs do not
follow that pattern — for example responsivity=True on the lightcone when your e1/e2 are raw
distortions rather than calibrated shears, or responsivity=False on the box when the shapes you supply
have already been calibrated.