Add full type checking of Qdac drivers

[jenshnielsen]

Should be merged after #2336 and not backported. This probably should be tested manually on both devices

[codecov]

Codecov Report

Merging #2341 (36aeac6) into master (6eae703) will increase coverage by 0.00%.
The diff coverage is 67.92%.

@@           Coverage Diff           @@
##           master    #2341   +/-   ##
=======================================
  Coverage   62.32%   62.32%           
=======================================
  Files         200      200           
  Lines       26267    26276    +9     
=======================================
+ Hits        16370    16377    +7     
- Misses       9897     9899    +2     

[astafan8]

I approve as long as the change has been tested on the insturment (including the verbose mode :) )

[FarBo]

I will test it with the instrument and approve it

[FarBo]

@jenshnielsen

I tested this PR for Qdevil. It seems that it is working without any issue (tested instrument version is 1.07). For testing _assigned_triggers, the only requirement is to ramp_voltage for more than 1 channel, otherwise triggers is 1 and _assigned_triggers will not be populated. Then, setting slope to 'Inf' for each channel results in popping that channel out of the _assigned_triggers.

@astafan8
What should be done for verbose mode? The comments in the driver is not that informative to what to do. Especially in the QDac docstring, it says "The driver assumes that the instrument is ALWAYS in verbose mode OFF
and sets this as part of the initialization, so please do not change this"

[jenshnielsen]

@FarBo thanks for testing

[jenshnielsen]

Perhaps @astafan8 meant update_currents=True ?

[FarBo]

update_currents=True queries the instrument for all channels and return responses, which can be seen as DEBUG messages in the load time.

[FarBo]

Both Qdac and Qdevil tested with the instruments. I approve this PR, unless @astafan8 explicitly explains what he wants to be tested in verbose mode.

[astafan8]

unless @astafan8 explicitly explains what he wants to be tested in verbose mode.

The verbose mode allows one to test this change (the square brackets got turned into curly brackets):

https://github.com/QCoDeS/Qcodes/blob/36aeac67a27dd9630577705b531988e080c0cad7/qcodes/instrument_drivers/QDevil/QDevil_QDAC.py#L573-L575

Especially in the QDac docstring, it says "The driver assumes that the instrument is ALWAYS in verbose mode OFF
and sets this as part of the initialization, so please do not change this"

well, what can i say.... then no need to test the functionality that is not even supposed to be used by anyone apparently... :)