<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Duarte,<br>
<br>
The API still relies on the information being in the database.<br>
For GRCh38, we have stored entries in the seq_region_synonym table
for 'chr22' and the like.<br>
For GRCh37, these entries are not stored, hence the API does not
know what chr22 means.<br>
<br>
I suggest using real chromosome names :-)<br>
<br>
<br>
Regards,<br>
Magali<br>
<br>
<div class="moz-cite-prefix">On 24/03/2016 10:49, Duarte Molha
wrote:<br>
</div>
<blockquote
cite="mid:CAGqkoELumr0Bp0_1vs+H7rtuoCT0-4T1W0RALd2gwNdeZ-3Gsw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi Devs</div>
<div><br>
</div>
<div>I was just wondering why a strange behavior is different
between the GRCH37 database and GRCh38 using the same API</div>
<div><br>
</div>
<div>I am currently using APIv83 and when I connect to my local
GRCh37 database, the method:</div>
<div><br>
</div>
<div>
<div>my $slice_targeted = $slice_adaptor->fetch_by_region(
'chromosome', $chr, $start, $end, $strand);</div>
</div>
<div><br>
</div>
<div>fails if $chr contains the prefix "chr" like in chr22</div>
<div>but it works fine against my also local GRCh38 database</div>
<div><br>
</div>
<div>since they are both using the same api should the behavior
not be the same?</div>
<div><br>
</div>
<div>Best regards</div>
<div><br>
</div>
<div>Duarte<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Dev@ensembl.org">Dev@ensembl.org</a>
Posting guidelines and subscribe/unsubscribe info: <a class="moz-txt-link-freetext" href="http://lists.ensembl.org/mailman/listinfo/dev">http://lists.ensembl.org/mailman/listinfo/dev</a>
Ensembl Blog: <a class="moz-txt-link-freetext" href="http://www.ensembl.info/">http://www.ensembl.info/</a>
</pre>
</blockquote>
<br>
</body>
</html>