microsoft / microsoft/Qcodes

Converting old --> new datasets: incomplete data transfer

Open
#1,129 0 comments 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

### Steps to reproduce
1. Find a dataset with multiple measurements (see example file)
2. from qcodes.dataset.legacy_import import import_dat_file
3. data_621 = import_dat_file('mainfolder/data/621')

### Expected behaviour
Importing all of the data from, in this case, 621 to the SQL file.

### Actual behaviour
It imports all of the set points, and the first data array of measured data. It creates columns for the other measurements, but fills them in with NULL values instead of with the data.

### System
**Mac**

**QCoDeS/Qcodes**

![621_example](https://user-images.githubusercontent.com/38584660/41103925-98bab8ee-6a6a-11e8-8d1d-896ad32c1092.png)

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 at qcodes.dataset.legacy_import and the import_dat_file entry point, then reproduce the issue with the example dataset at mainfolder/data/621. Trace how the set points and measured-data arrays are written to the SQL file; done means every measured-data column contains its imported values rather than NULL.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.