Welcome to OrensteinLabKit’s documentation!
OrensteinLabKit Python Module
OrensteinLabKit is a python module including all the functions which will be useful to the experiments in Orenstein’s lab. The outline of OrensteinLab is listed below.
- Instrument
- OptiCool
OptiCool_Control
- Lakeshore
Lakeshore336
- Operation
ESP301
- Attocube
- v2
Attocube_v2
- v4
Attocube_v4
- Measurement
- Yue
Measurement
Installation
OrensteinLabKit can be easily installed by pip install.
pip install OrensteinLabKit
Before using OrensteinLabKit, please remember to update the “configuration.txt” file in the module. The device ID of the lockin and the port ID of the ESP301 controller are required.
Instrument
This section includes the home-written control programs of several instruments. These instruments don’t have any developed python module/package to control, so I have to write the control programs by myself.
Instrument.OptiCool.OptiCool_Control
Control all the necessary operations of the OptiCool.
connect_opticool()
No input. Return the telnet object connecting to the socket server of the OptiCool.
read_temperature(telnetObj)
Input the telnet object returned by connect_opticool(). Return an array [temperature, status]. The status means the temperature approaching status, which can be “Standby”, “Tracking”, “Chasing”, “Near” and “Stable”.
set_temperature(telnetObj, set_point, rate, mode)
Input 4 arguments, telnet object, temperature set point, ramp rate, mode. The highest ramp rate is 10 K/min. The mode has two options.
0: Fast settle
1: No overshoot
Return “command received”.
read_field(telnetObj)
Input the telnet object. Return an array [field, status]. The status means the field approaching status, which can be “Ramping (Driven)” and “Holding (Driven)”.
set_field(telnetObj, set_point, rate, approach_mode, 1)
Input 5 arguments, telnet object, field set point, ramp rate, approach mode, field mode. The highest ramp rate is 110 Oe/s. The approach mode has three options.
0: Linear
1: No overshoot
2: Oscillate
The field mode has only one option in the OptiCool, but has two options in the PPMS and MPMS3. In this way, just use the value 1 for the field mode, which means “Driven”.
Return “command received”.
disconnect_opticool(telnetObj)
Close the telnet object returned by connect_opticool().
Instrument.Lakeshore.Lakeshore336
Control all the necessary operations of the Lakeshore 336 temperature controller.
initialization_lakeshore336()
Return the instrument object (inst).
read_temperature(inst)
Input the instrument object obtained from initialization_lakeshore336(). Return the temperature.
read_setpoint(inst)
Input the instrument object. Return the temperature setpoint.
set_setpoint(inst, output, set_temperature)
Input 3 arguments, instrument object, output port number (1, 2, 3, 4) and temperature setpoint.
read_ramp(inst)
Input the instrument object. Return an array [on_off, ramp rate].
set_ramp(inst, output, on_off, ramp_rate)
Input 4 arguments, instrument object, output port number (1, 2, 3, 4), on_off (0, 1) and ramp rate.
close_lakeshore336(inst)
Input the instrument object. Close the connection with the lakeshore 336.
Operation
This section includes some basic single-step operations frequently used in lab. The related instruments have developed python module/package to support, so the purpose of this section is just to make some basic operations easier to realize.
Operation.ESP301
Simple operations related to the ESP301 controller.
SingleStageMove(axis_index, pos, go_back)
Corotate(axis_index_1, pos_1, go_back_1, axis_index_2, pos_2, go_back_2)
Read_Position(axis_index)
Balance_PID_single(incident_polarization_angle, P, tolerance, balance_axis_index, channel_index, time_constant)
P can be extracted from Find_balance_angle in the Measurement section.
Operation.Attocube.v2.Attocube_v2
Simple operations related to the attocube controller. Note: attocube axis index: ‘x’, ‘y’ and ‘z’.
Read_Position(axis_index)
SingleStageMove(axis_index, real_target, tolerance, go_back)
DoubleStageMove(axis_index_1, real_target_1, tolerance_1, go_back_1, axis_index_2, real_target_2, tolerance_2, go_back_2)
Measurement
This section will include all the measurements in lab. However, different experiments may have different measurements to take, so I would like to create a subsection for everyone, so that group members can create their own measurement control programs. My measurement programs can work as examples. Please feel free to refer to them.
Measurement.Yue.Measurement
Lockin_time_record(channel_index, recording_time, time_constant, filename_head)
This function simply records the data from lock-in amplifier in real time.
Find_balance_angle(incident_polarization_angle, axis_index, start_pos, step_size, num_of_steps, go_back, channel_index, time_constant, filename_head)
This function automatically finds the balance angle in MOKE measurement.
Corotate_measurement(num_of_steps, axis_index_1, start_pos_1, step_size_1, go_back_1, axis_index_2, start_pos_2, step_size_2, go_back_2, channel_index, time_constant, filename_head)
This function takes a single birefringence measurement.
Pump_probe(axis_index, start_pos, step_size, num_of_steps, go_back, channel_index, time_constant, filename_head)
This function takes a single pump-probe measurement.
Mapping(filename_head)
This functions takes a MOKE mapping.
Pol_scan_Mapping(filename_head)
This functions takes a birefringence mapping.
Balance_PID_single(incident_polarization_angle, P, tolerance, balance_axis_index, channel_index, time_constant)
This PID-based function automatically finds the balance angle in MOKE measurement. P can be extracted from Find_balance_angle.
Field_scan(set_points, ramp_rate, balance_axis_index, channel_index, time_constant, balance_channel_index, filename_head)
This function take measurements in an applied field. Set points need to be an array.
Field_scan_PID(set_points, ramp_rate, balance_axis_index, channel_index, time_constant, P, balance_channel_index, balance_time_constant, filename_head)
This function take measurements in an applied field. The artifact from Faraday rotation of the window is automatically compensated via PID. Set points need to be an array. P can be extracted from Find_balance_angle.
Metadata
Release files for OrensteinLabKit 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| OrensteinLabKit-0.0.6.tar.gz | 25.2 kB | Without provenance | Details for OrensteinLabKit-0.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| OrensteinLabKit-0.0.6-py3-none-any.whl | Python 3 | none | any | Details for OrensteinLabKit-0.0.6-py3-none-any.whl |
Total release size: 53.5 kB
Release files / OrensteinLabKit-0.0.6.tar.gz
| Download URL | OrensteinLabKit-0.0.6.tar.gz |
|---|---|
| Size | 25.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85fe21f742fa08270241b34673dea8a4e821295d1d817d02e6b43b46588499d9
|
|
BLAKE2b-256 checksum How to use checksums |
b2fa361747d1fe628e285410d85df8c95e3ec3739d3bad250cc658a7dc234047
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.10
|
Release files / OrensteinLabKit-0.0.6-py3-none-any.whl
| Download URL | OrensteinLabKit-0.0.6-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77d256d7984caa942b64a0f9e412929a18fb05fc06e80beb9a339a17245842f5
|
|
BLAKE2b-256 checksum How to use checksums |
459d13d379f6a630a4cdcb602cdae9a03e1293b5a2e310f7323d57932091a47b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.10
|
Security for OrensteinLabKit 0.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.