The Pulse-Sequence Instrument Control Tool. Developing scripts to allow string-based input to Labber for more flexible control over pulse sequence configurations.
Starting up a single instance of the MultiPulse driver will create a MultiPulse log file (by default, although this can be disabled). There is no limit on the size of this file or any form of auto-breakpoint to generate a new one, so if the instrument runs continuously for many experiments, it can easily generate logfiles that run into hundreds of MB, if not GB.
This can be mitigated by forcing a new logfile to start after a certain condition, eg after N hours or N entries written.
Original report by Samuel Wolski (Bitbucket: 557058:90b732eb-6ab1-4b27-9495-eb00eafde259, GitHub: samwolski).
Starting up a single instance of the MultiPulse driver will create a MultiPulse log file (by default, although this can be disabled). There is no limit on the size of this file or any form of auto-breakpoint to generate a new one, so if the instrument runs continuously for many experiments, it can easily generate logfiles that run into hundreds of MB, if not GB.
This can be mitigated by forcing a new logfile to start after a certain condition, eg after N hours or N entries written.