Hi Joe,
On 03/12/2015 01:43 AM, Joe Britton wrote:
Goals by beginning of May
===
Aim is to run penning trap experiment on ARTIQ
1) run ARTIQ on KC705 with legacy TTL/DDS system (16 TTL, 8 DDS)
Ethernet is working fine on the KC705 now - I have fixed the low
throughput bug.
On Saturday, March 14, 2015 12:13 AM, Joe Britton wrote:
We have a higher level of H2 in our trap than we would like. And, when
Dopper laser cooled the 9Be+ ions react chemically with background
Hydrogen gas and form 9BeH+. We can tolerate this but need to keep track
of what fraction of our 9Be+
On Friday, March 13, 2015 10:44 PM, Britton, Joe wrote:
4) functional parameter database
What do you mean?
It would be helpful to have a history for the parameter database. We
use this in the Penning experiment to feed forward on some aspects of
the experiment that drift over time (e.g.
c) which file and line of code was responsible for underflow
This is non-trivial to implement as it requires unwinding the stack, getting a
machine instruction address/LLVM instruction mapping from LLVM, and
adding a LLVM instruction mapping/Python AST node mapping to the
Ok. Can we assume you consider it a manual operation to extract the
duty cycle of a gpio in an experiment and how you use that number is
all left up to you? Then this sounds just like a use case for the
soft logic analyzer and would depend on it.
No. I don't think this approach works.
On Fri, Mar 6, 2015 at 10:08 AM, Gaebler, John john.gaeb...@nist.gov wrote:
I would keep the duty cycle stuff simple for now. The first thing would be a
program that could analyze an Artiq experiment and print out the duty cycles
of any of the ttl lines (or combinations of the ttl lines).
Ok. Can we assume you consider it a manual operation to extract the
duty cycle of a gpio in an experiment and how you use that number is
all left up to you? Then this sounds just like a use case for the
soft logic analyzer and would depend on it.
Yes, I think that sounds right.
Hi Robert,
thank you, we will send you those estimates shortly.
(Cc'ing list)
One item we forgot is the handling of worker timeouts (e.g. if the
experiments goes into an infinite loop). I would propose a watchdog
context manager to use in the experiment code that terminates the
process with
On Mon, Mar 9, 2015 at 7:37 AM, Sebastien Bourdeauducq s...@m-labs.hk wrote:
thank you, we will send you those estimates shortly.
(Cc'ing list)
One item we forgot is the handling of worker timeouts (e.g. if the
experiments goes into an infinite loop). I would propose a watchdog context
