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

Use sleep instead of post_delay in doNd #3576

Merged
merged 13 commits into from
Nov 16, 2021
Merged

Conversation

FarBo
Copy link
Contributor

@FarBo FarBo commented Nov 12, 2021

This PR is created to change the delay time between setpoints in doNd functions. This is done because the current post_delay logic can unintentionally prolong the delay time if a ramped parameter is used, which the ramp time is shorter than the delay time provided in the doNd functions.

  • do1d
  • do2d
  • dond
  • test files if needed

The PR is addressing this issue:
#3564

@codecov
Copy link

codecov bot commented Nov 12, 2021

Codecov Report

Merging #3576 (5d16d02) into master (2991bab) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #3576   +/-   ##
=======================================
  Coverage   65.69%   65.69%           
=======================================
  Files         225      225           
  Lines       30465    30465           
=======================================
  Hits        20014    20014           
  Misses      10451    10451           

@FarBo
Copy link
Contributor Author

FarBo commented Nov 15, 2021

@jenshnielsen
As we are replacing post_delay with time.sleep, shouldn't we sleep after setting the setpoint to the value, rather than sleeping after the datasaver?
I think users put delay because they want desired values on instruments to be stabilized before entering to the datasaver part, which our post_delay attribute intended to handle this.

@jenshnielsen
Copy link
Collaborator

@FarBo Yes the sleep should be between set of setpoints and getting the parameter

@FarBo FarBo marked this pull request as ready for review November 15, 2021 18:08
@jenshnielsen
Copy link
Collaborator

@FarBo I think this is close to being ready. Could you add a changelog entry?

@jenshnielsen
Copy link
Collaborator

bors r+

@bors bors bot merged commit a906435 into microsoft:master Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants