Dosview
Overview
Dosview is a lightweight, efficient log viewer written in Python3, utilizing the Qt framework for its graphical interface. It is designed to facilitate quick viewing and analysis of UST's radiation detectors log files directly from the command line.
Features
- Command Line Interface: Start viewing logs with a simple command.
- Fast Performance: Optimized for quick loading and smooth scrolling through large log files.
- Cross-Platform Compatibility: Works on any platform that supports Python and Qt.
- Callable from gui: Dosimeter file can be opened from graphical file browser.
Installation
Dosview can be installed using several methods. Below are the instructions for each:
From PyPI Repositories
- Simply run the following command:
sudo pip3 install dosview
From GitHub Repository Using pip
- Ensure you have pip installed on your system.
- Run the following command to install directly from GitHub:
sudo pip3 install git+https://github.com/UniversalScientificTechnologies/dosview.git
From local repository clone using pip
- solve requirements from previous instructions
- Clone your repository
git clone git://github.com:UniversalScientificTechnologies/dosview.git
cd dosview
sudo pip3 install -e .
Desktop menu entry (Linux, optional)
pip install does not register dosview in the desktop application menu,
since that means writing outside the Python environment
(/usr/local/share/...). To add a menu entry and icon after installing:
sudo ./tools/install_desktop_entry.sh
Usage
To use dosview, open your command line interface and execute the following command:
dosview <filename>
Replace <filename> with the path to the log file you wish to view.
Configuration
Dosview does not require additional configuration. It is ready to use immediately after installation.
Metadata
Release files for dosview 0.1.26
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 |
|---|---|---|---|---|
| dosview-0.1.26.tar.gz | 106.1 kB | Without provenance | Details for dosview-0.1.26.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dosview-0.1.26-py3-none-any.whl | Python 3 | none | any | Details for dosview-0.1.26-py3-none-any.whl |
Total release size: 201.2 kB
Release files / dosview-0.1.26.tar.gz
| Download URL | dosview-0.1.26.tar.gz |
|---|---|
| Size | 106.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5764a4050e725bb08a00136b42aae7a9d413b1d2fbd52ef4acb693a28c399fc0
|
|
BLAKE2b-256 checksum How to use checksums |
cfa67e520fcdcd2a74d37fc36f94333867e37cce79953e93137a09243631173e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / dosview-0.1.26-py3-none-any.whl
| Download URL | dosview-0.1.26-py3-none-any.whl |
|---|---|
| Size | 95.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c7fc3e1915d02a473d34544f06548b4f7575ec8df52e99314ee124e81cc275c
|
|
BLAKE2b-256 checksum How to use checksums |
189da2bd452db4e5c209647859f2bf0bb914e00ce89e11414fad3715f8233397
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for dosview 0.1.26
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.