Cipres Web Portal

---

RAxML 7.0.4 on ABE

RAxML on ABE provides a familiar RAxML interface, but submits to ABE, a large NSF Teragrid Resource, rather than the CIPRES cluster. The ABE resource will run your RAxML job, and return the results just like the original RAxML interface.

Advantages: RAxML on ABE can handle larger job runs than our original RAxML interface. The ABE machine allows your job to run for up to 7 days / 168 hours. The interface will run the job using parallel RAxML, so run speed is 3 - 4.5 times faster than the CIPRES cluster. In other words, the computation may be equivalent to 21 - 28 days on the (sequential) CIPRES Cluster.

Disadvantages:The queue times on Teragrid resources vary according to traffic and according to the size of your job (shorter jobs typically have shorter queue waits). Sometimes TeraGrid resources go down for preventative maintenance or due to unforeseen circumstances. At present, this will cause your job to fail, and you will have to restart it. There is no restart capability at present.

Click this icon to check the traffic on TeraGrid:
Click this icon to check the Teragrid maintenance schedule:

How to use it: The interface for RAxML on ABE differs from the original interface by presenting a form that requires the user to enter a maximum wall clock time for each job. This will determine the job priority in the queue, help identify the number of processors required, and set a time for job termination (whether the run is finished or not). If you set a value of 0.5 hr or less, your job will run in a testing queue, which generally has a much shorter wait time than the production queue.

Should you use it? If you have jobs that run more than two days on the CIPRES cluster, you should definitely try to use RAxML on ABE.

Known Issues: None known.

If there is a tool or a feature you need, let us know.