Skip to content

DM-53254: Specify schema to use for formatting output catalogs #248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
isullivan merged 2 commits into from
Dec 4, 2025
Merged

DM-53254: Specify schema to use for formatting output catalogs #248

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
32f3981
Set default schema for APDB
isullivan Nov 20, 2025
1587612
Generalize schema name
isullivan Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion pipelines/_ingredients/ApPipe.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,8 @@ tasks:

connections.diaSourceTable: dia_source_detector
doRemoveSkySources: True
doUseApdbSchema: True # Force the table columns to match the APDB definition in sdm_schemas
doUseSchema: True # Force the table columns to match the APDB definition in sdm_schemas
schemaFile: "apdb.yaml"
Copy link
Member

@ctslater ctslater Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if you make the change I proposed on pipe_tasks, you'll need to specify the schemaName here as well. (Otherwise it's weird that apdb.yaml behaves differently)

getRegionTimeFromVisit:
class: lsst.pipe.tasks.getRegionTimeFromVisit.GetRegionTimeFromVisitTask
config:
Expand Down