@sbourdeauducq I'm not sure what you are imagining, but the only money I have access to is £3k year in travel/research funds, and in terms of skills, merely my own.
As I said, if you want to…
What do you think about creating a separate label for legacy compiler bugs (instead of, or in addition to, closing them)? We have several hundred kLOC of code here in Oxford alone that depends on…
@marmeladapk: Where can I find this branch – this would be very useful to have (useful enough that I was trying to convince students here to implement it)?
(@sbourdeauducq: In case you are…
@jordens Great, thanks – I dimly remember running into some weird behaviour with I2C muxes (?) in the past, but probably that's all solid on Kasli v2. (having online monitoring in a background…
Yes, I am by no means complaining about macOS specifically – it just supports my broader point that messing with the default OS rendering "without reason" (on the default path of a somewhat niche…
def return_many(): return ([4], [True],)
Your problem, at least this example, does not seem to be related to RPC or type annotations at all:
from artiq.experiment import EnvExperiment, kernel, rpc, host_only
from artiq.language.t…
This could definitely be improved in the documentation. However, this
Maybe this warrants a warning in the Urukul driver documentation that the output updates might be unstable in DMA.
does…
It might be worth looking at a Wireshark capture to see if there is anything strange happening/to get another layer of timestamps to correlate. I wonder whether this is related to the network…
Is the gateware bitstream/firmware build even different at all? I guess with gateware there is always the chance of two non-deterministic optimisation runs resulting in subtly different outcomes…
Commit 25346780bf looks like a false positive; a change to the compiler shouldn't have any effect on the Rust runtime.
Ah, I only saw now that I could have undone be088626063f83238517ee1422ba8427d477e1e2 instead of manually recreating the style. Oh well.
Yes, but I can prepare for the next experiment while writing the results for the previous one.
This should already be the case. The next-to-be-run experiment is already prepared while the…
This makes me wonder, why this is not done in the first place. I can only imagine a case where a result of a previous experiment influences how a consecutive experiment is executed.
That's…
These are likely just broadcast packets that are part of the regular background chatter on the network. The easiest way to monitor them (apart from modifying smoltcp to print them out) would be to…
Hmm, could this point to a hardware issue (e.g. power supply stability)? Or maybe the crash is related to the RTIO analyzer, if you have that enabled? (which would cause changes to the network…
If your experiment doesn't actually require any hardware readback, you might be interested in a branch I have that adds an emulation layer…
Just to be sure I understand correctly (since that wasn't clear to me from the initial post), for the "non-RPC" case you assign rtios to say self.rtios statically (on the host before the…