BR-SAScore
Implementation of BR-SAScore developed by Prof. Yousung Jung group at Seoul National University (contact: yousung@gmail.com).
Contents
- Developer
- OS Requirements
- Python Dependencies
- Installation Guide
- Usage
- Data
- Reproduce the results
- Publication
- License
Developer
Shuan Chen (shuan.micc@gmail.com)
OS Requirements
This repository has been tested on both Linux and Windows operating systems.
Python Dependencies
- Python (version >= 3.6)
- Numpy (version >= 1.16.4)
- rdkit (version >= 2019)
Installation Guide
From Github
pip install BRSAScore
From Github
git clone https://github.com/snu-micc/BR-SAScore.git
cd BR-SAScore
pip install -e .
Usage
from BRSAScore import SAScorer
scorer = SAScorer()
smi = 'CC(OC1=CC=CC=C1C(O)=O)=O' # Aspirin
score, contribution = scorer.calculateScore(smi)
The expected output of score should be
0.8789047205405656
See Demo.ipynb for the examples of estimating the synthetic accessibility of 18 structurally complex molecules shown in the paper.
Data
USPTO reaction dataset
The reactions of of the training reactions train_data.csv are downloaded from the Dropbox link available at the GitHub repo of GLN, originally from Figshare.
Building blocks
The zip file of eMolecules building blocks origin_dict.csv can be downloaded from the Dropbox link available the GitHub repo of Retro*.
Reproduce the results
[1] Download reaction and building-block data
Downlaod the data can put them in ./data/ and rename them to uspto.csv and emolecules.csv with column titled reactants>reagents>production and SMILES.
Feel free to change the (atom-mapped) reaction data and building blocks data as long as the data is correctly formatted. If the reaction data is not atom-mapped, we recommend to use LocalMapper to prepare high-quality the atom-mappings for your reactions.
[2] Prepare the BRScores from reaction and building-block data
Prepare the BRSAScores by
python scripts/prepare_Scores.py -r uspto -b emolecules
[3] Use BRSAScocre
from BRSAScore import SAScorer
reaction_from = 'uspto'
buildingblock_from = 'emolecules'
scorer = SAScorer(reaction_from=reaction_from, buildingblock_from=buildingblock_from)
To use the BRSAScore on you own data, replace the reaction_from and buildingblock_from
Publication
@article{chen2021deep, title={Estimating the synthetic accessibility of molecules with building block and reaction-aware SAScore}, author={Chen, Shuan and Jung, Yousung}, journal={Journal of Cheminformatics}, volume={}, number={}, pages={}, year={2024}, publisher={Springer} }
License
This project is covered under the MIT Liscence.
Metadata
Release files for BRSAScore 0.1.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 |
|---|---|---|---|---|
| BRSAScore-0.1.1.tar.gz | 13.0 MB | Without provenance | Details for BRSAScore-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| BRSAScore-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for BRSAScore-0.1.1-py3-none-any.whl |
Total release size: 26.0 MB
Release files / BRSAScore-0.1.1.tar.gz
| Download URL | BRSAScore-0.1.1.tar.gz |
|---|---|
| Size | 13.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
685cf1be63a7412cd2a416be3dda191b61c1723b6af9a2cc32d73c35b103d983
|
|
BLAKE2b-256 checksum How to use checksums |
7b1f05cdabc82740cebf53f39c17c8bc09995c613ab64e4b843b1018a69b65c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.10.0 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/1.0.0 urllib3/1.26.18 tqdm/4.64.1 importlib-metadata/4.8.3 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.5 CPython/3.6.13
|
Release files / BRSAScore-0.1.1-py3-none-any.whl
| Download URL | BRSAScore-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b292b58f61e7bae5a27d8b5159de70856cf71f0177ed261e76956b15820b667
|
|
BLAKE2b-256 checksum How to use checksums |
c662264fb1161590a86f14765b2606fa7daf7dc79e4a6191d3a26919158978d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.10.0 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/1.0.0 urllib3/1.26.18 tqdm/4.64.1 importlib-metadata/4.8.3 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.5 CPython/3.6.13
|
Security for BRSAScore 0.1.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.