DeadSea Optics: Spectrosopy software using the legacy Ocean Optics USB2000(+) spectrometer
The Ocean Optics spectroscopy devices are excellent to determine the spectrum of a light source. For older devices, however, the original software does not run on modern operating systems. New software can be expensive, and for many use cases the advanced features of the software are not needed.
Using information from old documents we built applications for working with the Ocean Optics USB2000 and USB2000+ devices. The software consists of a command-line interface, dso, and a graphical user interface, DeadSea Optics.
Screenshots
Installation
The latest version is always available on the Releases page (link is also in the right sidebar). Please scroll down to Assets and download the .msi-installer for Windows and the .dmg-installer for macOS. The application will also run on Linux, but no installer packages are provided at this moment. For Linux, follow the instructions below to install the command-line interface and optionally start the GUI using the provided gui command.
Driver installation on Windows
DeadSea Optics needs a driver to access the Ocean Optics USB device on Windows. The generic WinUSB device is sufficient, but it is unfortunately necessary to manually select that driver using administrator privileges.
- Connect the Device: Plug your USB device into your computer.
- Open Device Manager: Press Win + X and select Device Manager.
- Locate your Ocean Optics USB device. It might be listed under "Other devices" with a yellow warning icon.
- Right-click on the device and select Update driver.
- Choose Browse my computer for driver software.
- Select Let me pick from a list of available drivers on my computer.
- Scroll down and select Universal Serial Bus devices.
- From the list, choose WinUSB Device in both the left column (Manufacturer) and right column (Model) and click Next.
Your device should now be available to applications like DeadSea Optics.
Command-line interface
If you want to use the command-line interface, you can install using pip, pipx or, recommended, uv:
pipx install deadsea-optics
uv tool install deadsea-optics
This provides the identical deadsea-optics and dso commands.
You can also run the application directly using uvx or uv tool run:
uvx deadsea-optics
and even start the GUI directly, without installing, using
uvx deadsea-optics gui
Usage
The GUI interface is pretty self-explanatory. You can perform a Single measurement, a Continuous measurement, or Integrate over multiple measurements to increase the signal-to-noise ratio. The integration time is the time the sensor is actively recording a spectrum for a single measurement. A longer integration time effectively reduces the noise, but can result in overexposure of the sensor. This will be indicated in the status bar at the bottom of the screen. If you can't increase the integration time because of overexposure, you can integrate over # integrations number of measurements which will further increase the signal-to-noise ratio. Finally, the data can be plotted as a line or scatter plot and the data can be saved to a CSV file.
From the command line, the GUI application can be started with
dso gui
The command-line interface is perfect to do a quick measurement and write the data to a CSV file, or to perform multiple measurements with the exact same parameters. To check that a compatible device is available, run
dso check
For a single standard measurement, run
dso spectrum
Quite a few options are available. For an overview, run
dso spectrum --help
For example, to perform a measurement with an integration time of 0.5 seconds and write the data to a file without showing a graph or table, type
dso spectrum -t 500_000 -q -o data.csv
where the underscores in the number are entirely optional. To integrate over multiple spectra, run
dso integrate
which has many of the same options, and one extra to provide the number of measurements.
Helpdesk
We don't have a formal helpdesk, but please drop a line to d.b.r.a.fokkema@vu.nl if you need assistance or have questions.
Metadata
Release files for deadsea-optics 1.0.0
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 | |
|---|---|---|---|---|
| deadsea_optics-1.0.0.tar.gz | 736.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deadsea_optics-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / deadsea_optics-1.0.0.tar.gz
| Download URL | deadsea_optics-1.0.0.tar.gz |
|---|---|
| Size | 736.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aae8a3808899df895fa55ecc29a13f0c912957bf8fadffb858bc6121937cbb81
|
|
BLAKE2b-256 checksum How to use checksums |
bd42b9b47faff957fb816b599ba38aeac361ddad595048cff7705f1b8db96d2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.25
|
Release files / deadsea_optics-1.0.0-py3-none-any.whl
| Download URL | deadsea_optics-1.0.0-py3-none-any.whl |
|---|---|
| Size | 291.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
696a7884dd6d342d3d9f04467035078ed5f2b0d60f673e6feaa73996365d187b
|
|
BLAKE2b-256 checksum How to use checksums |
b0b03f573c5b3c4eebfa379262dd66916f4cbaf36bda8674d74a637791ffa4f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.25
|
Security for deadsea-optics 1.0.0
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.