[DAMD-126] Specify start value for AG camera ID (agId) Created: 17/Dec/21  Updated: 18/Dec/21  Resolved: 18/Dec/21

Status: Done
Project: Data Model
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: hassan Assignee: hassan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Story Points: 1
Sprint: 2DDRP-2021 A12

 Description   

The datamodel.txt mentions the AG Camera ID agId for the guidestar information in the pfsDesign and pfsConfig entities, but not explicitly the start value (0 or 1).

Specify what the start value should be.



 Comments   
Comment by hassan [ 17/Dec/21 ]

Following discussions between Yoshida, Hiroshige, yuki.moritani and cloomis, it has been agreed that the agId should start at 0.

Yoshida, Hiroshige comments:

I don't know a definitive answer. Certainly, it is more convenient
internally to use a zero-based numbering system (e.g., for indexing
arrays), and that is what I do in the current implementation of the AG
subsystem and opDB/FITS data it generates. On the other hand, the AG
cameras are currently numbered 1 through 6, so we may eventually need to
convert between zero-based and one-based numbering systems somewhere,
likely when data products are generated, consumed, and/or presented.

Comments from Craig:

I don’t feel very strongly about it. Given the choice I always prefer 0-based. But it is true and unchangeable that all the PFI ids (cobras, fibers, holes, modules, boards, fields, etc) are 1-based. If we will really talk about the AGs as part of the PFI we should probably make them 1-based. But I think we will not: the AGs are imagers and simply set the field. So I vote for 0-based.

Comment by hassan [ 18/Dec/21 ]

Trivial documentation update. Merged to master without review.

Generated at Sat Feb 10 15:34:32 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.