Arun Ahuja

Results 62 comments of Arun Ahuja

Perhaps related, but after the redeployment and submitting a run I see: ``` File "/home/cycledash/cycledash/venv/lib/python2.7/site-packages/requests/adapters.py", line 375, in send raise ConnectionError(e, request=request) ConnectionError: HTTPConnectionPool(host='demeter.hpc.mssm.edu', port=14000): Max retries exceeded with url:...

Some near-term ways to address this might be: - allow an RNA BAM to be specified on run submission - allow a third BAM (the RNA BAM) to be displayed...

Yes, you can submit any number of BAMs, but you can't submit a run with multiple tumor BAMs: ![image](https://cloud.githubusercontent.com/assets/455755/10398899/8a95689a-6e7d-11e5-9984-e1d88b2b58fb.png) But assuming the "multiple BAMs in a pileup" feature allows you...

Also "true positive" issue caught in the act

The gene_names were there before I refreshed to the latest deploy, this was submitted before the update.

So I did have them in the new deploy in another tab, refreshed that tab and now they are gone.

And now back: ![image](https://cloud.githubusercontent.com/assets/455755/8172906/e75eb9e0-1393-11e5-8ae1-264a0e483776.png)

...and now gone: http://cycledash.demeter.hpc.mssm.edu/runs/327/examine?query=sample_name+%3D+TUMOR+ORDER+BY+contig%2C+position

Verifying I'm not crazy: ![image](https://cloud.githubusercontent.com/assets/455755/8172955/9cfca56e-1394-11e5-847c-3486e24a82f1.png) ![image](https://cloud.githubusercontent.com/assets/455755/8172957/a41134f0-1394-11e5-8b71-47048a09779c.png)

On this IGV also allows you to jump to a gene: ![image](https://cloud.githubusercontent.com/assets/455755/6378035/647efc04-bcf6-11e4-85e9-dd084db7fa43.png)