Hi,
It seems to me that in all cases the experiments can be pre-computed and then
loaded onto the fpga in the normal way. As with the example that Joe gave
before, you just have to add an else statement (or another if that captures the
other possibilities) at the end of the experiment for
At present Quantum II does not do duty cycle management on its AOMs because
its less cumbersome (given the existing .dc language) to transform
AOM-induced beam pointing into amplitude noise using a fiber (and then noise
eat downstream). This approach wastes laser power and is a patch on the
.
From: jord...@gmail.com jord...@gmail.com on behalf of Robert Jördens
robert.jord...@nist.gov
Sent: Wednesday, March 11, 2015 4:36 PM
To: Gaebler, John
Cc: Britton, Joe; Sébastien Bourdeauducq; artiq@lists.m-labs.hk
Subject: Re: ARTIQ future details
On Fri, Mar 6, 2015
Hi,
We are able to flash the Papillio Pro from a Linux virtual machine with Migen,
ARTIQ already installed ect. using
1. wget http://m-labs.hk/artiq/binaries/binary_package.tar.gz
2. tar xzf binary_package.tar.gz
3. cd binary_package ./flash.sh -a (notice the .sh)
Is there a way to do this
Hi,
Could you explain how to run the example files for the GUI? I'm using the
virtual machine from Joe Britton made on 1/20/2015 and I am able to run the
flopping_f_simulation.py and flopping_f_siumulation.gui.py files. How do I
create/run an instance of the experiment or the GUI?
Thanks,
It is possible to use at() to start each iteration at a specific time.
Would that solve the duty cycle problem?
I'm not sure what you have in mind there exactly. It wouldn't be optimal to
slow down the main scan by a bunch to account for the possibility that saveion
might run. I guess it
Quick question, are we planning to support the old (Ryan's) PDQ firmware or
just the new one. Would there be much difficulty in supporting both?
I have started implementing the PDQ2 driver and made some changes to the
transport example. Please have a look. I have some points I'd like to
