Hard code exposure max in obs_lsst

Description

In https://rubinobs.atlassian.net/browse/DM-50002 we removed the dependency of exposure ID on controller. This inadvertently changed the definition of exposure_max to make it inconsistent with earlier data and also forcing confusing dimension record changes on everyone. Restore the original values for consistency.

Issue Matrix

hide

Activity

Show:

Steve Pietrowicz

April 11, 2025 at 6:08 PM

Looks fine. Straight-forwarded changes, no changes requested.

Jim Bosch

April 11, 2025 at 4:40 PM

Backport approved on the basis that this is a fix for an already-backported ticket, and it won’t affect pipelines. Please do the backport ASAP as we’d like to get what we hope will be the final release candidate before v29.0.0 going immediately afterwards.

Tim Jenness

April 11, 2025 at 4:23 PM

@Kian-Tat Lim this restores the behavior of last week.

@Jim Bosch can you please approve for backporting since we want to fix it in v29 as well.

@Michael Reuter / @Steve Pietrowicz this will lead to an error again when you register the instrument after next week's weekly if the update happened this week but it will restore the status quo and is safe to do.

Resize issue view side panel

Done

Pinned fields

Click on the next to a field label to start pinning.

Details

Assignee

Tim Jenness

Reporter

Tim Jenness

Labels

Reviewers

Steve Pietrowicz

Story Points

0.5

RubinTeam

Data Engineering

Components

obs_lsst

Parent

DM-46243 FY25/1 Data Engineering Tooling and Support

Priority

Undefined

Checklist

Created April 11, 2025 at 3:40 PM

Updated April 11, 2025 at 7:05 PM

Resolved April 11, 2025 at 7:05 PM