Bug: setting value jumps when type is int32
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
No source file or test is identified in the issue. First reproduce the voltage-setting behavior with np.int32, np.int64, np.float32, and np.float64 values, then trace the instrument voltage parameter's ramp or sweep handling. Done means integer NumPy values ramp without the false "jumping" error and retain the same behavior as float values.
Written by the indexing model from the issue text.
Description
I initialize a voltage.step value but, when I try to set a voltage value on my SMU I get the error 'cannot sweep voltage from numberx to numbery - jumping' when the number I am setting is of type np.int32, when I change the setting value type to np.float64 I no longer get this error and my ramp works fine.
- the return of this parameter from the instrument is float.
- instrument.voltage(np.int64(numbery)) & instrument.voltage(np.float32(numbery)) give the same behavior (no ramp) .
- after changing to float or np.float64 from one of the types that don't work, the next immediate set gives the same error but, any subsequent set works fine (until the type is changed back to one of the ones that dont work, then it immediatley gives the error without even working for one more set).
- Dominant language
- Python
- Stars
- 459
- Forks
- 361
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 83
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/Qcodes
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/Qcodes#8168 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
microsoft/Qcodes#1087 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
All instruments share a single logging.Logger, so per-instrument log configuration leaks between instrumentsPossibly taken @ymampaey claimed this 15 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Export to xarray dataset fails when two data variables do not share same setpointsMay be free again @jenshnielsen claimed this 104 days ago, and no pull request is open. Open
microsoft/Qcodes#8232 · 1 reaction · 2 assignees ·
Maintainers usually reply within 1 day
All issues in microsoft/Qcodes
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Negation with "not" and "no" is ignored during sentiment analysisPossibly taken @vivek-3728 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
techcsispit/mess-mood#11 · 1 comment ·
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ramnes/notion-sdk-py#408 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
btclib-org/btclib-wallet#267 ·
Maintainers usually reply within 1 day
-
good first issue tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
knnmelprop/YAADO#111 ·