[INSTRM-523] Provide visualization code for MCS Engineering run Created: 12/Oct/18  Updated: 09/Nov/18  Resolved: 09/Nov/18

Status: Done
Project: Instrument control development
Component/s: ics_mcsActor
Affects Version/s: None
Fix Version/s: None

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


 Description   

Please provide visualization code for MCS Engineering run in Oct 2018



 Comments   
Comment by hassan [ 12/Oct/18 ]

Current development is available on master:

https://github.com/Subaru-PFS/ics_mcsActor/tree/master/python/mcsActor/Visualization

Comment by hassan [ 12/Oct/18 ]

chyan and karr will do tests over the next few days to demonstrate the current code.

Comment by hassan [ 15/Oct/18 ]

Below are notes from karr (email [PFS-ics:01522] sent 2018-10-11) providing the most recent status:

Visualization notebook tested on Subaru system (running remotely)

  • displaying notebook, importing and running the code, reading
    sets of centroids from the database, running them through the code.
  • added more intelligent setting of parameters for centroiding, particularly
    the threshold value for finding spots. The MHS command setCentroidParameters
    will read values from keywords in the command, otherwise will attempt to calculate a
    reasonable threshold (based on what works with lab data), and if there is no image in memory
    will set a value that will at least run.
  • most recent version has been pushed to ics_mcsActor master branch

Things left to test (as was in my email exchanges with Chi-Hung and Craig).

  • reading the image from the database (getting the correct filename from the frameID and reading the image from the remote disk).
  • fix ginga plugin in notebook so it displays remotely (interactive viewing of the image during the run is important). This is probably an issue of setting the hostname/ports correctly.
  • I have a few updates to finish on my end, which include a more manual option for registering the spots to the mask (in case of odd data or unexpected behaviour in the code).
  • check the notebooks running on shell-ics (we were testing on mcs computer earlier because shell-ics was down)
Comment by hassan [ 08/Nov/18 ]

karr: I presume this ticket is done. Can we close this now?

Comment by hassan [ 09/Nov/18 ]

As far as the engineering run Oct 2018, this issue is resolved. Further work in the visualization code should be raised as separate tickets.

Generated at Sat Feb 10 16:25:53 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.