geomet-screen
Tools for screen deck layouts, wear monitoring and partition models.
Features
- SQLAlchemy Database Integration: SQLite-based database connection for managing screen deck layouts
- Excel Data Loading: Load screen deck layouts from Excel workbooks (one sheet per deck)
- Data Models: SQLAlchemy ORM models for screen decks and grid cells
- Plotly Visualization: Create interactive heatmap visualizations of deck grids
- Kaleido Integration: Export plots to static images (PNG, JPEG, SVG)
- Sphinx Documentation: Comprehensive documentation with Sphinx Book Theme
- Sphinx Gallery: Executable examples with automatic thumbnail generation
- Comprehensive Tests: Full test coverage using pytest
Installation
pip install geomet-screen
For development:
git clone https://github.com/elphick-consulting/geomet-screen.git
cd geomet-screen
pip install -e ".[dev,docs]"
Quick Start
Load a Screen Deck from Excel
from geomet.screen import DatabaseConnection, ExcelLoader
# Initialize database
db = DatabaseConnection("screen_data.db")
db.create_tables()
# Load deck from Excel
loader = ExcelLoader(db.get_session())
deck = loader.load_deck_from_excel(
workbook_path="screen.xlsx",
sheet_name="Deck1",
screen_name="Screen_A",
deck_name="Deck_1",
)
Visualize the Deck
from geomet.screen import plot_deck_grid
# Get deck data
grid_df = loader.get_deck_data(deck.id)
# Create plot
fig = plot_deck_grid(grid_df, title="Screen Deck Layout")
fig.show()
Running Tests
pytest tests/
Building Documentation
cd docs
make html
The documentation will be built in docs/build/html/.
Project Structure
geomet-screen/
├── geomet_screen/ # Main package
│ ├── database/ # Database connection and Excel loader
│ ├── models/ # SQLAlchemy models
│ └── visualization.py # Plotly visualization functions
├── tests/ # Test suite
├── examples/ # Sphinx Gallery examples
├── docs/ # Sphinx documentation
│ ├── source/ # Documentation source files
│ └── build/ # Generated documentation
└── pyproject.toml # Project configuration
Technologies Used
- uv: Modern Python package manager
- SQLAlchemy: SQL toolkit and ORM
- pandas: Data manipulation and analysis
- openpyxl: Excel file reading/writing
- plotly: Interactive plotting library
- kaleido: Static image export for plotly
- Sphinx: Documentation generator
- sphinx-book-theme: Beautiful book-style theme
- sphinx-gallery: Gallery of examples with thumbnails
- pytest: Testing framework
License
See LICENSE file for details.
Metadata
Release files for geomet-screen 0.1.2
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 |
|---|---|---|---|---|
| geomet_screen-0.1.2.tar.gz | 119.2 kB | With provenance | Details for geomet_screen-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| geomet_screen-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for geomet_screen-0.1.2-py3-none-any.whl |
Total release size: 141.1 kB
Release files / geomet_screen-0.1.2.tar.gz
| Download URL | geomet_screen-0.1.2.tar.gz |
|---|---|
| Size | 119.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a356b6e05916f5cd8c41ecdb0d9afc2afe32d8993a91b7df9b3185b46ba658b7
|
|
BLAKE2b-256 checksum How to use checksums |
254658815578a11bcdb1877062cbf70f87a451882890ded76777a24ee464c260
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 22, 2026.
Transparency logRelease files / geomet_screen-0.1.2-py3-none-any.whl
| Download URL | geomet_screen-0.1.2-py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a64b9c8c77805ce7e770a3f19b99935c7d7def5110fdf2ba7b5ea81252338247
|
|
BLAKE2b-256 checksum How to use checksums |
5dff9cec5d64bd19f323bbd3b9fcb0538df4fb7b8facbbd0b3374ea1dabdcf66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 22, 2026.
Transparency logSecurity for geomet-screen 0.1.2
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 2 files in this release have been uploaded with provenance metadata.
Attestation for geomet_screen-0.1.2.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 Jan 22, 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.