AB3 Developer Notes: Difference between revisions

From DISI
Jump to navigation Jump to search
(Created page with "'''UNDER DEVELOPMENT''' The back-end and the front-end of this tool can be accessed at ABBB and AB3FrontEnd repositories at https://gitlab.docking.org, respectively. The backend runs on flask and has two main scripts running that do all the main calculations, which are BespokeAnaloging.py and arthorquery.py. The Bespoke Analoging script gets called in the routes section with the call_ABBB function. There we use a json file with all our reaction information as the first...")
 
No edit summary
Line 1: Line 1:
'''UNDER DEVELOPMENT'''
'''UNDER DEVELOPMENT'''


The back-end and the front-end of this tool can be accessed at ABBB and AB3FrontEnd repositories at https://gitlab.docking.org, respectively. The backend runs on flask and has two main scripts running that do all the main calculations, which are BespokeAnaloging.py and arthorquery.py. The Bespoke Analoging script gets called in the routes section with the call_ABBB function. There we use a json file with all our reaction information as the first input and a smiles string as the second input which we get from the frontend. This script takes those inputs and runs the smiles against all those reactions and spits out building blocks if any of the reactions worked on the smiles. Those building blocks as well as a tanimoto coefficent can then be used in the following sctipt: arthorquery.py. The script takes all the building blocks that were dereived from the first script and uses arthor to find similar building blocks using the tanimoto coefficient and using inclusion and exclusion rules as a basis for the new analogs.
The back-end and the front-end of this tool can be accessed at ABBB and AB3FrontEnd repositories at https://gitlab.docking.org, respectively. The backend runs on Flask and has two main scripts running that do all the main calculations, which are BespokeAnaloging.py and arthorquery.py. The Bespoke Analoging script gets called in the routes section with the call_ABBB function. There we use a JSON file with all our reaction information as the first input and a smiles string as the second input which we get from the front-end. This script takes those inputs and runs the smiles against all those reactions and spits out building blocks if any of the reactions worked on the smiles. Those building blocks as well as a Tanimoto coefficient can then be used in the following script: arthorquery.py. The script takes all the building blocks that were derived from the first script and uses Arthor to find analogs of the building blocks using similarity against the Tanimoto coefficient and inclusion and exclusion rules as a basis.

Revision as of 18:52, 21 March 2023

UNDER DEVELOPMENT

The back-end and the front-end of this tool can be accessed at ABBB and AB3FrontEnd repositories at https://gitlab.docking.org, respectively. The backend runs on Flask and has two main scripts running that do all the main calculations, which are BespokeAnaloging.py and arthorquery.py. The Bespoke Analoging script gets called in the routes section with the call_ABBB function. There we use a JSON file with all our reaction information as the first input and a smiles string as the second input which we get from the front-end. This script takes those inputs and runs the smiles against all those reactions and spits out building blocks if any of the reactions worked on the smiles. Those building blocks as well as a Tanimoto coefficient can then be used in the following script: arthorquery.py. The script takes all the building blocks that were derived from the first script and uses Arthor to find analogs of the building blocks using similarity against the Tanimoto coefficient and inclusion and exclusion rules as a basis.