IPM RAS PSK and FS spectrometer files viewer
Required packages:
Optional packages:
pycatsearch: for in-place matching spectral lines;
numexpr: for accelerating certain numerical operations;
bottleneck: for accelerating certain types of nan evaluations;
openpyxl: for saving MS Excel files.
They should install at the first application start automatically.
Required Python: 
The package is developed under the newest Python to date. Older versions of Python should be compatible as long as
ruff makes no mistakes.
In case of a difficulty in the development, the support might shrink, but not further than what
proclaims.
Notes:
- to run on MS Windows 7, you can install Python from adang1345/PythonWin7;
PySide2requires Python < 3.11; there is a port ofPySide2byon Python 3.11, 3.12, and 3.13, but it's unclear whether it's stable;
PyQt6andPySide6require pretty modern OS, e.g., 64-bit MS Windows 10 21H2 or later;pyqtgraph<0.13.3is incompatible withQt6>=6.5.0;PySide6==6.9.1doesn't draw anything, it's a known bug.
Getting Python
Python might have already been installed on your system. If your system supports repositories, check them first. Otherwise, download an appropriate Python distribution (or the source code) from https://www.python.org/downloads/ and install it.
It will be convenient to add the Python directory to the PATH environment variable to get quick access to the binaries.
Getting the application
The source code is available at https://github.com/StSav012/psk_viewer.
Use pip or another Python package manager
You can get the code with pip (the preferred way):
- (optionally) create a virtual environment and activate it,
- issue
pip install psk_viewer
in the command line.
Then, do
pip install -U psk_viewer
every time you wish to update the code.
Use git
You can get the code with git:
- navigate to the directory you wish to store the code in,
- issue
git clone https://github.com/StSav012/psk_viewer.git
in the command line, - find
psk_viewerdirectory with the code; feel free to move or rename however you want.
Then, do
git pull https://github.com/StSav012/psk_viewer.git
every time you wish to update the code.
Use the official GitHub software
This way is pretty much like the previous.
If you prefer CLI applications, issue
gh repo clone StSav012/psk_viewer
in the preferred directory.
Get a packed archive
- download the source code archive from https://github.com/StSav012/psk_viewer/archive/master.zip,
- unpack its content into a directory to your taste.
The source code will get updated every time the application starts unless you manually delete updater.py file.
Launching the application
After the installation via pip or another package manager,
an executable named psk_viewer should be available in the environment. That's all.
Otherwise, there's more to do.
A file called main.py should be fed to Python executable.
If the file associations set so, the opening of the file should lead to executing the code. Ugly and unsafe.
If the Python directory is in PATH environment variable, issue something like
python main.py
Otherwise, use the full path to python (or python3) executable.
Feel free to create an entry to the quick launch or to the desktop to avoid excessive typing. The text does not cover this topic anyhow.
Usage tips
Parts of the application interface can be moved, re-arranged, and resized.
The least evident part of the interface is the toolbar. Its buttons allow you to do the following:
- open a data file, either from the FS or the PSK spectrometer, see the selector below the file name;
- clear everything opened and marked;
- replace the displayed data with their finite-step second derivative (if appropriate);
- switch the displayed data between the detector voltage and the absorption values (if appropriate);
- export the displayed data into a numerical table or as a picture;
- mark interesting data points, copy the values, save them, or remove the marks;
- customize colors, lines thickness, and some text formatting.
Read the tooltips, they may appear useful.
Metadata
Release files for psk-viewer 0.11.1
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 | |
|---|---|---|---|---|
| psk_viewer-0.11.1.tar.gz | 94.7 kB | With provenance | Details |
Release files / psk_viewer-0.11.1.tar.gz
| Download URL | psk_viewer-0.11.1.tar.gz |
|---|---|
| Size | 94.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
323ebda74d51743581b670dc11b614c683d10c9b5294c6004642b6a5a3ebacd0
|
|
BLAKE2b-256 checksum How to use checksums |
277d179b90ce6cc970ba1c155d2b276163cc75d81d8c5c411b86feb065e1ba88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logSecurity for psk-viewer 0.11.1
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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for psk_viewer-0.11.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logA 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.