On 06/05/2014 07:05 AM, Sébastien Bourdeauducq wrote:
> Hi,
>
> On 06/05/2014 11:22 AM, Robert Jordens wrote:
>> I have asked a few more interested people here to subscribe to the
>> mailing list. And I will get them to dig up example experiments or have
>> them try
On 05/28/2014 03:46 AM, Sébastien Bourdeauducq wrote:
> Ok. I already drafted some code that does this:
> https://github.com/m-labs/ARTIQ/blob/c423b4c9a0828277833ac9346a58c4736db975a9/examples/transform.py
> https://github.com/m-labs/ARTIQ/blob/c423b4c9a0828277833ac9346a58c4736db975a9/examples/coll
Hi Sebastien,
On 05/22/2014 04:34 AM, Sébastien Bourdeauducq wrote:
>> I think the idea of simply executing the code to construct the
>> timeline/graph is not bad at all and might just work fine also for
>> parallel blocks. The only thing I don't see it working for is branches
>> (loops and ifs).
On 05/21/2014 10:50 AM, Sébastien Bourdeauducq wrote:
> On 05/21/2014 04:09 AM, Robert Jordens wrote:
>> Good idea! Is that just mock-up, or does time_manager.format_timeline()
>> do something with the AST?
>> I look forward to seeing the other parts of the code.
>
> Th
Hello,
On 06/18/2014 05:34 AM, Sébastien Bourdeauducq wrote:
> The work over the past month consisted mostly in refining the language
> specifications, and starting to build a rough prototype of the system in
> order to get a better overview of areas in need of attention.
Thanks. During the revie
On 06/25/2014 10:23 AM, Sébastien Bourdeauducq wrote:
> On 06/25/2014 04:45 PM, Slichter, Daniel H. wrote:
>> - I am fine with the idea of the SPEC cards, but I am a bit worried
>> about the low pin count FMC used (only 34 LVDS pairs), and I wonder
>> whether the Spartan 6 will have enough oomph fo
Hello,
On 07/01/2014 12:18 PM, Sébastien Bourdeauducq wrote:
> Python often does that, e.g.
> def __init__(self, param1, ..., paramn):
> self.param1 = param1
> ...
> self.paramn = paramn
>
> I can modify the Experiment constructor to accept only keyword
> arguments, and set them
On 07/01/2014 04:08 PM, Sébastien Bourdeauducq wrote:
> On 07/01/2014 09:42 PM, Robert Jordens wrote:
>> It looks like there are the "truly global parameters"
>
> Are you talking about long lists of constants like those in
> IonProperties_inc.dc from your current co
On 07/02/2014 02:58 AM, Sébastien Bourdeauducq wrote:
> On 07/02/2014 12:50 AM, Robert Jordens wrote:
>>> We could simply use the regular Python mechanism for that, and import
>>> another Python module defining them. The current inline transform
>>> already suppor
On 07/02/2014 07:36 AM, Sébastien Bourdeauducq wrote:
>> Certainly. That was just sketching the functionality. How would you do
>> it without threads?
>
> I see two ways:
>
> 1)
> ts = set_timeout(some_time)
> for partial_result in do_computation():
> if timeout_expired(ts):
>
On 07/05/2014 04:43 PM, Sébastien Bourdeauducq wrote:
> How about the following mechanism for parameters:
> * Experiment constructors take an additional "mvs" (Missing Value
> Supplier) parameter.
> * When creating an Experiment, if some parameter values were specified
> but not supplied as keyword
* Start: 2014-07-23 12:55
* Topic: ARTIQ plans, part 2
* Present:
Sebastien Bourdeauducq
John Gaebler
Ryan Bowler
Andrew Wilson
Joe Britton
Robert Jordens
Daniel Slichter
Dave Wineland
Didi Leibfried
Dave Leibrandt
* Chair: DS
* Minutes: RJ
Speed issues
Hello,
On 08/12/2014 01:20 AM, Sébastien Bourdeauducq wrote:
> I'd like to propose a new system to deal with units, quantization by the
> devices, and rounding errors.
>
> The basic idea is to expose the "native" integer units of the devices
> directly to the user. For example, the statement:
> d
Hello,
On 08/12/2014 05:07 AM, Sébastien Bourdeauducq wrote:
> Yes. I was imagining one could use the smallest possible step as native
> unit in those special cases (but are they really special, or are most
> devices like that?). Of course, this requires an additional mechanism
> when exactness is
On 08/13/2014 03:03 PM, Britton, Joe wrote:
> Daniel, Justin, Brian, John G and I chatted over lunch about this. We
> agree that an implementation of the sort described in the attached
> whiteboard screenshot strikes a good balance between protecting users
> from doing something stupid and letting
On 08/15/2014 08:32 AM, Sébastien Bourdeauducq wrote:
> On 08/14/2014 09:16 AM, Robert Jordens wrote:
>> Also that excerpt misses the point of the underlying question, which is
>> when to best convert floating point physical quantities to integer
>> device units.
>
On 08/18/2014 10:20 AM, Sébastien Bourdeauducq wrote:
> I guess the first parallel block can be replaced with
> "delay(1*ms);bd.off();bdd.off()" since bd and bdd are already active by
> default or from the previous cool_detect run - correct?
Correct for the last 99 but not necessarily for the firs
On 08/19/2014 09:53 PM, Sébastien Bourdeauducq wrote:
> Ok. And should we support anything else than 32-bit integers for the
> array elements?
I imagine supporting the smaller datatypes (shorts and chars) might turn
out to be beneficial for the efficiency of the RPC wire protocol and
long longs mi
On 09/03/2014 01:56 AM, Sébastien Bourdeauducq wrote:
> Florent and I got the full DDR3 SODIMM to work on the KC705 board. The
> peak bandwidth is 64Gbps, which I think sets the record of the fastest
> open source SDRAM controller :)
Congratulations! Impressive tour de force.
> Please test on you
On 09/03/2014 01:56 AM, Sébastien Bourdeauducq wrote:
> Please test on yours and report your results - all the code is committed
> in MiSoC, so you should be able to build and flash everything with:
Works fine here. The windows look good with vivado as well as ise.
Temperature and/or vivado-ise di
On 09/05/2014 04:07 AM, Sébastien Bourdeauducq wrote:
>> Temperature and/or vivado-ise differences change it by at most one bit
>> time.
>
> I guess you meant a IODELAY tap?
Yes.
Robert.
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/a
Hello,
On 09/09/2014 08:16 AM, Sébastien Bourdeauducq wrote:
> I'm considering rewriting this as follows:
>
> class PhotonHistogram(AutoContext):
> parameters = "bd bdd pmt repeats nbins"
>
> def report(self, i, n):
> print(i, n)
>
> @kernel
> def cool_detect(self):
>
On 09/09/2014 06:28 PM, Sébastien Bourdeauducq wrote:
> On 09/10/2014 01:15 AM, Robert Jordens wrote:
>> * no parallel context around pmt.count_rising(): i would like to be able
>> to use inputs (counting, tagging) in a parallel context with outputs.
>
> The removal of thi
On 09/19/2014 08:55 AM, Slichter, Daniel H. wrote:
> Sebastien has indicated that we are basically ready for a breakout
> board from the KC705 to the existing DDS/TTL system, so that we can
> start using the KC705 and new software to test and run our
> experiments. I am willing to go ahead and des
On 09/19/2014 11:06 AM, Slichter, Daniel H. wrote:
> I heartily agree on all counts. However, for back compatibility with
> current DDS and TTL breakout boards I thought we should at least have
> the option. We can use commericial SCSI cables to improve the
> reliability over the current homemade
On 09/19/2014 07:20 PM, Sébastien Bourdeauducq wrote:
> On 09/20/2014 06:38 AM, Robert Jordens wrote:
>> A jitter of one parallel UI is unlikely.
>
> For transmission, yes. For reception, the SERDES needs to align the
> received data words with the parallel clock, which c
On 09/22/2014 02:20 PM, Slichter, Daniel H. wrote:
>> The receive parallel clock is reconstructed from the received data
>> and the latency is constant once locked.
>
> Yes, but if this timing relationship is different each time the
> system is rebooted (I have seen on datasheets that for some of
On 09/22/2014 10:52 PM, Sébastien Bourdeauducq wrote:
> We cannot use the data pairs for synchronization, as the latency of the
> transceivers might not be the same in both directions.
Yes we can. Just define that timing is measured wrt what actually
happens at the (one) frontend. Such a definitio
testing there. Meanwhile develop
the future link (and/or distributed rtio architecture) plus new hardware
for the kc705. Nothing down the road requires developing an adapter
board between the kc705 and the current parallel bus.
> On 09/23/2014 05:53 AM, Robert Jordens wrote:
>> This is not
On 10/09/2014 02:41 AM, Yann Sionneau wrote:
> Which Linux distribution should be supported by the ARTIQ manual [0]
> explaining how to install everything?
I don't see many distribution-dependent things on the horizon. Is there
a problem with keeping it distribution independent?
> Could you also
On 10/10/2014 02:34 AM, Yann Sionneau wrote:
> If you take as an example Debian Wheezy (stable) versus Debian Jessie
> (testing), the steps to install migen/misoc/artiq can be quite
> different, mainly due to the fact that Python 3.3 (or superior) is
> not packaged at all in Debian Wheezy, you ther
On 10/13/2014 04:24 AM, Sébastien Bourdeauducq wrote:
> On 08/12/2014 05:32 PM, Robert Jordens wrote:
>> n = core.coerce(1.2345*ns) # [n] = core.cycle
>> for i in range(1000):
>> core.delay(n)
>> f = dds.coerce(345*MHz)
>> t = dds.coerce(core.coerce(1000*n, to
On 10/15/2014 12:35 AM, Sébastien Bourdeauducq wrote:
> I've done some quick testing on the sustained performance that the
> system has when pushing RTIO switch commands with some minimal
> processing between them (increase the time and manage the loop).
> It tured out that a new switch command can
Hello,
On 04/10/2015 11:18 AM, Sébastien Bourdeauducq wrote:
> On 04/10/2015 10:24 PM, Ben Keitch wrote:
>> I would like to ask you about how you do a phase measurement on the
>> sine clock on the DDS? We are looking at some new DDS card designs
>> and think we might need to implement a phase de
This is to be synchronized with the corresponding change in misoc.
---
artiq/gateware/targets/kc705.py | 16
artiq/gateware/targets/pipistrello.py | 10 +-
artiq/runtime/bridge.c| 4 ++--
artiq/runtime/clock.c | 4 ++--
artiq/runtime
This is to be synchronized with the corresponding change in misoc.
---
artiq/gateware/targets/kc705.py | 16
artiq/gateware/targets/pipistrello.py | 10 +-
artiq/runtime/bridge.c| 4 ++--
artiq/runtime/clock.c | 4 ++--
artiq/runtime
---
artiq/gateware/targets/kc705.py | 6 +++---
artiq/gateware/targets/pipistrello.py | 2 +-
artiq/runtime/bridge.c| 4 ++--
artiq/runtime/dds.c | 28 ++--
artiq/runtime/dds.h | 8
artiq/runtime/test_mo
37 matches
Mail list logo
