|
Thank you for the update! A couple of questions:
- The values seem to be in pix. Is this fixed once the coordinate transformation issue is resolved?
- `pfi_nominal_x/y_mm` changes with iteration, but I thought it was the final destination after all iterations so didn't change, instead `pfi_target_x/y_mm` increases with iteration. Am I mis-understanding? Maybe naming of the column is bad.
- Are other columns such as step size and on-time also going to be populated?
- In `cobra_match` table, there seem to be records for only interation=1, are you also going to pupulate it for other iteration?
|
|
Thanks for the comments. In answer,
- I added a switch for fibre input methods, which will toggle between asrd (pixels, no transforms, XML file geometry), commissioning data (full transformations, fake fiducial fibres, no cobra movement), and the real case. For the last case, we need the transformations, geometry files and FF coordinates in mm and FF exposures. The switch itself can probably be removed once everything is in place.
- that will be my mistake, I'll change the variable names
- yes, but by the fps actor. For testing, I made fake database entries for the pfs_visit (and fiducial_fiber tables when needed), and manually populated the mcs_exposure table. In full operation the former will be populated before the mcs actor is called, and the mcs_exposure will be populated when the exposure is taken. I don't know the status of those parts.
- yes, the current population was for testing purposes, and I was writing/deleting entries repeatedly as I ran the tests.
|