Fastsom
A PyTorch and Fastai based implementation of Self-Organizing Maps.
You can find documentation and examples here.
Contents
Getting started
Install as a dependency
To install Fastsom, you can use pip to install the PyPi package:
pip install fastsom
or you can install directly from Github:
pip install git+ssh://github.com/kireygroup/fastsom
# or
pip install git+https://github.com/kireygroup/fastsom
Alternatively, you can clone the repository and then install as follows:
git clone git@github.com:kireygroup/fastsom
cd fastsom
python setup.py install
Docker boilerplate
This project was bootstrapped with the cookiecutter-dl-docker template.
Prerequisites
To run examples for this project you can either use Docker / Nvidia-Docker or recreate the environment on your local machine by using the provided requirements.txt.
Steps for Docker are described below.
Building the image
An utility script can be found in bin/build.sh:
./bin/build.sh
Running the container
A run script is available:
./bin/run.sh
This will mount the directories /fastsom and /nbs inside the container, allowing for code changes to be automatically replicated.
Note: if you plan on using Nvidia-Docker, you should use one of the images available on the Nvidia Container Repository.
The container will start a new Jupyter Notebook server on port 8888. Jupyter Lab is also available.
Note that the fastsom folder will be mounted inside the container, so any change you make to the source files or notebooks will be replicated on both host and container.
Developing inside the container
With Visual Studio Code and PyCharm, it is possible to use the container Python interpreter for development.
An SSH server has been configured inside the container to allow connection via PyCharm's remote interpreter feature.
In Visual Studio Code, this can be done via the Remote - Containers extension.
Documentation setup
Fastsom's documentation is built with Sphinx and deployed to Gihtub Pages via the gh-pages branch.
Documenting the code
We use a Numpy docstring notation (check out this link for more information about the various docstring styles).
Building the docs
To generate the static HTML documentation, use the following:
cd docs
make docs
Deploying the docs on GH Pages
Docs are automatically built from the master branch and pushed to the gh-pages branch on each version tag.
Metadata
Release files for fastsom 1.0.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 | |
|---|---|---|---|---|
| fastsom-1.0.2.tar.gz | 23.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fastsom-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.4 kB
Release files / fastsom-1.0.2.tar.gz
| Download URL | fastsom-1.0.2.tar.gz |
|---|---|
| Size | 23.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
772248c184749603a1ed6f815a870b8179d7f37db74e00bd914d0413c71ea440
|
|
BLAKE2b-256 checksum How to use checksums |
943f72ab11a3f473f0991c5091c544ee233642fcd54e90ef1a672b66c03e3334
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.6.9
|
Release files / fastsom-1.0.2-py3-none-any.whl
| Download URL | fastsom-1.0.2-py3-none-any.whl |
|---|---|
| Size | 31.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a32c294d47de33f0ff6472a93e6359129003e8799edfabea195946b98068d63f
|
|
BLAKE2b-256 checksum How to use checksums |
28f46a164e27243bf41cda269915431c60b6db3e2fae31ca3467395900a70775
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.6.9
|
Security for fastsom 1.0.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.
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.