There are a few things we will need to do before SM1 can/should be run at Subaru. Some will merit their own tickets, but I'll start with a text list. In rough order of time requirement.

1. Before we can acquire data:

• add pfs-data account at Subaru – that is the account which is used to write image files. (Done, INSTRM-588)
• change pfs and pfs-data user/group IDs on BEEs to match the Subaru LDAP numbers. (Done, INSTRM-800)
• move the LAM ics_dnsmasq MAC files to the Subaru directory; make sure names are there. (Done, INSTRM-801)
• add tables for SPS AIT to the Subaru opdb.
• install enuActor and all sps actors and programs. [Can probably run anywhere] (Done, INSTRM-806 INSTRM-816, INSTRM-803)

2. Before we can run cold:

• provide STS the datum [ID, name, help] bindings we have self-assigned in the alertsActor. (Done, INSTRM-804 INSTRM-820 INSTRM-821)
• install and wire in rough1 ics_roughActor. (Done, INSTRM-805 etc.)

3. Before we can call the instrument Subaru-compliant:

• change image locations to INSTRM-823 compliant /data/raw/YYYYMMDD/sps/ directories (INSTRM-831 +)
• change visit source from LAM's seqnoActor to gen2Actor/iicActor (INSTRM-862)
• wire in gen2 headers (INSTRM-863, INSTRM-466 (done))
• switch to iicActor control of the spsActor (top-level call in spsActor already exists) (INSTRM-789)
• adapt sequencing engine from spsait (INSTRM-931)
• migrate spsait commands to iicActor (INSTRM-933)
• add Gen2 .sk, etc for published IIC functions for SPS. (INSTRM-864)
• add Gen2 .sk, etc for engineering SPS functions (sps expose, etc). (INSTRM-865)
• convert spsaitActor, etc. to use the obDb visitSet, etc. tables for experiment/exposure logs. (INSTRM-866)

In that last group, some tickets must be closed before we can archive FITS files: INSTRM-831, INSTRM-862, INSTRM-863