AIDD Codebase
A high-level codebase for deep learning development in drug discovery applications using PyTorch-Lightning.
Dependencies
The codebase requires the following additional dependencies
- CUDA >= 11.4
- PyTorch >= 1.9
- Pytorch-Lightning >= 1.5
- RDKit
- Optionally supports: tensorboard and/or wandb
Installation
The codebase can be installed from PyPI using pip, or your package manager of choice, with
$ pip install aidd-codebase
Usage
- Configuration: The coding framework has a number of argument dataclasses in the file arguments.py. This file contains all standard arguments for each of the models. Because they are dataclasses, you can easily adapt them to your own needs.
Does your Seq2Seq adaptation need an extra argument? Import the Seq2SeqArguments from arguments.py, create your own dataclass which inherits it and add your extra argument.
*It is important to note that the order of supplying arguments to a script goes as follows:*
- --flags override config.yaml
- config.yaml overrides default values in arguments.py
- default values from arguments.py are used when no other values are supplied
At the end, it stores all arguments in config.yaml
- Use: The coding framework has four main parts:
- utils
- data_utils
- models
- interpretation
These parts should be used
- File Setup: The setup of the files in the system is best used as followed:
coding_framework
|-- ..
ESR X
|-- project 1
|-- data
|-- ..
|-- Arguments.py
|-- config.yaml
|-- main.py
|-- datamodule.py
|-- pl_framework.py
Contributors
All fellows of the AIDD consortium have contributed to the packaged.
Code of Conduct
Everyone interacting in the codebase, issue trackers, chat rooms, and mailing lists is expected to follow the PyPA Code of Conduct.
2 maintainers
Metadata
2 maintainers
Release files for aidd-codebase 0.2.0
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 | |
|---|---|---|---|---|
| aidd-codebase-0.2.0.tar.gz | 9.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aidd_codebase-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.2 kB
Release files / aidd-codebase-0.2.0.tar.gz
| Download URL | aidd-codebase-0.2.0.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b71c5a92905947e809c2429ca8a876c690922c3b9d980e3f53a0c46fa2f64c3a
|
|
BLAKE2b-256 checksum How to use checksums |
ace26762d0cc4873ea1e17a116a87720d0e91045dd5f256c6b219a32b79124c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.9.5 Linux/5.17.5-76051705-generic
|
Release files / aidd_codebase-0.2.0-py3-none-any.whl
| Download URL | aidd_codebase-0.2.0-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5806856691676f0708135c1a98b82bc3f398f0465a433afe94edc7d91bebe1a4
|
|
BLAKE2b-256 checksum How to use checksums |
2cb0146bb2364191370a41157221f41042ce86175b85058de100d2bc79646621
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.9.5 Linux/5.17.5-76051705-generic
|
Security for aidd-codebase 0.2.0
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.
