acedrg -h
acedrg -v (or --version)
acedrg -c (or --mmcif=) input_mmcif_file -o (or --out=) name_root_for_output_files -r (or --res= ) output_short_monomer_name(optional)
acedrg -i (or --smi= ) input_file_containing_a_SMILES_string -o (or --out=) name_root_for_your_output_files -r (or --res= ) output_short_monomer_name(optional)
acedrg -m (or --mol= ) input_mol_file -o (or --out=) name_root_for_output_files -r (or --res= ) output_short_monomer_name(optional)
acedrg -g (or --mol2=) input_mol2_file -o (or --out=) name_root_for_output_files -r (or --res= ) output_short_monomer_name(optional)
acedrg -L (or --linkInstruction=) instruction_file_for_build_covalent-links (txt format) -o (or --out=) name_root_for_output_files -r (or --res= ) output_short_monomer_name(optional)
Description
Input and output files
Usage
Keyworded input
References
Authors and credits
How to cite ACEDRG
The program ACEDRG is designed for the derivation of stereo-chemical information about monomers/ligands (or small molecules). It uses atom typing based on local chemical and topological environment to organise bond lengths and angles from a small molecule database i.e. the Crystallography Open Database (COD). Information about hybridisation states of atoms, small ring belongingness (up to seven membered rings), ring aromaticity and nearest-neighbour information is encoded in the atom types. All atoms from COD have been classified according to the generated atom types. All bonds and angles have also been classified according to the atom types, and, in a certain sense, bond types.
Using the tables containing those bonds and angles, ACEDRG can derive ideal
bond lengths, angles for an unknown monomer/ligand. It also generates information onabout planar groups and stereo-chemical properties in the monomer/ligand. The minumum information Acedrg requires is element types of atoms in the monomer/ligand, and the basic bonding pattern in the monomer/ligand, such as atom connnections and bond-orders. Of course, users can provide some extra information such as coordinates of atoms, information about known chiral-centers.
Acedrg can also generate link information encapsulating covalent bond between two monomers. A user needs to define atoms to be covalently bonded with the bond order as well as atoms that need to be removed from each monomer. Acedrg generates a file containing (1) information on the link, i.e. the bonds, angles and torsion angles that involve atoms from both monomerss, (2) information about modifications of both monomers. Modification can contain change, deletion or addition of atoms, atom types, bonds, angles torsion angles, planaritites, chiral centres and nominal charges.
Note: When a link are generated AceDRG requires that all bond orders of both monomers to be one of "single", "double", "triple". "Deloc" or "aromatic" bond orders can confuse AceDRF. It is therefore recommended that before running AceDRG in link generation mode both monomers should be generated by AceDRG.
Note 2: In cases like bonds between phosphate , carboxyl groups and other ligand one must make sure that the correct atom is selected. Usually atom with formal charge should be selected as an atom involved in covalent link. Before generating link imformation one must study the chemistry of covalent bonds between monomers.
When used to generate a full descriptioon of a monomer/ligand, Acedrg can take several input file formats used in the computational chemistry: SMILES, mmCIF, SDF/MOL, and SYBYL MOL2 files. It outputs ACEDRG-derived ideal
bond lengths, angles, plane groups, aromatic rings and chirality information, and writes them to an file of mmCif format that can be used by the refinement programs and model building programs. AceDRG also outputs a set of coordinates in the PDB file format.
An input instruction file is required for running Acedrg in covalent link generation mode.
"C1=CC=CC(CCC2)=C12", which can be feed into command-lines
a_smiles.smi, which contains the above SMILES string and can be feed into command-lines
201
Mrv0541 02231214312D
14 15 0 0 0 0 999 V2000
3.0791 1.6500 0.0000 O 0 0 0 0 0 0 0 0 0 0 0 0
1.6500 -0.8250 0.0000 O 0 0 0 0 0 0 0 0 0 0 0 0
3.0791 -0.8250 0.0000 N 0 0 0 0 0 0 0 0 0 0 0 0
4.5741 0.6639 0.0000 N 0 0 0 0 0 0 0 0 0 0 0 0
2.3645 0.4125 0.0000 N 0 0 0 0 0 0 0 0 0 0 0 0
4.5741 -0.6639 0.0000 N 0 0 0 0 0 0 0 0 0 0 0 0
3.7935 0.4125 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
3.7935 -0.4125 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
3.0791 0.8250 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
2.3645 -0.4125 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
5.0556 0.0000 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
3.0791 -1.6500 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
4.8305 1.4482 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
1.6500 0.8250 0.0000 C 0 0 0 0 0 0 0 0 0 0 0 0
1 9 2 0 0 0 0
2 10 2 0 0 0 0
3 8 1 0 0 0 0
3 10 1 0 0 0 0
3 12 1 0 0 0 0
4 7 1 0 0 0 0
4 11 1 0 0 0 0
4 13 1 0 0 0 0
5 9 1 0 0 0 0
5 10 1 0 0 0 0
5 14 1 0 0 0 0
6 8 1 0 0 0 0
6 11 2 0 0 0 0
7 8 2 0 0 0 0
7 9 1 0 0 0 0
M END
#
data_comp_list
loop_
_chem_comp.id
_chem_comp.three_letter_code
_chem_comp.name
_chem_comp.group
_chem_comp.number_atoms_all
_chem_comp.number_atoms_nh
_chem_comp.desc_level
UNL UNL . NON-POLYMER 70 39 .
#
data_comp_UNL
#
loop_
_chem_comp_atom.comp_id
_chem_comp_atom.atom_id
_chem_comp_atom.type_symbol
_chem_comp_atom.type_energy
_chem_comp_atom.charge
_chem_comp_atom.x
_chem_comp_atom.y
_chem_comp_atom.z
UNL N N NT2 0 -3.654 2.378 1.008
UNL C27 C CH1 0.000 -4.053 1.059 0.498
UNL C28 C CH1 0.000 -5.015 0.357 1.466
UNL O4 O OH1 0.000 -6.187 1.144 1.627
UNL C29 C CH1 0.000 -5.373 -1.044 0.973
UNL C21 C CR66 0.000 4.504 -0.782 0.373
................
loop_
_chem_comp_bond.comp_id
_chem_comp_bond.atom_id_1
_chem_comp_bond.atom_id_2
_chem_comp_bond.type
_chem_comp_bond.aromatic
_chem_comp_bond.value_dist
_chem_comp_bond.value_dist_esd
UNL N C27 single n 1.470 0.013
UNL C27 C28 single n 1.532 0.010
UNL C27 C26 single n 1.512 0.020
UNL C28 O4 single n 1.421 0.011
UNL C28 C29 single n 1.523 0.010
................
loop_
_chem_comp_angle.comp_id
_chem_comp_angle.atom_id_1
_chem_comp_angle.atom_id_2
_chem_comp_angle.atom_id_3
_chem_comp_angle.value_angle
_chem_comp_angle.value_angle_esd
UNL C27 N HN1 109.984 3.00
UNL C27 N HN2 109.984 3.00
UNL HN1 N HN2 108.673 3.00
UNL N C27 C28 111.315 2.25
UNL N C27 C26 111.865 2.42
UNL N C27 H27 108.113 1.50
................
_chem_comp_tor.comp_id
_chem_comp_tor.id
_chem_comp_tor.atom_id_1
_chem_comp_tor.atom_id_2
_chem_comp_tor.atom_id_3
_chem_comp_tor.atom_id_4
_chem_comp_tor.value_angle
_chem_comp_tor.value_angle_esd
_chem_comp_tor.period
UNL sp3_sp3_80 C28 C27 N HN1 -60.000 10.00 3
UNL sp3_sp3_112 C27 C26 O3 C25 180.000 10.00 3
UNL sp3_sp3_115 C24 C25 O3 C26 180.000 10.00 3
UNL sp3_sp3_20 C12 C24 C25 O3 180.000 10.00 3
UNL sp3_sp3_121 O3 C25 C9 C11 60.000 10.00 3
................
loop_
_chem_comp_chir.comp_id
_chem_comp_chir.id
_chem_comp_chir.atom_id_centre
_chem_comp_chir.atom_id_1
_chem_comp_chir.atom_id_2
_chem_comp_chir.atom_id_3
_chem_comp_chir.volume_sign
UNL chir_1 N C27 HN1 HN2 both
UNL chir_2 C27 N C26 C28 negative
UNL chir_3 C28 O4 C29 C27 negative
................
loop_
_chem_comp_plane_atom.comp_id
_chem_comp_plane_atom.plane_id
_chem_comp_plane_atom.atom_id
_chem_comp_plane_atom.dist_esd
UNL plan-1 C11 0.020
UNL plan-1 C13 0.020
UNL plan-1 C14 0.020
UNL plan-1 C15 0.020
UNL plan-1 C16 0.020
UNL plan-1 C17 0.020
UNL plan-1 C20 0.020
................
loop_
_pdbx_chem_comp_descriptor.comp_id
_pdbx_chem_comp_descriptor.type
_pdbx_chem_comp_descriptor.program
_pdbx_chem_comp_descriptor.program_version
_pdbx_chem_comp_descriptor.descriptor
UNL SMILES ACDLabs 10.04 "O=C6c2cc1ccccc1cc2C7C4(c3ccccc3CCC4=O)C(OC5OC(C(O)C(O)C5N)CO)CC67"
UNL SMILES_CANONICAL CACTVS 3.341 "N[C@@H]1[C@@H](O)[C@H](O)[C@@H](CO)O[C@H]1O[C@H]2C[C@H]3[C@H](c4cc5ccccc5cc4C3=O)[C@@]26C(=O)CCc7ccccc67"
UNL SMILES CACTVS 3.341 "N[CH]1[CH](O)[CH](O)[CH](CO)O[CH]1O[CH]2C[CH]3[CH](c4cc5ccccc5cc4C3=O)[C]26C(=O)CCc7ccccc67"
acedrg -i "C1=CC=CC(CCC2)=C12" -o my_ligand
When the job finishes, you will see two output files, my_ligand.cif and my_ligand.pdb.
acedrg -i my_ligand.smi -o my_ligand
The file - my_ligand.smi, contains a SMILES string, such as C1=CC=CC(CCC2)=C12.
Again, the output files are my_ligand.cif and my_ligand.pdb.
acedrg -c my_ligand.cif -o my_ligand_fromAcedrg
Output files:
my_ligand_fromAcedrg.cif - description file in a ccp4 mmcif ligand format
my_ligand.pdb - coordinate file in the PDB format
acedrg -m my_ligand.mol -o my_ligand
Output files:
my_ligand_fromAcedrg.cif - description file in a ccp4 mmcif ligand format
my_ligand.pdb - coordinate file in the PDB format
acedrg -g my_ligand.mol2 -o my_ligand
Outut files:
my_ligand_fromAcedrg.cif - description file in a ccp4 mmcif ligand format
my_ligand.pdb - coordinate file in the PDB format
acedrg -h
-h signals that AceDRG print out a help manual that contains all options. It will print some info about all input options.
acedrg -v
-v signals that AceDRG will print out its version number.
acedrg -c my_ligand.cif -o my_ligand_fromAcedrg -r a_3_letter_ligand_name
-r signals that AceDRG will use the input a_3_letter_ligand_name as the
short name for the ligand in the output mmcif file, i.e. my_ligand_fromAcedrg.cif.
acedrg -c my_ligand.cif -o my_ligand_fromAcedrg -p
-p signals that AceDRG must use the coordinates from the input file.
acedrg -m my_ligand.mol -o my_ligand -K (upper case)
-K signals that AceDRG will keep protonation state defined in the input file
acedrg -i my_ligand.smi -o my_ligand -j n (an integer)
-j signals that AceDRG will try to generate n initial conformers and
optimize them. Then output one conformer that corresponds
to the lowest engergy.
acedrg -i my_ligand.smi -o my_ligand -k n (an integer)
-k signals that AceDRG will try to generate n initial conformers and
optimize them. Then output all those n different files.
acedrg -i my_ligand.smi -o my_ligand -l (low case) n (an integer)
-l signals that AceDRG will make RDKit to run number of n steps in
its geometrical optimizations for the molecule conformers. It
is usually used together with option -k or -j to get better
conformers. But it may take much longer time.
acedrg -o my_atom_types_in_ligand -n
-n signals that AceDRG will generate two kinds of atom types (CCP4 type, aceDRG type)
for all atoms of the ligand. Then output all atom types in an output file,
i.e. my_atom_types_in_ligand.txt
acedrg -L(upper case) my_instructions.txt -o my_link
LINK: RES-NAME-1 2OP FILE-1 2OP_acedrg.cif ATOM-NAME-1 C RES-NAME-2 VAL ATOM-NAME-2 N
It means that AceDRG will generate a link between atoms C of 2OP and N of VAL. The description of 2OP is in the file 2OP_acedrg.cif and the description of VAL is from the monomer library.
acedrg -c 2OP.cif -o 2OP_acedrg -p
LINK: RES-NAME-1 2OP FILE-1 2OP_acedrg.cif ATOM-NAME-1 C RES-NAME-2 VAL ATOM-NAME-2 N DELETE ATOM OXT 1
which means that atom, OXT, in ligand 1, i.e. 2OP will be deleted when the link is generated. DELETE instructions should be at the end of the instruction line.
LINK: RES-NAME-1 CYS ATOM-NAME-1 SG RES-NAME-2 TMP FILE-2 TMP.cif ATOM-NAME-2 C1 CHANGE BOND C1 C2 SINGLE 2
which means that the bond between C1 and C2 in ligand 2, i.e. TMP will be changed into a bond order of single.
LINK: RES-NAME-1 LYS ATOM-NAME-1 NZ RES-NAME-2 PLP FILE-2 PLP_acedrg.cif ATOM-NAME-2 C4A BOND-TYPE DOUBLE DELETE ATOM O4A 2
which means that the bond order between NZ in LYS and C4A in PLP_acedrg.cif is double.
The main reference for ACEDRG is:
Fei Long, Robert A Nicholls, Paul Emsley, Saulius GraZulis, Andrius Merkys,
Antanas Vaitkus and Garib N Murshudov
"ACEDRG: A stereo-chemical description generator for ligands"
Acta Cryst. (2017), D73, 112-122.
AceDRG uses rdkit for chemistry perception and REFMAC for :
For RDKit cite
RDKit Documentation
For REFMAC cite
Murshudov, G. N., Skubak, P., Lebedev, A. A., Pannu, N. S., Steiner, R. A., Nicholls, R. A. ,
Winn, M. D., Long, F. & Vagin, A. A.
REFMAC5 for the refinement of macromolecular crystal structures
Acta Cryst. (2011), D67, 355-367
RDKit REFMAC