Skip to content

Umbrella analyses: lc cannot run at a parent that composes path-backed sub-analyses #209

Description

@lhparker1

A parent astra.yaml whose outputs are all from: aliases into analyses.<id>.path: sub-analyses (e.g. lightcone-vrecon-leakage) can be lc init'd, but lc status there fails:

Error: output id 'replication.catalog_ph002' contains a dot, so the manifest beside it could not be told from the output's own name.

The resolver inlines path-backed children under dotted ids, and assets.output_path then tries to place them under the parent's own results/. lc has no notion of an output living in a child project's results folder, so an umbrella is currently view-only: you write its universe by hand and run lc inside each part.

Wanted

  • lc status / lc materialize at the parent resolve a path-backed child's outputs to <path>/results/<child universe>/… and delegate runs to the child.
  • A clear error when a path-backed child is not configured in the parent's universe (today the TS SDK silently binds nothing, and viewers show every output as unmaterialized).
  • Related, astra-tools: astra universe generate at a parent should emit analyses.<id>.universe: <child's default> for path-backed children instead of omitting them, since that is the only shape that resolves.

Nothing in lc init should edit the parent's universe file from a child; the reference belongs where analyses.<id>.path: is added.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JY1S2BupvBMJJPifaYQop1

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions