microsoft / microsoft/Qcodes

Station overwrite removes references to instruments but leaves instruments functioning

Open
#1,883 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

If one overwrites the station the snapshot gets reset - that is, it doesnt have any references to instruments previously imported. However, all instruments are still functioning in qcodes so measurements can be performed although all snapshots are completely empty.

I would expect the snapshot to always contain all instruments currently loaded in python.

Error arises if one accidentally reruns the initialization:
First init looks fine and snapshot has the instrument.
![image](https://user-images.githubusercontent.com/23334244/71663493-bb88db80-2d55-11ea-94d5-b72bd23f37ce.png)
Rerun init without kernel reset throws an error on instrument import. However, station has already been overwritten. From user point everything looks fine and measurements can continue but all snapshots are empty which is discovered when it is needed in post analysis.
![image](https://user-images.githubusercontent.com/23334244/71663584-17ebfb00-2d56-11ea-8986-d1a0f1462bae.png)

@jenshnielsen @Dominik-Vogel

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 reproducing the station overwrite after rerunning initialization without a kernel reset, then inspect how station snapshots and instrument imports are handled. Confirm the existing instruments remain represented in the snapshot after overwrite, and verify that measurements and post-analysis see the same instrument data.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.