Skip to main content

LADOCK

Molecular docking workstation built on the LADOCK pipeline, shipped as one package with two front-ends:

Command What it is
ladock-desktop PySide6 GUI workstation, dark Catppuccin theme
ladock-cli Rule-based (non-LLM) docking agent — guided wizard or fully scripted

Both share the same engines, the same preparation pipeline, and the same bundled bin/ tree. Proprietary software — free for academic use, commercial license required for for-profit use (see License).

LADOCK Desktop


Features

  • Multi-engine docking — AutoDock Vina, AutoDock 4, VinaGPU, AutoDock-GPU
  • Batch docking — run multiple ligands in parallel with built-in job scheduler
  • Ligand library management — import from CSV, SDF, or PDBQT; SMILES rendering via RDKit
  • Interactive 3D viewer — 3Dmol.js-powered molecular visualization
  • Non-covalent interaction analysis — H-bond, π-stacking, hydrophobic contacts, and more
  • Result explorer — sortable tables with binding energy results
  • Project management — save/load docking projects with structured job directories
  • Native cross-platform prep — receptor/ligand PDBQT preparation runs natively on Windows, Linux and macOS via Meeko + RDKit (no MGLTools, no WSL required for Vina/Vinardo)
  • Platform-aware engines — the docking UI enables only the scoring functions supported where LADOCK runs. The Windows build is pure-native (Vina/Vinardo); AutoDock4 / AutoDock-GPU are Linux-only and become available by running LADOCK inside WSL or on Linux

Requirements

  • Python ≥ 3.10
  • PySide6 ≥ 6.5
  • NumPy ≥ 1.24
  • SciPy ≥ 1.10
  • pandas ≥ 2.0
  • RDKit ≥ 2023.3 — molecular preparation and SMILES rendering
  • Meeko ≥ 0.5 (+ gemmi) — native receptor/ligand PDBQT preparation

Installation

One install provides both commands (Miniconda/Anaconda recommended on Windows):

pip install ladock

Upgrading from LADOCK 0.1.x? Releases up to 0.1.6 (March 2024) were a different, Apache-2.0 licensed command-line tool published under the same PyPI name. Version 2.0 is a rewrite with new commands (ladock-cli, ladock-desktop) and a different licence — see License. Pin ladock==0.1.6 if you depend on the old behaviour.

From a source checkout:

git clone https://github.com/laode-aman-ung/LADOCK.git
cd LADOCK
pip install -e .

The docking engines are far too large for a wheel, so they are fetched once, after install:

ladock-fetch-binaries

That downloads bin/<platform>/ into the package. If the install directory is read-only, put the binaries anywhere and point LADOCK_BIN at them.


Usage

ladock-desktop        # GUI workstation
ladock-cli            # guided docking wizard
ladock-cli dock --receptor rec.pdb --ligand lib.sdf --out results/ --native-ligand LIG

Equivalent module invocations — python -m ladock.desktop, python -m ladock.cli — work from a source checkout without installing.

WSL (Windows Subsystem for Linux)

AutoDock4 / AutoDock-GPU are Linux-only. Run LADOCK inside WSL, or from Windows:

scripts\ladock-wsl.bat

The launcher scripts in scripts/ (ladock.sh, ladock.bat, ladock.ps1, install.*) remain for source checkouts and desktop shortcuts; they discover a suitable Python and start the same entry points.


Workspace Structure

LADOCK/
├── ladock/               # The installed package (distribution: "ladock")
│   ├── paths.py          # Where bin/ and bundled resources live (shared)
│   ├── binaries.py       # `ladock-fetch-binaries`
│   ├── cli/              # `ladock-cli` — rule-based docking agent
│   │   └── agent.py      #   wizard, dock/components/prepare-receptor commands
│   ├── desktop/          # `ladock-desktop` — GUI workstation
│   │   ├── main.py       #   entry point
│   │   ├── app/          #   main window, dialogs, project manager
│   │   ├── core/         #   job models, WSL backend, tool paths, licensing
│   │   ├── data/         #   project model, result parser
│   │   ├── engine/       #   molecule prep, interaction analyzer, tool detector
│   │   ├── gui/          #   theme, panels, 3D viewer, assets
│   │   └── config/       #   example inputs
│   └── bin/              # Engine binaries, per platform (fetched, not in git):
│       ├── windows/      #   Vina (native .exe)
│       ├── linux/        #   Vina, AutoDock4/AutoGrid4, AD-GPU, ADFRsuite, MGLTools
│       └── mac/          #   Vina (native)
├── scripts/              # Launchers & installers for source checkouts
├── packaging/            # Release staging, PyInstaller spec, OS installers
├── docs/                 # CLI agent documentation
├── website/              # Project website (static HTML/CSS/JS)
└── HAKI/                 # Intellectual property (HakCipta, Merek)

Bundled Tools

Binaries live per platform under ladock/bin/<platform>/, fetched once with ladock-fetch-binaries:

Tool Version windows linux mac
AutoDock Vina 1.2.7 ✅ ✅ ✅
AutoDock 4 / AutoGrid 4 — ✅
AutoDock-GPU 1.6 ✅
ADFR / AGFR ADFRsuite 1.0 ✅
MGLTools 1.5.6 ✅
OpenBabel 2.4.1 (in ADFRsuite) ✅

Receptor and ligand PDBQT preparation is done natively by Meeko + RDKit on all platforms, so the Linux-only MGLTools bundle is only needed for the AutoDock4 / AutoDock-GPU grid path and flexible-receptor mode. The Windows build is pure-native (Vina/Vinardo only) and is deliberately not combined with WSL — to use the Linux engines, run LADOCK inside WSL or on Linux, where the app detects itself as a Linux host and enables the full engine set.

External tools (AutoDock-GPU, VinaGPU) can also be configured via Settings → Tool Paths.


Citation

If you use LADOCK in your research, please cite:

Aman LO, Ischak NI, Tuloli TS, Arfan A, Asnawi A. (2024). Multiple ligands simultaneous molecular docking and dynamics approach to study the synergetic inhibitory of curcumin analogs on ErbB4 tyrosine phosphorylation. Research in Pharmaceutical Sciences, 19(6), 754–765. https://doi.org/10.4103/RPS.RPS_191_23

Aman LO, Sihaloho M, Arfan A. (2023). Pencarian inhibitor DYRK2 dari database bahan alam ZINC15: Analisis farmakofor, simulasi docking dan dinamika molekuler. Jurnal Sains Farmasi & Klinis, 10(1), 100–113. https://doi.org/10.25077/jsfk.10.1.100-113.2023

Aman LO, Arfan A, Asnawi A. (2023). In silico study of the synergistic interaction of 5-fluorouracil and curcumin analogues as inhibitors of B-cell lymphoma 2 protein. International Journal of Applied Pharmaceutics, 15(Special Issue 2), 61–66. https://doi.org/10.22159/ijap.2023.v15s2.05

Third-party tools


License

LADOCK Desktop is proprietary software — Copyright (c) 2024 La Ode Aman. All rights reserved. See LICENSE for the full terms.

  • Free non-commercial use (2024–2029): free of charge for everyone — students, academics, independent researchers, and the general public — for non-commercial research, study, teaching, and evaluation. No registration, institutional email, or license key is required; the app activates the free academic license automatically until December 31, 2029. Subject to the citation requirement above.
  • Commercial use: requires a paid commercial license (for-profit companies, CROs, pharmaceutical/biotech firms, or any commercial R&D). Contact the licensor at laode_aman@ung.ac.id.

This is not an open-source license. Redistribution, sublicensing, and resale are not permitted.

Metadata

Release files for ladock 0.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ladock 0.3.1
File Size Uploaded
ladock-0.3.1.tar.gz 522.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ladock 0.3.1
File Interpreter ABI Platform
ladock-0.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / ladock-0.3.1.tar.gz

Download URL ladock-0.3.1.tar.gz
Size 522.9 kB
Tags Source
SHA-256 checksum
How to use checksums
e773513a2b156dbd9dc95000f9d02999d4207a8fb117beac21d2aff381a028b8
BLAKE2b-256 checksum
How to use checksums
0f5c67e3270946036ed5852c509b49caf30507ca9af67c471896efabb97943a9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.

Transparency log

Release files / ladock-0.3.1-py3-none-any.whl

Download URL ladock-0.3.1-py3-none-any.whl
Size 537.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bce6366736ee27ca3570a15651d8e9687fb30869134ed87913186ea76a9290e8
BLAKE2b-256 checksum
How to use checksums
1c1553f2d00cbde38b0671667aa84f63a1886e1fbaf1628f5446c37dcb3bc6ca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.2

2 release files

This release

0.3.1 This release

2 release files

0.3.0

2 release files

0.1.6

1 release file

0.1.1

1 release file

0.1.0

1 release file

0.0.9

1 release file

0.0.8

1 release file

0.0.7

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page