Example
Sample code in AL_Notebook.ipynb notebook
Install
pip install active_learning- OR
python setup.py sdistpython setup.py install
Environment Setup
- Make sure that conda is installed.
- Run the following command in the root directory to build the conda
environment "trews":
conda env create -f environment.yml - Run
source activate trewsbefore executing the Jupyter notebook. - "trews" has a package nb_conda which allows you to specify the conda env you want as a Jupyter kernel. You must have "trews" activated for the Jupyter notebook server to manage conda environments
Objective
- Provide justification for custom sepsis definition generated from soliciting rich feedback from physicians.
- Create an AL implementation that incorporates rich feedback from physicians to improve the TREWS tool.
- Long-term goal: Create a library of active learning tools for any CDSS we design for new clinical problems.
Code Organization
- General functions should be written in .py files under folder 'python_scripts'
- Experiments should load these python files into iPython notebooks
for visualization/output neatness and reproducibility.
- Large experimental datasets should be stored locally and tracked using plaintext files or logs.
- Datasets used for testing implementation should be kept under repository 'dev_data'
Metadata
Release files for active-learning 0.3.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 | Actions |
|---|---|---|---|---|
| active_learning-0.3.0.tar.gz | 14.3 kB | Without provenance | Details for active_learning-0.3.0.tar.gz |
Release files / active_learning-0.3.0.tar.gz
| Download URL | active_learning-0.3.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e626798146b4fc9f9445fbb6dc8cd71245bc89ffdff22011bcf9401b006156f9
|
|
BLAKE2b-256 checksum How to use checksums |
f81fe94889532e3f771b543926f2a6ca9ec9239b2e0ac684ecb0f64136fdaf4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for active-learning 0.3.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.