This page is a collection of known bugs in SweepMe! which may have unforseen or risky consequences. If you find a bug which is not in this list, submit a new ticket, please.
Disclaimer
The following tables list bugs known to the developers which affect the SweepMe! main program or official modules. The lists are maintained in all conscience but may be incomplete. The absence of entries for a specific version does not allow to deduce that the software is free of bugs.
List of Bugs
Bugs in SweepMe!
| Description |
Implication |
Status |
Fixed in Version |
Workaround |
Comment
|
| Hierarchy offset when modules are unchecked |
When an unchecked module is above the following: - Loop with Reduction mode: Data from the wrong dimensions will be reduced, or measurement stops due to error.
- Condition / ControlWidgets / WaferProber using Skip sweeps below feature: The sweeps will not be skipped or only at a lower hierarchy level.
- CustomFunction using tuple arguments for measurement data: Passed data might be truncated if data is not in the same branch as the CustomFunction.
|
Fixed |
1.5.6.20 |
Reorder modules or do not uncheck modules that are above other modules making use of one of the features mentioned in the Implications. |
|
| Saving setting does not continue when one module has an exception |
Setting file is in incomplete and setting cannot be restored |
Fixed |
1.5.5.48 |
So, far this bug has only been observed with using Form module where the an exception is raised after the save check boxes disappeard because of another bug. There is no real workaround. Try to continuosly save a history of your setting file to restore a setting in case you saved it with wrong information. |
Please update to a newer version
|
| Modal dialogs can be hidden behind other dialogs |
Some dialog windows have exclusive input (i.e. no other UI interaction is possible), but they are hidden behind other dialog windows, leading to a state where a user cannot interact with SweepMe! any more. |
Fixed |
1.5.5.47 |
Try to avoid opening multiple setting and option dialogs in parallel. If you already are in the bug scenario, use your keyboard to close the hidden modal dialog (Esc or ↵ Enter). |
-
|
| Widgets are not correctly saved to settings |
After loading settings, widgets are floating or at wrong position |
Open |
- |
Save setting, reload, fix widget and resave setting. |
in progress
|
| Unchecked widgets are not saved to setting if setting is saved during run |
Setting cannot be reloaded correctly. |
Fixed |
1.5.5.34 |
Do not save settings during run |
Please update to a newer version
|
| Removal of a floating widget during a run using the right-top corner cross in beta version <=1.5.5.33 |
Programm crashes |
Fixed |
1.5.5.34 |
Do not close the widget during run |
Please update to a newer version
|
| "Delete version" in version manager deletes entire folder "CustomDevices" for beta version 1.5.5.1 to 1.5.5.8 |
Loss of all custom Device Classes |
Fixed |
1.5.5.9 |
Do not use button "Delete version" |
Please update to a newer version
|
| Only a single 1D data file with Loop = nonstop |
Missing data |
Fixed |
1.5.3.22 |
- |
Please update to a newer version
|
| Seldom, random freezes in version 1.5.3.x |
Program does not react |
Fixed |
1.5.3.21 |
- |
Please update to a newer version
|
| Plots with the same name are overwritten |
Not all images are saved |
Fixed |
1.5.1.14 |
- |
Could be problematic when plots show the same but with different slicing
|
| Using 'stop' functionality does not work |
Measurement aborts |
Fixed |
1.5.3.16 |
- |
Please update to a newer version
|
Bugs in Modules
| Module |
Description |
Implication |
Status |
Fixed in Version |
Workaround |
Comment
|
| Form |
Save check box disappears when fields are moved up or down |
Inconsistent state of the GUI fields |
Fixed |
2023-05-21 |
Don't move fields up and down |
|
| Temperature |
Temperature module does not work |
Measurement stops immediately |
Fixed |
1.5.3.16 |
- |
Update to a newer version
|
Known Issues
| Issue |
Description |
Recommendation |
Comment
|
| Windows Update forces a restart and interrupts measurement
|
Especially in Windows 10, Windows has a strict update policy and forces restarts of your computer, even if applications like SweepMe! are still running. This can interrupt a measurement and in the worst case damage your equipment.
|
In Windows 10, you can define Active Hours, during which Windows will not install updates and restart. For long-running or over-night measurements, set the Active Hours accordingly. As an administrator, you can set a group policy that Windows will not resart as long as a user is logged in.
|
|
| After changing the name of a DeviceClass, the setting has to be renewed
|
The setting does not work anymore. 'Find ports' does not load any ports.
|
Please change the DeviceClass to the new one and save your setting.
|
We will introduce a DeviceClass ID to the setting in a future version to overcome this issue.
|
| Nesting of modules limited to 30
|
A single branch cannot have more than 30 modules in the sequencer (This limit does not affect modules that are in different branches). SweepMe! relies on numpy arrays to store and process measurement data, and numpy has a limitation to 30 dimensions.
|
Consider to rearrange the modules depending on your measurement setup, or combine the functionality of multiple modules into a single CustomFunction, if possible.
|
In the next major SweepMe! version we can upgrade to the latest numpy that extends the limit by a factor of 2.
|