Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keithley 2600: 4 probe current sweep support #3023

Merged
merged 7 commits into from
May 21, 2021

Conversation

RasmusBC59
Copy link
Contributor

This PR adds a new mode to the doFastSweep function of the of Keithley 26xx

The new mode allows for 4 probe measurements

@jenshnielsen

@codecov
Copy link

codecov bot commented May 18, 2021

Codecov Report

Merging #3023 (7c9a0f5) into master (f77f3ab) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #3023      +/-   ##
==========================================
- Coverage   65.55%   65.52%   -0.03%     
==========================================
  Files         213      213              
  Lines       28441    28454      +13     
==========================================
  Hits        18644    18644              
- Misses       9797     9810      +13     

Copy link
Contributor

@astafan8 astafan8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i know this is a bit out of scope of the PR, but can the "fastsweep" parameter be explicitly mentioned in the notebook? :) please? :) otherwise the reader thinks that doFastSweep is the only way to run the measuyrement (resulting in a legacy qcodes dataset!), while it is not, because "fastsweep" is an array parameter and can be used with the Measurement class as usual.

self.setpoint_names = ('Current',)
self.setpoint_units = ('A',)
self.label = 'voltage'
self._short_name = 'vi_sweep_four'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for clarity/expressiveness?

Suggested change
self._short_name = 'vi_sweep_four'
self._short_name = 'vi_sweep_four_probe'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree :-)

@@ -62,6 +62,13 @@ def prepareSweep(self, start: float, stop: float, steps: int,
self.label = 'voltage'
self._short_name = 'vi_sweep'

if mode == 'VIfour':
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.. or is this too verbose?

Suggested change
if mode == 'VIfour':
if mode == 'VIfourprobe':

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree :-)

@@ -62,6 +62,13 @@ def prepareSweep(self, start: float, stop: float, steps: int,
self.label = 'voltage'
self._short_name = 'vi_sweep'

if mode == 'VIfour':
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be also added to the docstring, not only here but also in other methods in this file ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree :-)

@jenshnielsen jenshnielsen added this to the 0.26.0 milestone May 19, 2021
@jenshnielsen
Copy link
Collaborator

Agree with @astafan8 that we should not promote the Measurement but use the "new" dataset in the examples if possible. Otherwise this looks good

@RasmusBC59
Copy link
Contributor Author

@astafan8 I have updated the notebook to use fastsweep in combination with a d0d. We could also make a new function(do_faste_sweep) in the driver wrapping the d0d. So performing the fastsweep stays a one-liner?

@astafan8
Copy link
Contributor

I have updated the notebook to use fastsweep in combination with a d0d

perfect!!! thank you!

We could also make a new function(do_faste_sweep) in the driver wrapping the d0d. So performing the fastsweep stays a one-liner?

no, that would be mixing concerns for negligible benefit -- do*d is already a one-liner-ish :) and the fact that doFastSweep exists as a method is just historical and shouldn't have been added in the first place.

@astafan8 astafan8 changed the title Keithley 2600 4probe Keithley 2600: 4 probe current sweep support May 19, 2021
@jenshnielsen jenshnielsen merged commit b38e37a into microsoft:master May 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants