00:59 <rjo> sb0: i transport further and further (each time returning to the points wehre my lasers are) to see how far i can transport the ion (before loosing it). we would usually also wrap each attempted target transport into a for i in range(100) loop and abort if we lost the ion.

01:00 <rjo> sb0: re in-use frames: i imagined begin() would memorize what has been begun, then prepare() knows it. but explicitly passing the frames to to prepare() is also fine.

01:01 <rjo> sb0: sorry. s/begin()/open_frame()/

01:02 <rjo> sb0: prepare() would clear that list after preparing them. that however sounds like a hidden sideffect. explicitly passing to prepare() is ok.

02:29 <sb0> rjo, since the frames/segments need to know about the core device they are already obtained from the pdq2 object via create_frame

02:31 <sb0> so the pdq2 object might as well do this memorizing of what frames have been created since the last call to prepare(), so the user doesn't have to list them

02:35 <sb0> but this removes the possibility to create a pool of frames in advance, and then select a few to load into the PDQs via prepare(). not sure if you'll ever need that...

09:14 <GitHub91> [migen] sbourdeauducq pushed 1 new commit to master: http://git.io/RDqOSg

09:14 <GitHub91> migen/master dbaeaf7 Florent Kermarrec: remove trailing whitespaces

09:15 <GitHub184> [misoc] sbourdeauducq pushed 1 new commit to master: http://git.io/e_E9Lw

09:15 <GitHub184> misoc/master 53ded72 Florent Kermarrec: remove trailing whitespaces

09:16 <GitHub7> [misoc] sbourdeauducq force-pushed master from 53ded72 to 20528c6: http://git.io/LjONPA

09:17 <GitHub78> [misoc] sbourdeauducq pushed 1 new commit to master: http://git.io/4eWhqg

09:17 <GitHub78> misoc/master 34ed315 Florent Kermarrec: remove trailing whitespaces

20:11 <rjo> sb0: might be useful but afaics you can do that by directly using the methods that prepare() would call.