AcceleratorModule CLI
CLI for AcceleratorModule library (accmt).
This is a command-line tool wrapper around Accelerate's command-line utilities ('accelerate').
Installation
accmt-cli is automatically installed when installing accmt library. You also install it via pip:
pip install accmt-cli
Launch
You can launch any distributed training process with the following command:
accmt launch [-N][-n, --gpus][-O1][--strat] <your_python_script> [...]
Where:
- -N (optional): Corresponds to the number of processes, or a Python-like slice to take GPUs from a certain index (e.g. '-N=2:', to take GPUs from index 2).
- -n or --gpus (optional): Corresponds to a list of CUDA devices (e.g. '-n=1,3,5,6', to take GPUs indices 1, 3, 5 and 6).
- -O1 (optional): Corresponds to the optimization of type 1, which calculates the efficient number for 'OMP_NUM_THREADS', depending on how many processes you will run you training script.
- --strat (optional): Corresponds to the specific strategy to implement, or a configuration file path from Accelerate ('accelerate config --config_file=your-config.yaml'). See 'accmt strats' for specific strategies. ... (optional): You can add here any additional arguments that your Python script might have.
Get model from checkpoint
You can get a model from any checkpoint using the following command:
accmt get <checkpoint> --out=<output-model-directory> [--dtype]
Where:
- --out or -O (REQUIRED): Output model directory name where to save the model.
- --dtype (Optional): PyTorch data type of model parameters. Default is 'float32'.
Strats
You can check the specific strats included with the following command:
accmt strats [--ddp][--fsdp][--deepspeed]
Where:
- --ddp: To only filter for DDP strategies.
- --fsdp: To only filter for FSDP strategies.
- --deepspeed: To only filter for DeepSpeed strategies.
Example
Generate an example HPS file config with the following command:
accmt example
This will generate a file on your current directory called 'hps_example.yaml'.
Debug
Enable debug mode with:
accmt debug [--level] ...
Where --level flag is an integer number, which indicates the level of debugging. Available levels are:
LEVEL 1:
- Disables logging (MLFlow, Tensorboard, etc).
LEVEL 2:
- Disables model and teacher compilation.
LEVEL 3:
- Disables model saving, checkpointing and resuming (no folders will be created).
LEVEL 4 (default):
- Force
eval_when_start(in Trainer) to False.
LEVEL 5:
- Disables any evaluation.
Metadata
Release files for accmt-cli 1.4.7.1
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 | |
|---|---|---|---|---|
| accmt_cli-1.4.7.1.tar.gz | 13.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| accmt_cli-1.4.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 77.4 kB
Release files / accmt_cli-1.4.7.1.tar.gz
| Download URL | accmt_cli-1.4.7.1.tar.gz |
|---|---|
| Size | 13.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae8e3b24131afe1bc046fed9b45ebf609b34dac55c00e188ae201e1f18244b97
|
|
BLAKE2b-256 checksum How to use checksums |
a06dd1bff865a96ba4238f6e64ffa2ce40fd0a2620c7f7a43b8fceed2aff206c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.11
|
Release files / accmt_cli-1.4.7.1-py3-none-any.whl
| Download URL | accmt_cli-1.4.7.1-py3-none-any.whl |
|---|---|
| Size | 63.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c04a5cd2532155b829dd74cb041385799dd3d73aea78684df38dbcaec15d7dd
|
|
BLAKE2b-256 checksum How to use checksums |
0933f50c9eff1a2fc0a62cf9ff2165132a9eb6f24e46c97086ced60bbf2a7d03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.11
|
Security for accmt-cli 1.4.7.1
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.