On 01/28/2015 09:56 PM, Yann Sionneau wrote:
+from artiq.frontend.loglevel import verbosity_args, init_logger
Looks good to me, but I'd rather put those two small functions in
artiq.tools instead of creating another file.
Sébastien
___
ARTIQ mailing
I advocate adding options to setup.py to include these dependencies if a user
want's them.
I think it would make sense to fork external dependencies into m-labs/artiq so
that dependencies don't break over time.
I second the motion.
___
ARTIQ
On Wed, Jan 28, 2015 at 6:56 AM, Yann Sionneau y...@m-labs.hk wrote:
Was that the idea you had in mind?
I've put the loglevel.py containing the factorized code in artiq.frontend but
I guess it must go somewhere else, except that I'm not sure what location
would be the best.
If this is OK
Le 28/01/15 14:54, Sébastien Bourdeauducq a écrit :
On 01/28/2015 09:56 PM, Yann Sionneau wrote:
+from artiq.frontend.loglevel import verbosity_args, init_logger
Looks good to me, but I'd rather put those two small functions in
artiq.tools instead of creating another file.
Here is the fixed
On 01/29/2015 04:25 AM, Slichter, Daniel H. wrote:
I think it would make sense to fork external dependencies into
m-labs/artiq so that dependencies don't break over time.
I second the motion.
What about pointing out to known good version numbers of dependencies in
the ARTIQ documentation?
Adding an LTC6957 introduces minimal additional complexity or cost, so I vote
to do that. Helps with the jitter problem.
but I'm worried
about a possible part-to-part skew inside the DDS chips between SYNCLK and
the output, which is why the possibility of sampling the latter can help with
I advocate adding options to setup.py to include these dependencies if a
user want's them.
I think it would make sense to fork external dependencies into m-labs/artiq
so that dependencies don't break over time.
-Joe
On Wed, Jan 28, 2015 at 8:39 AM, Yann Sionneau y...@m-labs.hk wrote:
Hello,
