AAMP User Interface
An app to control the automated additive manufacturing platform.
Installation
To use this app, you need to install Python (version 3.10 or higher).
In a terminal window in a new directory, run pip install aamp_app or pip install --upgrade aamp_app to install the app. Use the latter one to upgrade the app after it's installed. All dependencies will be installed with it. You may wish to use a virtual python environment if you don't want this app or its dependencies to interfere with your current system. On Mac or Linux-based systems, do this by running the following commands before installing:
pip install virtualenv: This line installs the virtualenv package which allows you to create virtual python environments.
virtualenv venv: This line creates a virtual environment (called venv) in the current directory. This will create a new folder (called venv) with the environment data.
source venv/bin/activate: This line activates the virtual environment. After activating the virtual environment, you should be able to see (venv) in your terminal window. If you close the terminal window/tab, you will have to execute this command to activate the environment again before using the app.
Usage
To start the app, run aamp_app. Enter the database user credentials for MongoDB. These credentials will be saved as plain text in a text file (called pw.txt) in the same directory. Therefore, this app should only be used on trusted computers. If the connection to the database cannot be established using the provided credentials, you will be required to run aamp_app again to retry. To delete the user credentials, simply delete the pw.txt file.
Device Requirements
Most devices should be able to connect to the app without any problems. However, certain devices require some drivers/software to create a connection. Due to the nature of the specific drivers/software, they must be installed separately.
Miscellaneous Commands (for dev)
Package app:
python3 setup.py sdist bdist_wheel
Upload to pip:
twine upload --skip-existing dist/*
Metadata
Release files for aamp-app 0.0.1.30
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 | |
|---|---|---|---|---|
| aamp_app-0.0.1.30.tar.gz | 85.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aamp_app-0.0.1.30-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 294.2 kB
Release files / aamp_app-0.0.1.30.tar.gz
| Download URL | aamp_app-0.0.1.30.tar.gz |
|---|---|
| Size | 85.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11a4bda5ded3641fbb1671c55ba1ba7116422ecfa5c14033e298c4326aca6f7a
|
|
BLAKE2b-256 checksum How to use checksums |
610750ab2190c61f80b1b6e296ff6fbfbbfcda39fb76aaac86ebc8ef21250fb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / aamp_app-0.0.1.30-py3-none-any.whl
| Download URL | aamp_app-0.0.1.30-py3-none-any.whl |
|---|---|
| Size | 208.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d12c653015e9150fd07807c6e513e9203becff0661a673dd3ad66a91ed5344ce
|
|
BLAKE2b-256 checksum How to use checksums |
504652782ffd260655615b296bb8ce30944d801020e47cb637288b84f27ea63c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for aamp-app 0.0.1.30
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.