SimCATS v2.0.0

SimCATS now introduces support for simulating sensor scans, along with several additions and improvements to sensor modeling and configuration.

Please have a look at the documentation on ReadTheDocs

Changes:

• SimCATS now supports the simulation of sensor scans. To enable this, the SensorScanSensorInterface was introduced as an extension of the standard SensorInterface. Sensor implementations based on this interface can be used to:

  • simulate measurements of only the sensor using the new measure_sensor_scan function of the Simulation class
  • simulate measurements of other quantum dots using the measure function of the Simulation class

• A generic implementation of the SensorScanSensorInterface, called SensorScanSensorGeneric, has been added. It is based on a simplified model of the sensor dot in which the barriers and the dot are represented as three resistors in series. The sensor signal is defined as the conductance across this series:

  • Barrier conductances are modeled using generalized logistic functions (GLFs).
  • The dot conductance is modeled using Lorentzians, along with a GLF describing the final rise where the barriers cease to exist and the device becomes fully conductive.

  This model was implemented as part of the master’s thesis of Benjamin Papajewski. See the notebook example_SimCATS_SensorSimulation.ipynb for a detailed explanation of the sensor model and usage examples.

• Added the support function reset_offset_mu_sens to simulate retuning the sensor to a fixed working point before measuring a new CSD.

  • Warning: This function modifies the provided Simulation object.

• Added a new default configuration featuring the sensor, available in default_configs as "GaAs_v2_extended_sensor".

• Added a parameter sampler for generating variations of the existing GaAs configuration. The sampler, sample_random_variations_v3_config, can be imported from simcats.config_samplers. An example is provided in example_SimCATS_SensorSimulation.ipynb.

Breaking changes:

• Renamed several internal sensor modules. These changes should typically not affect imports, as the modules are internal and users generally import functions and classes from the sensor module rather than from specific file paths (which are not exposed in the documentation).
  Affected modules:
  • _generic_sensor.py -> _sensor_generic.py
  • _gaussian_sensor_peak.py -> _sensor_peak_gaussian.py
  • _lorentzian_sensor_peak.py -> _sensor_peak_lorentzian.py