sb0 changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs :: Due to spam bots, only registered users can talk. See: https://freenode.net/kb/answer/registration
_whitelogger has joined #m-labs
<GitHub-m-labs> [artiq] sbourdeauducq commented on pull request #1185 b5a5be4: Better still raise an exception here to help catch program bugs. A simple ``raise ValueError`` will do. https://github.com/m-labs/artiq/pull/1185#discussion_r228385429
<GitHub-m-labs> [artiq] sbourdeauducq commented on pull request #1185 b5a5be4: This is already pretty clear from the name of the function, ``add_mutually_exclusive_group``. https://github.com/m-labs/artiq/pull/1185#discussion_r228385671
<GitHub-m-labs> [migen] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/migen/commit/657c0c72e63597162837809dfe3635d69a98cfd9
<GitHub-m-labs> migen/master 657c0c7 Staf Verhaegen: class TSTriple: width is the width of the base signal
<bb-m-labs> build #324 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/324
sb0 has quit [Quit: Leaving]
rohitksingh_work has joined #m-labs
attie has quit [Remote host closed the connection]
attie has joined #m-labs
rohitksingh_wor1 has joined #m-labs
rohitksingh_work has quit [Ping timeout: 268 seconds]
[X-Scale] has joined #m-labs
X-Scale has quit [*.net *.split]
[X-Scale] is now known as X-Scale
rohitksingh_wor1 has quit [Ping timeout: 252 seconds]
rohitksingh_work has joined #m-labs
m4ssi has joined #m-labs
rohitksingh has quit [Ping timeout: 252 seconds]
rohitksingh has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
rohitksingh has quit [Ping timeout: 260 seconds]
<GitHub-m-labs> [artiq] jordens created urukul-sync (+7 new commits): https://github.com/m-labs/artiq/compare/e1a7e6713a3a^...3985953e8d51
<GitHub-m-labs> artiq/urukul-sync e1a7e67 Robert Jördens: device_db_ptb: fix zotino clr
<GitHub-m-labs> artiq/urukul-sync dffbe3f Robert Jördens: TTLClockGen: expose acc_width
<GitHub-m-labs> artiq/urukul-sync f81c3c9 Robert Jördens: urukul: add sync_in generator...
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
rohitksingh has joined #m-labs
<GitHub-m-labs> [artiq] bradbqc commented on issue #1144: Ah, I see. Well, thank you for trying! https://github.com/m-labs/artiq/issues/1144#issuecomment-433436397
sb0 has joined #m-labs
m4ssi has quit [Ping timeout: 246 seconds]
<GitHub-m-labs> [artiq] jordens commented on issue #1144: To use Sayma with 1 GHz data rate, the parameters of SAWG, the JESD core as well as the clocking setup and DAC configuration code need to be adjusted. This is likely achievable as most of the parts are designed for and were individually already tested at 1 GHz. But it's not straight-forward. Based on input and requirements from the funding groups and users, with the rob
m4ssi has joined #m-labs
<GitHub-m-labs> [artiq] bradbqc commented on issue #1144: Seems reasonable. Thanks for the explanation. https://github.com/m-labs/artiq/issues/1144#issuecomment-433451608
<GitHub-m-labs> [artiq] bradbqc commented on issue #1144: Do either of you have any tips on how I can really get familiar with Sayma (both the hardware and firmware/gateware)? So far I've just been reading code, looking at schematics, and browsing datasheets, but that feels somewhat inefficient so if there's any documentation or anything that I've overlooked I'd love to know. https://github.com/m-labs/artiq/issues/1144#iss
<GitHub-m-labs> [artiq] jordens pushed 3 new commits to urukul-sync: https://github.com/m-labs/artiq/compare/3985953e8d51...2f29b07217ad
<GitHub-m-labs> artiq/urukul-sync c1f625f Robert Jördens: ad9910: disable sync_clk output
<GitHub-m-labs> artiq/urukul-sync 7d79f3b Robert Jördens: ad9910: add docs for sync tuning, refactor
<GitHub-m-labs> artiq/urukul-sync 2f29b07 Robert Jördens: ad9910: add io_update alignment measurement...
<GitHub-m-labs> [artiq] jordens commented on issue #1144: Depends on what you want to do. Tell us about yourself.... https://github.com/m-labs/artiq/issues/1144#issuecomment-433459185
m4ssi has quit [Remote host closed the connection]
<GitHub-m-labs> [artiq] klickverbot commented on pull request #1115 131c576: Done. https://github.com/m-labs/artiq/pull/1115#discussion_r228599098
<GitHub-m-labs> [artiq] klickverbot commented on issue #1115: Thanks. Looking good.... https://github.com/m-labs/artiq/pull/1115#issuecomment-407481101
<GitHub-m-labs> [artiq] klickverbot commented on issue #1115: Any further bikeshed color suggestions? As suggested, I've removed the default arguments as well, which will break people's code, but perhaps it is cleaner indeed.... https://github.com/m-labs/artiq/pull/1115#issuecomment-433476893
rohitksingh has quit [Quit: Leaving.]
<GitHub-m-labs> [artiq] bradbqc commented on issue #1144: Right now I don't have a specific goal in mind. Until I saw this "issue" I had essentially given up on increasing the sample rate (apparently those minor peaks I mentioned in our email chain aren't as big a deal as was initially impressed upon me). Mostly I just want to become more familiar with the inner workings of Sayma so that I'll be better equipped to handle issue
<GitHub-m-labs> [artiq] klickverbot commented on issue #1115: (@jordens @sbourdeauducq Apologies for the delay – any comments?) https://github.com/m-labs/artiq/pull/1115#issuecomment-433511967