Running the code on a server by default

I don't speak computer completely fluently but yesterday we had a bar discussion about how to run a single experiment with several computers, for example one for each ATS card one has. I agree, this sounds cumbersome but if the software was written by default to run as a server and the user interactions (function calls, scripts etc.) would be send to it, then one could run an experiment on two computers where one just passes function calls on to the other. This wouldn't necessarily be noticed by the user with a single computer, but opens up some nice possibilities. For our multi qubit experiments this might be a nice solution sometimes. Also, one could measure remotely without using TeamViewer. Data could be both sent back and stored on the measurement computer. In many cases, the fridges have a second computer that could run qcodes. Ultimately a remote computer running qcodes would not be so different from any other piece of hardware in our setups.

The issue names no files, tests, or entry points. Start by tracing how Qcodes currently runs experiments and communicates with hardware, then clarify the server/client boundary, supported remote interactions, and data flow. Done would require an agreed design and implementation scope for running experiments across computers.