replica_exchange(1)
π replica_exchange β the manual, but make it make sense π
okay bestie, sit down, hydrate, because we're about to talk about replica_exchange from the Cooperative Computing Tools, manual section 1. this one is a whole moment. π«Ά
β¨ NAME β¨
replica_exchange β a Work Queue application for running replica exchange simulations using ProtoMol. yes, that's the whole name. short. iconic. she knows what she is. π
πΈ SYNOPSIS πΈ
replica_exchange [options] <pdb_file> <psf_file> <par_file> <min_temp>
<max_temp> <num_replicas>
π¦ DESCRIPTION π¦
so, replica_exchange is a Work Queue application for running replica exchange simulations using the ProtoMol simulation package. and listen β she supports both barrier and non-barrier based runs. versatile queen. π
the barrier based run transfers the configuration files and input data for each replica to the connected work_queue_worker() instances, runs the ProtoMol simulation package, and gathers the output, at every single Monte Carlo step. it literally waits for the simulation of all replicas to finish at each step before it moves on to the next step, which means yeah, it incorporates a barrier at every step. no skipping ahead, no cutting corners. and at the end of every step? it randomly picks two neigboring replicas, applies the metropolis criterion, and if that criterion is satisfied, it swaps the parameters of the two replicas and keeps the simulations going. π
the non-barrier based run is equivalent to the barrier run in the output and results it produces. same vibes, same receipts. BUT it avoids using a barrier by running multiple monte carlo steps for each replica until that replica gets picked to attempt an exchange. by default, the application will run using this non-barrier implementation. so that's the default girlie. β¨
the pdb_file, psf_file, and par_file arguments specify the input files required for the simulation run. the min_temp and max_temp specify the temperature range in which the replicas are simulated. and the number of replicas being simulated is given by num_replicas. that's the whole roster. π
replica_exchange can be run on any machine accesible to work_queue_worker instances. anywhere. she travels. π
π OPTIONS π
-n <name>β Specify a project name for using exclusivework_queue_workerinstances. it's giving β¨exclusiveβ¨.-x <filename>β Specify the name of thexyzfile for output.-d <filename>β Specify the name of thedcdfile for output.-m <number>β Specify the number of monte carlo steps. Default =100.-s <number>β Specify the number of molecular dynamics steps. Default =10000.-p <path>β Specify path for storing output files.-qβ Assign closer temperature values to replicas in the first and last quartile.-iβ Assume ProtoMol is installed and available inPATHon worker site.-bβ Use barrier in waiting for all replicas to finish their steps before attempting exchange.-lβ Print debuggging information. (yes, that's spelled exactly like that in the original, and no, i'm not touching it. leaving it alone out of respect. π)-hβ Show this help message.
π EXIT STATUS π
On success, returns zero. On failure, returns non-zero. that's it. that's the tea. π
π§ ENVIRONMENT VARIABLES π§
if the cctools are installed in a non-system directory, such as your home directory, then you must set the PYTHONPATH environment so that the workqueue python module can be found. for example:
% setenv PYTHONPATH $HOME/cctools/lib/python2.4/site-packages
don't skip this bestie, she will NOT find her module and you will be sad. π
π₯ EXAMPLES π₯
to run a replica exchange experiment with 84 replicas in the temperature range 278 to 400K using the sample input files:
% replica_exchange ww_exteq_nowater1.pdb ww_exteq_nowater1.psf par_all27_prot_lipid.inp 278 400 84
to run a replica exchange experiment, with project name ReplExch, over 250 Monte Carlo steps running 1000 molecular dynamics steps and involving 84 replicas in the temperature range 278 to 400K using the sample input files:
% replica_exchange -N ReplExch -m 250 -s 1000 ww_exteq_nowater1.pdb ww_exteq_nowater1.psf par_all27_prot_lipid.inp 278 400 84
π yes, the second example uses-Nwhile the option list says-n. that's just how it is in the original, so i'm keeping it exactly as-is. no notes. π
π COPYRIGHT π
The Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. This software is distributed under the GNU General Public License. See the file COPYING for details.
π SEE ALSO π
- Cooperative Computing Tools Documentation
- Work Queue User Manual
work_queue_worker(1)work_queue_status(1)work_queue_factory(1)condor_submit_workers(1)sge_submit_workers(1)torque_submit_workers(1)
and that's the whole page, bestie! π this edition is from CCTools 8.0.0 DEVELOPMENT β that's the version stamped on the page, dated right there on the original footer alongside replica_exchange(1). slay, go run some simulations, and remember: no cap, the facts stay exactly the same even when the vibe is immaculate. periodt. β¨π
π¦
π¦ where this page comes from
- debian bookworm: coop-computing-tools 9.9-2+b4 Β· GPL-2.0-only
- ubuntu jammy: coop-computing-tools 9.9-2ubuntu3 Β· GPL-2.0-only
- ubuntu noble: coop-computing-tools 9.9-4ubuntu4 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms