Bayesian ALS Tracking and Phase Evaluation
If you would like to try the ALSTracker, we host it at the MPI Dortmund:
https://alstracker.mpi-dortmund.mpg.de/
How to install your own server (Ubuntu)
- Install a linux, e.g. Ubuntu
- Install git
sudo apt install git - Install nginx
sudo apt install nginx - Install supervisorctl
sudo apt install supervisor - Download and unzip mogp model: https://fraenkel.mit.edu/mogp/
- Download and install miniforge
curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"bash Miniforge3-$(uname)-$(uname -m).shMINICONDA_DIR=~/miniforge3${MINICONDA_DIR}/bin/conda init- Logout and login again
conda activate alstrackerpip install alstracker
- Clone this repository
git clone https://github.com/MPI-Dortmund/ALSTracker cd ALSTracker- Create a new conda environment
conda env create -f ./conda.yaml
- Adjust the variables
XXX_RUN_DIR_XXX,XXX_MINIFORGE_XXX,XXX_USER_XXX,XXX_GROUP_XXX,XXX_MOGP_PKL_XXXbased on the decisions in the previous steps ingunicorn_start.sh - Adjust the
command,stdout_logfile,uservariables inals_tracker.conf.template - Copy or link the
als_tracker.conf.templateto/etc/supervisor/conf.dsudo ln -s $(realpath als_tracker.conf.template) /etc/supervisor/conf.d/als_tracker.conf
- Start the tracker
sudo supervisorctl start als_tracker
- Adjust the variables
XXX_RUN_DIR_XXX,XXX_LOG_DIR_XXX,XXX_SERVERNAME_XXXin the nginx.template- Make sure that the
XXX_LOG_DIR_XXXdirectory is writable for thewww-datagroup. For example if you chose a directory in your home directory, make sure to allow r/w to the www-data group. (e.g.sudo chgrp www-data .)
- Make sure that the
- Copy or link the
nginx.templateto/etc/nginx/sites-enabledsudo ln -s $(realpath nginx.template) /etc/nginx/sites-enabled/als_tracker.site
- Get a certificate for the SERVERNAME (This should alter your als_tracker.site file)
sudo snap install certbot --classicsudo certbot --nginx
- Restart nginx
sudo systemctl restart nginx
Metadata
Release files for ALSTracker 1.4.3
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 |
|---|---|---|---|---|
| alstracker-1.4.3.tar.gz | 858.5 kB | Without provenance | Details for alstracker-1.4.3.tar.gz |
Release files / alstracker-1.4.3.tar.gz
| Download URL | alstracker-1.4.3.tar.gz |
|---|---|
| Size | 858.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a88213df52459c328ee9618961e4c752a743467c599224c76d2a13bb72831ddb
|
|
BLAKE2b-256 checksum How to use checksums |
ae77de432d1283f2d00975b80e9cf334523a1d6fb4b901002f2b5ad42da5941a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Security for ALSTracker 1.4.3
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.