-
Type: Bug
-
Status: Open (View Workflow)
-
Priority: Normal
-
Resolution: Unresolved
-
Component/s: pfs_utils
-
Labels:None
-
Story Points:1
From the docString, the pfs_utils function FiberIds.xyForCobras assumes some 0-indexed cobra identifier, but the code actually assumes fiberId (but 0-indexed, not 1-indexed as the actual fiberId identifier is):
Accessing the x, y coordinates for a given cobra by fiberId is IMO useful. So I propose to keep the function, but change the docString to assume a 1-indexed fiberId, and correct the implementation such that it works with a 1-indexed fiberId.