microsoft / microsoft/Qcodes

unified commands for Instrument drivers

Open
#77 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion
Dominant language
Python
Stars
459
Forks
359
Avg merge
3d 6h
Merged PRs (30d)
73

Description

While we integrate more and more drivers into qcodes we will have to make sure they can be used in a uniform fashion from the user perspective.
We might already run into this in @eendebakpt comment in #74
I guess all DMMs have basically the same main functions, but different special functions, the same goes for SourceMeters, magnets and others.
If we have single users working on a new driver we somehow cant force them to go through potentially tens of other drivers to figure out the optimum syntax.

How can we unify this?

Also in line with this, most instruments have a model name, a manufacturer, version, software version, i even think the visa *IDN? command is unified, at least it looks the same for the instruments I looked for.
In my drivers I did:

        vendor, model, serial, software = map(str.strip, self.IDN.split(','))

and put that data in a dict, however, I think this should be unified as well and be saved in the snapshot.
How should we go about it?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing instrument drivers and the discussion in issue #74 to compare common DMM, SourceMeter, and magnet functions. Examine how IDN data such as vendor, model, serial, and software version is currently represented. Done requires an agreed uniform driver interface and a defined way to store instrument identity in snapshots.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.