[INSTRM-1259] Add better accessors for SuNSS fiber info Created: 29/Apr/21 Updated: 18/Jun/21 Resolved: 18/Jun/21 |
|
| Status: | Won't Fix |
| Project: | Instrument control development |
| Component/s: | pfs_utils. |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | SuNSS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Reviewers: | cloomis | ||||||||||||||||
| Description |
|
The sunss column in the GFM carries all the info we need in a 3 character text field. We need to pick that apart for actual use. Question: do we want to always return imaging/diffuse and the fiber id as a pair? For the imaging/diffuse part, do we want "imaging"/"diffuse" strings or, say, an isImaging boolean? I think we never want a 1..254 sunss fiber id. |
| Comments |
| Comment by rhl [ 29/Apr/21 ] |
|
I don't care about "imaging"/"diffuse" v. isImaging as this gets transferred to the pfsConfig file; it's just a matter of how we write the pfsDesign file. I think we do want the 1..254 SuNSS fiberId as it tells me how to make images of the sky with SuNSS |
| Comment by cloomis [ 29/Apr/21 ] |
|
I should have stated that this is a bug fix as well as improvements. The sunss column is U3 ("i1", "d2", "emp") and needs to be parsed out before anything will work. |
| Comment by rhl [ 18/Jun/21 ] |
|
Work is done on |