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
<sb0> better separation of the items
<sb0> try e.g. multiscan
swivel has joined #m-labs
<swivel> hello
<sb0> hi swivel
<swivel> I was just watching a few of the Milkymist-related talks on youtube, and was wondering if there were any plans to produce a second generation of the physical device?
<GitHub41> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/voaZL
<GitHub41> artiq/master b3b0e19 Sebastien Bourdeauducq: dashboard: compute initial experiment window size from font metrics
<sb0> swivel, no, but there are/were plans to make the numato opsis compatible with it
<sb0> mithro, ^
<bb-m-labs> build #476 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/476
<swivel> sb0: I see, thanks for the info, I'll go look into the opsis. Mind if I idle here? I suspect the conversations will be interesting.
<bb-m-labs> build #220 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/220
<bb-m-labs> build #746 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/746
<sb0> sure
<GitHub143> [artiq] sbourdeauducq pushed 2 new commits to master: https://git.io/voanB
<GitHub143> artiq/master 6500d3f Sebastien Bourdeauducq: conda: use setuptools entry_points...
<GitHub143> artiq/master b769403 Sebastien Bourdeauducq: dashboard: larger experiment initial window size
<sb0> whitequark, now_save isn't called if the kernel terminates with an exception, is it?
<bb-m-labs> build #477 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/477
<sb0> is the kernel also going to update the global "now" symbol on exception? what if it was modified in registers?
<sb0> and shadowing the global variable in now_init() and now_save() is messy. different names should be used or those functions should just deal with the global.
<bb-m-labs> build #221 of artiq-win64-test is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/221 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<bb-m-labs> build #747 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/747 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<sb0> why of course
<sb0> pfff
<sb0> net result of setuptools entry points: they now check for irrelevant dependencies (OutputCheck, lit) before running; gui_scripts has zero effect on windows and it still opens consoles
<sb0> I cannot remember *any* setuptools feature that worked correctly
<GitHub24> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/voand
<GitHub24> artiq/master b97ad69 Sebastien Bourdeauducq: conda: install lit and OutputCheck
<bb-m-labs> build #748 of artiq is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/748 blamelist: Sebastien Bourdeauducq <sb@m-labs.hk>
<GitHub35> [artiq] sbourdeauducq pushed 1 new commit to master: https://git.io/voanx
<GitHub35> artiq/master 4e241f1 Sebastien Bourdeauducq: conda: try lowercase package name
<cr1901_modern> Last time I used setuptools, I couldn't verify it worked properly before installing it b/c --dry-run was broken :/
<cr1901_modern> Last time I used setuptools to deploy something I wrote*
<sb0> setuptools on the other hand is incapable of checking for relevant dependencies, such as qt
<sb0> it seems the only thing that works (somehow), is a package made only of GUI programs or only of CLI scripts
<sb0> you cannot mix
Marcelos has quit [Ping timeout: 250 seconds]
<sb0> reading those issues I'm glad we're not supporting OS X
<sb0> "What you will see is that the menu doesn't appear straight away (you have to switch application then back to get it to work). Now try running the program again with pythonw - it works!"
<bb-m-labs> build #478 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/478
<bb-m-labs> build #222 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/222
<bb-m-labs> build #749 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/749
sandeepkr__ has quit [Ping timeout: 244 seconds]
sandeepkr has joined #m-labs
<cr1901_modern> Do Xilinx tools even exist for OS X?
<sb0> artiq doesn't depend on xilinx tools for most things
<cr1901_modern> Well I suppose you could use just firmware blobs; I'm just so used to compiling it.
<cr1901_modern> gateware* blobs
<sb0> that gets flashed into the board and then the rest of the software doesn't know about it
<cr1901_modern> Well, my question is moot anyway. Perhaps to deal with your Qt woes, extend setuptools to check whether ld can link qt? :/
<sb0> pyqt doesn't work like that
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #m-labs
<whitequark> sb0: now_save() is not called when an unhandled exception propagates to the top of stack.
<whitequark> there is no global "now" symbol
<whitequark> well
<whitequark> forget that, that's not what I meant
<whitequark> re: global now symbol
<sb0> is the "now" symbol written in all cases except for "local" computations with registers?
<sb0> e.g. when you make a syscall, is now up-to-date?
<whitequark> let me check.
<whitequark> sb0: delay_mu and delay do an RMW cycle with nothing to cause an exception in between
<whitequark> however, if the code manipulates the timeline with now+at calls, then of course that may raise
ssk1328 has joined #m-labs
ssk1328 has left #m-labs [#m-labs]
<sb0> okay so the global is generally up-to-date?
<sb0> it becomes a bit redundant with the timestamp parameter of e.g. rtio_out ..
rohitksingh has joined #m-labs
rohitksingh1 has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
<whitequark> yeah, it's up-to-date
rohitksingh1 has quit [Quit: Leaving.]
EvilSpirit has joined #m-labs
EvilSpirit has quit [Ping timeout: 240 seconds]
sb0 has quit [Ping timeout: 240 seconds]
rohitksingh has joined #m-labs
sb0 has joined #m-labs
<whitequark> sb0: fyi the dashboard is leaking memory, about 1MB RSS per 50 experiment runs
<whitequark> with nothing there, just the schedule being updated
<whitequark> and nothing in the log
<whitequark> also seems to murder my ADSL, but that's probably not anywhere near relevant
<sb0> whitequark, what's your quamash version? once in a blue moon, pyqt-related bugs get fixed, and that was one of them
<whitequark> soemthing from debian, so probably old
<sb0> whitequark, are you using the board right now?
<sb0> seems so.
<whitequark> yes
<whitequark> I am trying to reproduce that bug
<whitequark> currently at 36000th iteration, with no modifications so it ought not be fixed yte
rohitksingh has quit [Quit: Leaving.]
<sb0> you can use core.comm.close() instead of creating new workers
<whitequark> hm
<sb0> whitequark, what is struct msg_rpc_batch?
<sb0> it's not used anywhere, can I remove it?
<whitequark> if it's not used anywhere, go ahead
<whitequark> I don't remember what it is
<whitequark> btw, your self.core.comm.close() doesn't change much
<sb0> ah? i'd have thought worker startup would cause most of the delay
<whitequark> not significantly, maybe 2x
<whitequark> ah, just 4000 runs this time
<whitequark> okay, let's try it again...
mumptai has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh1 has joined #m-labs
rohitksingh has quit [Ping timeout: 260 seconds]
rohitksingh1 has quit [Ping timeout: 252 seconds]
rohitksingh has joined #m-labs
sb0 has quit [Quit: Leaving]
rohitksingh has quit [Ping timeout: 276 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 276 seconds]
awallin has joined #m-labs
kmehall_ has joined #m-labs
kristian1aul has joined #m-labs
kristianpaul has quit [*.net *.split]
bentley` has quit [*.net *.split]
bb-m-labs has quit [*.net *.split]
kaaliakahn has quit [*.net *.split]
awallin__ has quit [*.net *.split]
kmehall has quit [*.net *.split]
kaaliakahn has joined #m-labs
bb-m-labs has joined #m-labs
FelixVi has quit [Remote host closed the connection]
bentley` has joined #m-labs
<whitequark> sb0: just kill the artiq_run process if it's still running and prevents you from doing something
<GitHub117> [artiq] whitequark pushed 1 new commit to master: https://git.io/voVk7
<GitHub117> artiq/master 8e2c664 whitequark: runtime: remove confusing variable shadowing.
<bb-m-labs> build #479 of artiq-kc705-nist_clock is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-kc705-nist_clock/builds/479
FelixVi has joined #m-labs
<bb-m-labs> build #223 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/223
<bb-m-labs> build #750 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/750
mumptai has quit [Quit: Verlassend]
FelixVi has quit [Remote host closed the connection]