sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
<GitHub> [artiq] sbourdeauducq closed issue #694: ImportError: cannot import name 'Keep' when installing artiq 2.2 from source https://github.com/m-labs/artiq/issues/694
<GitHub> [artiq] sbourdeauducq commented on issue #695: No, because this creates additional maintainance at every major release, and will be forgotten. But we can add a note telling developers that they should be careful which branch they are on. https://github.com/m-labs/artiq/issues/695#issuecomment-289947817
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to release-2: https://github.com/m-labs/artiq/commit/483a897db4cdb9a28962a803af465d8e05ff69d7
<GitHub> artiq/release-2 483a897 Chris Ballance: monkey_patches: fix 3af29f7
<sb0> bb-m-labs, force build --branch=release-2 artiq
<bb-m-labs> build forced [ETA 36m26s]
<bb-m-labs> I'll give a shout when the build finishes
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/2e2d0be201cd3ca8a82b3d2f938181bc0c7e867e
<GitHub> artiq/master 2e2d0be Sebastien Bourdeauducq: skip crashing DMA tests on buildbot
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/6d1046cae25afb1512d64f54e1547671b77e0506
<GitHub> artiq/master 6d1046c Sebastien Bourdeauducq: conda: use python 3.5.3
<18VAAVYHC> [artiq] sbourdeauducq closed issue #670: Conda package for Artiq 2.2 broken on Windows: PyQt5 DLL load failed https://github.com/m-labs/artiq/issues/670
<GitHub> [artiq] sbourdeauducq commented on issue #670: OK, thanks https://github.com/m-labs/artiq/issues/670#issuecomment-289957337
<bb-m-labs> build #484 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/484
ohama has quit [Ping timeout: 264 seconds]
ohama has joined #m-labs
<bb-m-labs> build #446 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/446
<bb-m-labs> build #1420 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1420
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/0cda1a3d3415a2ca7109c9a2ffb5ce6844ca4ad9
<GitHub> artiq/master 0cda1a3 Sébastien Bourdeauducq: manual: add note about git branches...
<bb-m-labs> build #485 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/485
<bb-m-labs> build #447 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/447 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1421 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1421
<bb-m-labs> build #486 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/486
<bb-m-labs> build #448 of artiq-win64-test is complete: Warnings [warnings python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/448 blamelist: S?bastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #1422 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1422
sb0 has quit [Quit: Leaving]
sb0 has joined #m-labs
rohitksingh_work has joined #m-labs
<GitHub> [artiq] whitequark closed issue #690: fix "session aborted: " message https://github.com/m-labs/artiq/issues/690
<GitHub> [artiq] sbourdeauducq commented on commit 948ed6f: You forgot to update 6caab4d10b13d1aa578801c986f7b33bf5b8a725. https://github.com/m-labs/artiq/commit/948ed6fb0a8dc5e513c55fb87bbbf82a2f8dc4e5#commitcomment-21532947
<GitHub> [artiq] whitequark commented on commit 6caab4d: Should we really not have a proper interface for these errors? Or highlight them in the UI separately? https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21532951
<GitHub> [artiq] sbourdeauducq commented on commit 6caab4d: What would a "proper interface" look like? https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21532959
<GitHub> [artiq] whitequark commented on commit 6caab4d: Like the "clean kernel termination" thing we have. https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21532960
<GitHub> [artiq] sbourdeauducq commented on commit 6caab4d: Nope, see #691 https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21532965
<GitHub> [artiq] sbourdeauducq commented on commit 6caab4d: "Sending those messages through the session interface while a kernel executes is not a good idea because asynchronous RTIO errors can appear after the kernel has terminated" https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21532969
<GitHub> [artiq] whitequark commented on commit 6caab4d: Um, I meant sending it when the *next* kernel is *starting*. https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21532996
<GitHub> [artiq] sbourdeauducq commented on commit 6caab4d: Then it gets silently ignored if there is no next kernel. Worse than streaming logs IMO. https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21533001
<GitHub> [artiq] whitequark commented on commit 6caab4d: Okay. Then polling a flag, instead of polling logs. https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21533011
<GitHub> [artiq] sbourdeauducq commented on commit 6caab4d: See the other argument about DRTIO in #691. https://github.com/m-labs/artiq/commit/6caab4d10b13d1aa578801c986f7b33bf5b8a725#commitcomment-21533014
<bb-m-labs> build #487 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/487
<bb-m-labs> build #1423 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1423 blamelist: whitequark <whitequark@whitequark.org>
zumbi has quit [Ping timeout: 240 seconds]
zumbi has joined #m-labs
<GitHub> [artiq] jordens commented on issue #693: Thanks https://github.com/m-labs/artiq/pull/693#issuecomment-290003028
Gurty has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 240 seconds]
rohitksingh_work has joined #m-labs
rohitksingh_wor1 has quit [Ping timeout: 268 seconds]
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 268 seconds]
rohitksingh_wor1 has quit [Ping timeout: 268 seconds]
<GitHub> [artiq] cjbe opened pull request #696: language: fix PYONValue list defaults (fixes #682) (master...pyon-list-default) https://github.com/m-labs/artiq/pull/696
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/756e8a415effabf243f846a36964f17ffc9a8f23
<GitHub> artiq/master 756e8a4 Chris Ballance: language: fix PYONValue list defaults (fixes #682)
<GitHub> [artiq] sbourdeauducq commented on issue #696: Yes. Thanks. https://github.com/m-labs/artiq/pull/696#issuecomment-290098628
<GitHub> [artiq] sbourdeauducq pushed 1 new commit to release-2: https://github.com/m-labs/artiq/commit/e8c5cb55cbce5a85bf051ccf68c24c111bf03f38
<GitHub> artiq/release-2 e8c5cb5 Chris Ballance: language: fix PYONValue list defaults (fixes #682)
<bb-m-labs> build #488 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/488
<bb-m-labs> build #1424 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1424 blamelist: Chris Ballance <chris.ballance@physics.ox.ac.uk>
<sb0> hmm... should I buy a low-bias current sense amplifier IC, or mess around with capacitors in parallel with the current sense resistor and low duty cycle operation of the amplifier?
<rjo> what do you want do do? measure small currents?
<sb0> measure the emission current of a bayard-alpert gauge through the cathode
<sb0> the bias/leakage of the current sense amplifier would substract from the actual current
<sb0> I could avoid this problem by measuring the anode current instead, but then I need a current sense amplifier that can take much higher common-mode voltage
<rjo> that's mA usually.
<sb0> it's down to 100's of uA, in low vacuum
<rjo> you can download the SRS RGA schematics to get an idea how to do that.
<sb0> and eg a TSC1031 can leak 15uA
<rjo> take a FET amp if bias current is your problem.
<sb0> well, might be good enough, the gauge isn't very precise to begin with
<rjo> and drive a virtual ground with a transimpedance amp.
<rjo> assuming your collector is a reasonable voltage (0V usually).
<sb0> yes, I'm putting the collector at 0V to reduce leakage via the cable/feedthrough
<sb0> then the cathode is at ~ +30V
<sb0> what virtual ground?
<sb0> for having negative voltages?
<rjo> or "virtual 30V"
<sb0> well, I want to keep the ground at 0V, since this might go to earth/cable shields/vacuum chamber
<sb0> and the collector at 0V to reduce leakage
<sb0> negative voltages are quite easy to do with a charge pump, just needs a small IC and 2 capacitors
<rjo> sure. with corresponding ripple.
<rjo> what's your 30V supply. if it is isolated just place it above the TIA.
<rjo> or even check the SRS gauge controllers' schematics. the circuits are not terribly complicated.
<sb0> I have a +250V supply connected to the anode, an isolated ~2V supply on the filament (cathode), and the cathode is connected to ground via a (controlled) "resistor" that develops the +30V
<sb0> the plan is to 1) control the resistor so the cathode stays at +30V 2) control the filament heating so the emission current stays at some fixed value
<sb0> whitequark, so, SRS are using a diode with 0.8V drop for filament power! no fancy synchronous rectification stuff...
<sb0> ah, right, they use a TIA instead of a current sense amp for measuring emission current
<whitequark> SRS?
<whitequark> ah I see
<GitHub> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/245e18634758e9643e26e6ff3110344cd8a9d3b0
<GitHub> artiq/master 245e186 whitequark: Commit missing parts of 948ed6fb.
<GitHub> [artiq] whitequark closed issue #669: Dashboard prevents connection to coredevice https://github.com/m-labs/artiq/issues/669
<GitHub> [artiq] whitequark commented on issue #669: I believe that both smoltcp bugs were fixed, and we *also* stopped using UDP for moninj, so this is not reproducible anymore. https://github.com/m-labs/artiq/issues/669#issuecomment-290186494
<bb-m-labs> build #489 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/489
<bb-m-labs> build #1425 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1425 blamelist: whitequark <whitequark@whitequark.org>
hedgeberg has quit [Ping timeout: 240 seconds]
hedgeberg has joined #m-labs
Gurty has quit [Ping timeout: 240 seconds]
Gurty has joined #m-labs
<whitequark> bb-m-labs: force build artiq
<bb-m-labs> build forced [ETA 35m39s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #490 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/490
<bb-m-labs> build #1426 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1426
<whitequark> wtf
<whitequark> why did that suddenly start failing
<whitequark> it's probably something screwy about the lab. network, because there's no commit this can be clearly attributed to *shrug*
ohama has quit [Remote host closed the connection]
<GitHub> [artiq] StanleyEDavidsdavid30 opened issue #697: Using SPI Protocol with Pipistrello https://github.com/m-labs/artiq/issues/697
ohama has joined #m-labs