soco-device
A package for logging, saving, and automatically choosing device during model inference stage.
Usage
-
install package
pip install soco-device
-
example usage
from soco_device import DeviceCheck
dc = DeviceCheck()
# Return a device name ('cpu'/'cuda') and a list of gpu ids, if any
model_name_or_path = <model name>
n_gpu_needed = 2
device_name, device_ids = dc.get_device_by_model(model_name_or_path, n_gpu=n_gpu_needed)
# If only single gpu, set device_name as 'cuda:gpu_id'
# For either cpu or multi gpu case, set device_name as 'cpu'/'cuda'
device_name = '{}:{}'.format(device_name, device_ids[0]) if len(device_ids) == 1 else device_name
device = torch.device(device_name)
# ......
# Set up multi gpu training if available
if len(device_ids) > 1:
model = torch.nn.DataParallel(model, device_ids=device_ids)
# log gpu memory needed in inference stage
dc.log_start()
# ......
# inference model for one time here
dc.log_end()
dc.save(model_name_or_path)
Metadata
Release files for soco-device 0.0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| soco_device-0.0.5.2-py3-none-any.whl | Python 3 | none | any | Details for soco_device-0.0.5.2-py3-none-any.whl |
Release files / soco_device-0.0.5.2-py3-none-any.whl
| Download URL | soco_device-0.0.5.2-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c398cda97fe5c89c98dc51d942f1a2caeac2c160273532e74e8bacb93ac85b8
|
|
BLAKE2b-256 checksum How to use checksums |
1220615c73765ea8f2bf22141d6b398ba749589c7b3e8758d3de0d79fd6c5d49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.50.2 CPython/3.6.9
|
Security for soco-device 0.0.5.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.