Slide 1

Slide 1 text

Running FALCON-Unzip Example on AWS Jun 1, 2016 Jason Chin

Slide 2

Slide 2 text

Perquisites • An AWS EC2 account • An SSH keypair (http://docs.aws.amazon.com/AWSEC2/latest/User Guide/ec2-key-pairs.html#having-ec2-create-your- key-pair)

Slide 3

Slide 3 text

Go to the “instance tab” to “Lunch Instance” Data, code and an example of the results are in snapshot snap-d555eba7 (set up for r3.8xlarge instance)

Slide 4

Slide 4 text

Choose Ubuntu 14.04 LTS AMI

Slide 5

Slide 5 text

Choose rx.8xlarge for 244G ram ( we can run 32 / 4 = 8 daligner jobs at the same time, each can take up to 24G RAM)

Slide 6

Slide 6 text

Use “us-east-1a” availability zone

Slide 7

Slide 7 text

Add the snapshot snap-d555eba7 and attached to device /dev/sdd and set the size to 250Gb

Slide 8

Slide 8 text

You can ignore the warning and use the default here.

Slide 9

Slide 9 text

Review everything

Slide 10

Slide 10 text

Click the “Lunch” button in the bottom of the lunch review page, AWS will ask which SSH key pair. I had an existing one called “starcluster”. Yours will be different, pick one.

Slide 11

Slide 11 text

Go back to the instance tab. If the instance starts up successfully, you will see “running” status associated with the instance. Right click, you will get a pop-up menu. Click “connect” to get the hostname for connection.

Slide 12

Slide 12 text

On a local terminal, ssh into the instances following AWS’s instruction. After you login, the vanilla Ubuntu box needs some quick configuration. We need to: (1) Mount a new EBS volume generated based on the snapshot that has the data to /EBS (2) It is best to use the instance’s SSD for processing the data. We need to format the storage. (3) Copy configuration and run the assembly.

Slide 13

Slide 13 text

(1) Mount a new EBS volume generated based on the snapshot that has the data to /EBS with the following commands: mkdir /EBS mount /dev/xvdd1 /EBS (2) It is best to use the instance’s SSD for processing the data. We need to format the storage by running `fdisk /dev/xvdb` interactively. Here is an example. What you need to input is highlighted. Input “n” Input “p” Use default, or input “1” Use default Use default Input “w”

Slide 14

Slide 14 text

We still need to format and mount the new partition, here are the commands mkfs.ext4 /dev/xvdb1 mkdir /test_run/ mount /dev/xvdb1 /test_run Now you can change directory to /test_run to use the SSD and do a test assembly run, Here is an example cd /test_run/ cp /EBS/FALCON_asm_example_template/* . bash run_example.sh & It takes about 7 to 8 hours which might cost about $25 for the CPU hours used. The created EBS volume also costs some thing. You can delete it one the run is finished. The assembly results in SSD will be destroyed one the instance is terminated. You should terminated the instance once the assembly is done. If you want to keep the assembly results, you need to copy it out. The I/O from the snapshot is slow initially. (see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html) A previous run example is inside `/EBS/FALCON_asm_example/`. The final Quvier primary contigs and associated haplotigs are in `/EBS/FALCON_asm_example/4- quiver/cns_output/`

Slide 15

Slide 15 text

CPU Load Time Course

Slide 16

Slide 16 text

All System Monitoring Time Course

Slide 17

Slide 17 text

General Disk Usage (including all intermediate data files) and the results in 4-quiver/cns_output/

Slide 18

Slide 18 text

Terminate the instance Delete the associated EBS volume