MSVAR @ BioHPC

MSVAR (version 1.3) is a Markov Chain Monte Carlo (MCMC) simulation program by Mark A. Beaumont, designed to explore the most probable demographic and genealogical histories consistent with a sample of chromosomes typed at one or more loci. Author's description of the program is available here. For references and more information, see the following page.

You will need to specify how many independent MSVAR tasks you want to run through a single click of "Submit" button (suggested number of tasks is 11 or less). You will then need to upload a zip archive file containing the infile, init_v_file, and INTFILE for each of those tasks. The files within the archive should be called infile.1, init_v_file.1, INTFILE.1, infile.2, init_v_file.2, INTFILE.2, infile.3, init_v_file.3, INTFILE.3,and so on. The zip archive must be created in such a way that when it is unpacked, all files are located in the "current directory" (i.e., the zip file must not contain any subdirectories). The tasks will be run independently. Results from each task will be placed in a separate directory and packed together into a zip archive, available for htpp and ftp download via a link in a notification e-mail. For best efficiency of compute node utilization, the tasks should be of similar length. The number of processors the job will run on will be adjusted automatically and can be lowered by the user.

Calculations will be carried out on the BioHPC compute cluster at CBSU. You will receive e-mail notifications when the job is submitted, when it starts, and when it is finished. Output will be available via links embedded in the notification e-mails. For more information about this program and BioHPC interface in general, please visit our Frequently Asked Questions page.

E-mail:
(only guests need to use this field, registered users should log in)

Job name: (will be set based on the name of input zip file)

Number of tasks

Upload your input file (*.zip)

Maximum number of processors to use
(lowering the number of processors may allow the job to start sooner, but it will increase the time of the calculation)

Cluster: ( Show timeout info )