https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-737 Instrument control development <p><tt>ics_mcsActor</tt> is currently commanded directly by Gen2, so self-allocates frameIds. It has no context about its exposures (how many are being taken, etc.) so wastefully allocates full 100-frame visits for each frame.</p> <p>When we switch to <tt>ics_fpsActor</tt> control, that will be able to fetch/receive a visit and tell the mcsActor about the individual frames within that.</p> <p>Implement this. The only trick is that in operation, the fpsActor itself will be told what the active visit is. But that is pretty minor.</p> INSTRM-737

Implement correct visitId/frameId logic for the FPS/MCS system.

Task Normal Done Done cloomis cloomis Thu, 22 Aug 2019 00:34:32 +0000 Tue, 27 Aug 2019 14:23:57 +0000 Tue, 27 Aug 2019 14:23:57 +0000 ics_fpsActor ics_mcsActor 0 1 <p>We are implementing an <tt>ics_iicsActor</tt>, which is by design the main consumer of visits from Gen2, and which passes those visits down to the <tt>fpsActor</tt>, <tt>spsActor</tt>, and <tt>agccActor}}s. So in this case it will be the {{iicActor</tt> which does the allocation.</p> <p>ics_iicActor merged at bac8542, tagged 1.0.0, installed<br/> ics_fpsActor merged at 0444f19, tagged 1.2.1, not installed<br/> ics_mcsActor merged at 357a85e, tagged 1.4.9, not installed.</p> <p>Basically, there is a <tt>iic fpsLoop cnt=N</tt> command which controls the <tt>fps testLoop</tt> command, which in turn commands individual <tt>ics expose</tt> commands. Unlikely to be finished, but is functional enough to hand back for other FPS work. Please note, <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=chyan" class="user-hover" rel="chyan">chyan</a></p> Development Rank 0|zy005k: Story Points 1.0