The docking program DOCK is parameterized by several files, each controlling different aspects of the program's behavior, such as the sampling algorithm for molecular poses or the scoring function for estimating the free energy of binding for each molecular pose. These files are known as "dockfiles" and exist in custom formats exclusive to DOCK and related software (e.g., matching_spheres.sph). In this work, we use the term DOCK parameterization to refer to a specific set of dockfiles, and we take a DOCK parameterization combined with a DOCK executable to constitute a docking model. (i.e., a step s takes {x, ...} as input and produces {y, ...} as output, so output y depends on input x). For example, matching_spheres.sph depends on rec.crg.pdb in the matching spheres generation step . A child node can be created only once all its parent nodes exist. The input files completely determine the blaster DAG, which is automatically derived from them by a deterministic process. Starting from the root nodes of the blaster DAG, a multitude of different branching paths are taken, with each path leading to a distinct leaf node. A specific combination of leaf nodes represents a specific DOCK parameterization, and their respective paths from the root nodes in sum completely define how it is created from the input files. Once initialized, the blaster DAG serves as a pipeline of steps that generates the DOCK parameterizations corresponding to all valid combinations of leaf nodes.