Skip to content

Clean up the boundaries between shear_psf_leakage, cs_util & sp_validation #77

Description

@cailmdaley

Umbrella for getting a cleaner split across the three UNIONS weak-lensing repos: shared concerns live in the shared library (cs_util), analysis/validation logic stays in the analysis repos, and dependency arrows point analysis → library, never the reverse.

  • cs_util — shared library of tested primitives (size, shape, cosmology, plotting)
  • sp_validation — catalogue validation + cosmology inference
  • shear_psf_leakage — PSF-leakage calculation

The same concerns keep getting re-implemented in the wrong layer. Sub-issues track each instance:

— Claude on behalf of Cail

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions