CosApp Lab - Toolbox for managing and deploying CoSApp powered dashboards.
Introduction
The primary goal of CoSApp Lab is to help users transform existing CoSApp modules into interactive dashboards, with almost no additional development or configuration.
Examples
Using CosApp Lab in JupyterLab
CoSApp Lab provides a JupyterLab extension named SysExplorer for creating interactive dashboards. This extension allows users to dynamically customize the layout and fill their dashboard with multiple predefined widgets, such as charts, controllers (sliders, etc.), 3D visualization panels...
Using CosApp Lab standalone mode
Dashboards defined with SysExplorer in JupyterLab can also be exported into libraries and served by CoSApp Lab as web applications.
Documentation
A more detailed CoSApp Lab documentation is available at:
https://cosapp-lab.readthedocs.io/
Installation
Stable release
The easiest way to obtain cosapp_lab is to install the conda package:
conda install -c conda-forge cosapp_lab
cosapp_lab is also available on PyPI. However, since pythonocc-core is not, users can install cosapp_lab with pip, but the 3D viewer widget will not work.
pip install cosapp-lab
JupyterLab is not a direct dependency of cosapp_lab, but users need to have JupyterLab (>3.0) in order to create CoSApp dashboard in notebooks.
Development
Setup development environment
# create a new conda environment
conda create -n cosapplab -c conda-forge python jupyterlab nodejs=20
conda activate cosapplab
# download cosapp_lab from gitlab
git clone --recursive https://gitlab.com/cosapp/cosapp_lab.git
# install JS dependencies, build and install JupyterLab extension in development mode
cd cosapp_lab
npm run install
npm run build:all
npm run install:extension
# install cosapp_lab in editable mode
python -m pip install -e .
Testing
# Test python code
python -m pytest
# Test typescript code
npm run test
Build documents
cd docs
sphinx-build -b html -d _build/doctrees . _build
Metadata
Release files for cosapp-lab 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 | |
|---|---|---|---|---|
| cosapp_lab-1.0.0.tar.gz | 23.1 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cosapp_lab-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.2 MB
Release files / cosapp_lab-1.0.0.tar.gz
| Download URL | cosapp_lab-1.0.0.tar.gz |
|---|---|
| Size | 23.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd6dca790f8d38cd7abdd6492af84863994c5be5793ea206c711a2088b9f232b
|
|
BLAKE2b-256 checksum How to use checksums |
1e511de75ce626a37b9472b7082365a61e650ec41c7a5f1347ec00fa5871b9b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Release files / cosapp_lab-1.0.0-py3-none-any.whl
| Download URL | cosapp_lab-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3ff38a61b0e9c5e21bd380eba686a26cbada66772f9ed6ecb934f0c54838504
|
|
BLAKE2b-256 checksum How to use checksums |
7d62594ca518769ab72c9a4b1585ab68bd9864236c1badd198c019d26f8fc008
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Security for cosapp-lab 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.