Search results

The purpose of the LoadFiles modules is to define a number of files. The module then performs a variation over a The file path can then be forwarded to other modules or widgets to perform a certain process for each file.

...Here, users can place modules via drag and drop. The arrangement of these modules determines their activation timing, repetitions, and variations. ...modules. Some have a Sweep mode and value for transferring values between modules. This feature enables, for example, synchronizing the voltage increase of t

[[Category:Modules]] [[Category:Add-On Modules]]

...es and more information can be found [https://sweep-me.net/services/add-on-modules here] * Licenses can be activated using the menu "Tools" -> "Modules & Devices" -> menu "Licenses".

...y nesting modules into each other, creating branches and nested for-loops. Modules of the same type can even be added multiple times. Almost any procedure can == Modules ==

* [[Modules]] {{FlexBoxItemColorBox|title=Modules|dark=#b8e|light=#f7f0ff|

[[Category:Modules]] [[Category:Add-On Modules]]

We develop SweepMe! on demand. We add features and modules that complement the program. Device Classes are added at any time, we have

[[Category:Modules]] [[Category:Add-On Modules]]

[[Category:Modules]] [[Category:Add-On Modules]]

[[Category:Modules]] [[Category:Add-On Modules]]

...nd manage modules and devices. It can be found in the menu via 'Tools' -> 'Modules & Devices'. ...r.PNG|frameless|right|Version manager of SweepMe! to download and manage [[Modules]] and [[Devices]]]]

...ere are basic modules such as [[Loop]] or [[Hold]], and [[Devices | device modules]] that communicate with external hardware. ...ional [[Modules]] or [[Devices]] via the 'Tools' menu -> [[Version manager|Modules&Devices]].

[[Category:Modules]] [[Category:Basic Modules]]

[[Category:Modules]] [[Category:Add-On Modules]]

...ots. It can load drivers which can bringe their own parameters, similar to modules like [[Logger]] or [[Switch]]. [[Category:Modules]]

All variations of modules that are below the Condition module in the sequencer are skipped and the pr [[Category:Modules]]

...sily placed using the drag-and-drop feature from a list of all available [[Modules]]. The Sequencer organizes measurements in a hierarchical tree structure of modules. Each module can be thought of as a for-loop over its sweep values, represe

Several Modules can load Instrument drivers (formerly "Device classes") which are small cod You can download or update Drivers via the Version Manager (menu "Tools" -> "Modules & Devics") which is part of the SweepMe! main installation.

...ion for a couple of time, to allow users that purchased a bundle of add-on modules to be able to use it. As there is no plan to release a 1.6 version, we did == Modules & Devices ==

# If there are multiple MakeFile modules in one branch, the lowest active one (it also means checked in the Sequence * the SweepValues of all Modules above MakeFile in the sequencer

[[Category:Modules]] [[Category:Add-On Modules]]

To program own modules, you need a license key. Modules can deeply interact with the entire program so that specific knonwledge is ...ieces. They have to be designed in a way to be able to work with all other modules. It is not recommended to put a final end user application into a module, e

SweepMe!'s WaferProber modules uses an absolute addressing scheme. Instead of using communication function * The modules hands over the current sweep value to the driver during the semantic functi

[[Category:Modules]] [[Category:Add-On Modules]]

[[Category:Modules]] [[Category:Device Modules]]

...y read values from other instruments. To stop the looping, one can use the add-on module [[Condition]] to for example to stop the process when the setpoint h [[Category:Modules]]

* Load values from a file to hand them over to various Modules as [[Sweep value]] ...h line of your file, the ReadValues module will perform a variation of the modules in the sequencer that are hierarchically below.

...s can stem from modules that are present in the same branch, but also from modules in previously active branches. ...the [[configure()]] phase of Calc and thus even before configure of child modules.

...="row"| Use, but no redistribution (for [[List of Included Python Packages|modules already included in SweepMe!]])

...he Sweep mode is similar to the Sweep mode that can be found in many other modules. For a capacitance-voltage (CV) curve one would use "Voltage" as Sweep mode [[Category:Modules]]

...SweepMe!. These Python functions can be used to receive data from multiple modules to analyze data or calculate new parameters. * Access to measured data from all other modules.

[[Category:Modules]] [[Category:Device Modules]]

[[Category:Modules]] [[Category:Device Modules]]

...les['email']. It only works if 'email' is already registered as key in sys.modules so that the property '__path__' can be modified. if not libpath in sys.modules['email'].__path__:

Therefore the following modules are typically needed in one branch: # A module that applies the output value of the PID modules, e.g. an [[SMU]] module with a driver for power supply

[[Category:Modules]] [[Category:Device Modules]]

The <Type of the Module> must be related to the [[Modules]] provided by SweepMe! and every Module provides different functionality to ...architecture specific. These can be third-party libraries or custom python modules that are separated from the <code>main.py</code> for a clearer structure.

...[[Sequencer]] is given, with a short explanation. One can configure the [[Modules]] by double-clicking on them in the [[Sequencer]] window. In this article, ...upper SMU a drain variation of the lower SMU is done. If you swap the SMU modules regarding gate and drain variation, one can measure transfer characteristic

# we only wait once, e.g. if the driver is used in multiple modules with the same device

In order to get the available ports listed in the GUI of the corresponding [[Modules|Module]], choose desired port types by: