The workflow was executed on Linux x86_64 CPU using the public 1EVE/E20 example. GNINA 1.3.3 generated three poses, PoseBusters 0.6.5 checked all three, and PLIP 2.4.0 analyzed all three with matching chemical identity. This is computational workflow validation; no experimental or biological validation has been performed.
Tested host: Ubuntu 24.04.2, Linux x86_64, two vCPUs, about 8 GiB RAM, Python 3.12.15. The project has its own environment and versioned GNINA binary; the SHA-256 is 3340c1f49cd3c7c84d8699182a1c6af13c7fa2a22448d1204640446106f72172. Although execution uses --no_gpu, this binary needs CUDA/cuDNN loader libraries. They are installed only in the project environment and available through the isolated environment, together with the Open Babel Xrender dependency. No system CUDA driver or global Python modification was needed. The measured GNINA command took about 45 seconds on this host; this is one observation, not a runtime guarantee. The recorded installation and shared caches occupied about 8.3 GiB; this is an observed footprint, not a minimum storage requirement. Downloads require network access; no privacy audit is claimed.
Docking/CNN scores are not measured affinity, IC50 or efficacy. PoseBusters checks configured plausibility and reference criteria; PLIP reports rule-based contacts in supplied coordinates. This one known-pocket fixture does not establish general docking accuracy, cross-platform compatibility or biological activity. No independent prediction RMSD calculation was performed: the report retains PoseBusters' configured RMSD-threshold booleans. Neutral ligand choice, stripped water/glycans and unmodeled termini constrain interpretation.
Setup time is an estimate, not a measured total installation time.