Introduction
ColDA is an open source project aimed at providing distributed machine learning tools for data analysis and machine learning based on Assisted Learning.
Package
Getting Started
Use case
- Examples and Instructions can be found in
examples/
Package Stucture
-
Basic package structure can be found in Github repository
-
Compared to the Basic package structure,
docs/will contain different element. But at this point, you can follow the template -
py-pkgis the main part of the package, you can add more modules (with__init__.py) in this part. For example, if you addtempmodule, you can importtempmodule by:
import temp from py-pkg
-
This package structure can be improved by learning PyTorch package structure.
-
Basic Structure:
py-package-tempate/
|-- docs/
|-- |-- build_html/
|-- |-- build_latex/
|-- |-- source/
|-- py-pkg/
|-- |-- __init__.py
|-- |-- __version__.py
|-- |-- curves.py
|-- |-- entry_points.py
|-- tests/
|-- |-- test_data/
|-- | |-- supply_demand_data.json
|-- | __init__.py
|-- | conftest.py
|-- | test_curves.py
|-- .env
|-- .gitignore
|-- Pipfile
|-- Pipfile.lock
|-- README.md
|-- setup.py
How to Manage Package Environment
pipenvis used to manage package. You can installpipenvby:
pip3 install pipenv
- Use
pipenvto install package. The first command is to install the package for development. The second command is to install the package for production.
pipenv install --dev
pipenv install
- Use
pipenvto uninstall package:
pipenv uninstall
Pipenv Shells
- Entering into a Pipenv-managed shell. Remeber doing this every time before running the project.
cd py-package-tempate
pipenv install
pipenv shell
License
ColDA is licensed under the Apache 2.0 License.
Code of Conduct
Please review and adhere to the Code of Conduct when contributing to ColDA.
Reference
Please use the following reference
@article{diao2022gal,
title={GAL: Gradient Assisted Learning for Decentralized Multi-Organization Collaborations},
author={Diao, Enmao and Ding, Jie and Tarokh, Vahid},
journal={Advances in Neural Information Processing Systems},
volume={35},
pages={11854--11868},
year={2022}
}
Metadata
Release files for colda 0.0.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 | Actions |
|---|---|---|---|---|
| colda-0.0.1.tar.gz | 81.3 kB | Without provenance | Details for colda-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| colda-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for colda-0.0.1-py3-none-any.whl |
Total release size: 229.4 kB
Release files / colda-0.0.1.tar.gz
| Download URL | colda-0.0.1.tar.gz |
|---|---|
| Size | 81.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
249c2c2324fe4a3c04b859f14993537aa531bbdf403952527224235b59a0f468
|
|
BLAKE2b-256 checksum How to use checksums |
0be0d31df21ec6add9d346a1e181b774c9db131d76b29413fc82818755ac7cca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.7
|
Release files / colda-0.0.1-py3-none-any.whl
| Download URL | colda-0.0.1-py3-none-any.whl |
|---|---|
| Size | 148.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
371eeaf656013ba5c356652f57dc9ec852bf7a1999a897d77a26e619fce5035a
|
|
BLAKE2b-256 checksum How to use checksums |
745e9e5d70b5cfc8c3b000462b79f3803a7266a89476d78ee327dd09d90a732c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.7
|
Security for colda 0.0.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.