<div dir="ltr">Thanks Andy. <div><br></div><div>1) Just to confirm. Are you able to load this file into IGV from URL?</div><div><br></div><div><a href="ftp://ftp.ensembl.org/pub/release-75/data_files/homo_sapiens/GRCh37/rnaseq/GRCh37.HumanBodyMap.brain.1.bam">ftp://ftp.ensembl.org/pub/release-75/data_files/homo_sapiens/GRCh37/rnaseq/GRCh37.HumanBodyMap.brain.1.bam</a><br>
</div><div><br></div><div>If yes, do you paste this link as ftp:// or http:// in the URL box?</div><div><br></div><div>2) When you mentioned 'I've tried sorting on a local GTF file but to little success without it taking up a lot of RAM', you actually were not able to sort the file as opposed to having sorted it and not been able to load it into IGV. Am I right? How much memory are you using with IGV?</div>
<div><br></div><div>Thanks,</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 8 March 2014 11:48, Andy Yates <span dir="ltr"><<a href="mailto:ayates@ebi.ac.uk" target="_blank">ayates@ebi.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Apologies from my initial reading of their docs it seemed that there was no support for FTP. I have been able to load our BAMs into a local IGV instance so I don't think there is a problem here. It was probably related to our FTP issues yesterday.<br>
<br>
As for loading the models I've tried sorting on a local GTF file but to little success without it taking up a lot of RAM. So at the moment I would suggest using the DAS track for the gene annotations & using the flat files for the RNA-seq data. If we can manage to make something better we will let you know.<br>
<span class="HOEnZb"><font color="#888888"><br>
Andy<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 7 Mar 2014, at 11:20, Genomeo Dev <<a href="mailto:genomeodev@gmail.com">genomeodev@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> There are other things in Ensembl which I want to use inside igv, not just the annotations such as RNAseq and Epigenetic data, hence I have been looking at loading from URL. Well, based on this IGV documentation, IGV also accepts ftp:<br>
><br>
> Load from URL<br>
><br>
> To load data from an HTTP URL:<br>
><br>
> • Select File>Load from URL.<br>
> • Enter the HTTP or FTP URL for a data file or sample information file, then click OK.<br>
> <a href="http://www.broadinstitute.org/igv/loaddata" target="_blank">http://www.broadinstitute.org/igv/loaddata</a><br>
><br>
> For the other question, would it be safe for me to do the gtf to bigBed conversion myself?<br>
><br>
> G.<br>
><br>
> On 7 March 2014 09:11, Andy Yates <<a href="mailto:ayates@ebi.ac.uk">ayates@ebi.ac.uk</a>> wrote:<br>
> Hi Genomeo<br>
><br>
> So firstly looking at the information at igv it can only render tracks hosted on http. Those files are on FTP only. Without locally downloading it you won't be able to visualise. We are looking into making this available on http but I cannot give any firm timelines.<br>
><br>
> Secondly I did manage to load the gtf in igv (did it about 2 weeks ago) but it took 4gb and ages to load. Like cup of coffee timescales but it did work in the end. The solution here would be to use an alternative format such as bigBed. We don't make the genes available in that format at the moment but I am working towards making this happen. We recognise how important this is with so many new browsers now available we need yo make it easier to access Ensembl data and in particular the gene sets.<br>
><br>
> As an alternative you could always download bed from the rest api's region endpoint (<a href="http://beta.rest.ensembl.org/documentation/info/feature_region" target="_blank">http://beta.rest.ensembl.org/documentation/info/feature_region</a>) so long as you can work in smaller regions (5mb). Or you could attach the Ensembl das source which igv says it can understand. There's info from <a href="http://www.ensembl.org/info/data/ensembl_das.html" target="_blank">http://www.ensembl.org/info/data/ensembl_das.html</a><br>
><br>
> Hope this helps a little<br>
><br>
> Andy<br>
><br>
> Sent from my tablet<br>
><br>
> On 6 Mar 2014, at 18:13, Genomeo Dev <<a href="mailto:genomeodev@gmail.com">genomeodev@gmail.com</a>> wrote:<br>
><br>
>> Hi,<br>
>><br>
>> (1)<br>
>><br>
>> I am trying to use IGV browser to load bam files form this location:<br>
>><br>
>> <a href="ftp://ftp.ensembl.org/pub/release-75/data_files/homo_sapiens/GRCh37/rnaseq/" target="_blank">ftp://ftp.ensembl.org/pub/release-75/data_files/homo_sapiens/GRCh37/rnaseq/</a><br>
>><br>
>> But I am getting an error message that not possible to establish SOCKS proxy connection.<br>
>><br>
>> I have found that igv mention that 'for .bam, .tdf, and indexed file formats the server must support byte-range requests.' (<a href="http://www.broadinstitute.org/igv/loaddata" target="_blank">http://www.broadinstitute.org/igv/loaddata</a>)<br>
>><br>
>> I was wondering whether there is any thing from the ensembl server side that is causing this error.<br>
>><br>
>> Thanks.<br>
>><br>
>> (2)<br>
>><br>
>> I want to load annotation into IGV genome browser from <a href="ftp://ftp.ensembl.org/pub/release-75/gtf/homo_sapiens/Homo_sapiens.GRCh37.75.gtf.gz" target="_blank">ftp://ftp.ensembl.org/pub/release-75/gtf/homo_sapiens/Homo_sapiens.GRCh37.75.gtf.gz</a><br>
>><br>
>> But the file is too large to handle at once. Any advice from the Ensembl browser team on how I should be conducting this operation?<br>
>><br>
>> Thanks,<br>
>><br>
>> --<br>
>> G.<br>
>> _______________________________________________<br>
>> Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>
>> Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" target="_blank">http://lists.ensembl.org/mailman/listinfo/dev</a><br>
>> Ensembl Blog: <a href="http://www.ensembl.info/" target="_blank">http://www.ensembl.info/</a><br>
><br>
> _______________________________________________<br>
> Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>
> Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" target="_blank">http://lists.ensembl.org/mailman/listinfo/dev</a><br>
> Ensembl Blog: <a href="http://www.ensembl.info/" target="_blank">http://www.ensembl.info/</a><br>
><br>
><br>
><br>
><br>
> --<br>
> G.<br>
> _______________________________________________<br>
> Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>
> Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" target="_blank">http://lists.ensembl.org/mailman/listinfo/dev</a><br>
> Ensembl Blog: <a href="http://www.ensembl.info/" target="_blank">http://www.ensembl.info/</a><br>
<br>
<br>
_______________________________________________<br>
Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>
Posting guidelines and subscribe/unsubscribe info: <a href="http://lists.ensembl.org/mailman/listinfo/dev" target="_blank">http://lists.ensembl.org/mailman/listinfo/dev</a><br>
Ensembl Blog: <a href="http://www.ensembl.info/" target="_blank">http://www.ensembl.info/</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">G.</div>
</div>