[ensembl-dev] Dev Digest, Vol 23, Issue 4
陈岗
danielchen06 at gmail.com
Wed May 2 14:06:11 BST 2012
Hi Beth
You're right, the files on ftp server are correct, I lost
file translation_attrib.txt.gz by myself, downloading it right now.
It's my fault, sorry
Best Regards.
2012/5/2 <dev-request at ensembl.org>
> Send Dev mailing list submissions to
> dev at ensembl.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.ensembl.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
> dev-request at ensembl.org
>
> You can reach the person managing the list at
> dev-owner at ensembl.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Error - $parms->add_config() has failed: Invalid command
> 'CustomLog' (Asela Dassanayake)
> 2. Re: two LastZ.pms (Kathryn Beal)
> 3. Re: caenorhabditis_elegans_core_66_220 import error (Karyn Megy)
> 4. Re: caenorhabditis_elegans_core_66_220 import error (Beth Yates)
> 5. Question regarding the varian_effect_predictor VCF support
> for multiple samples (Duarte Molha)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 2 May 2012 17:56:44 +1200
> From: Asela Dassanayake <aseladassanayake at gmail.com>
> Subject: Re: [ensembl-dev] Error - $parms->add_config() has failed:
> Invalid command 'CustomLog'
> To: Ensembl developers list <dev at ensembl.org>
> Message-ID:
> <CAA+8yz__+bDzMvhV5byU4gkUMV1ZmOVeNCB+UuEZ6nWLUGS2jQ at mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Dan,
>
> Thank you for your reply. As you suspected it was a Apache Module error. I
> fixed it by loading various modules and then I was able to kick start the
> ensembl server. I will post the list of apache modules required for the
> benefit of others.
>
> Thanks
> Asela
>
> On Tue, May 1, 2012 at 9:08 PM, Dan Sheppard <ds23 at sanger.ac.uk> wrote:
>
> > Hi Asela,
> >
> > I've not seen this in EnsEMBL before but this kind of apache error is
> most
> > often caused by running the wrong version or one compiled with incorrect
> > modules.
> >
> > Could you send the output of these two commands?
> >
> > httpd -V
> > httpd -l
> >
> > In your case, it looks like mod_log_config may be missing, but that
> > doesn't mean it's right just to add it in as there must be a deeper
> reason
> > why it's not there for you which will probably come back to bite you.
> >
> > Alternatively, if you check you followed the instructions here,
> >
> >
> http://www.ensembl.org/info/**docs/webcode/install/non-**ensembl-code.html
> <http://www.ensembl.org/info/docs/webcode/install/non-ensembl-code.html>
> >
> > that usually fixes this kind of error.
> >
> > Thanks,
> > Dan.
> >
> >
> > Syntax error on line 55 of /media/Data/cvs.bin/conf/**httpd.conf:
> >>
> >> $parms->add_config() has failed: Invalid command 'CustomLog', perhaps
> >>
> >> misspelled or defined by a module not included in the server
> configuration
> >>
> >
> > ______________________________**_________________
> > Dev mailing list Dev at ensembl.org
> > List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/**
> > mailman/listinfo/dev <http://lists.ensembl.org/mailman/listinfo/dev>
> > Ensembl Blog: http://www.ensembl.info/
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.ensembl.org/pipermail/dev/attachments/20120502/9d6360a5/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 2 May 2012 09:48:55 +0100
> From: Kathryn Beal <kbeal at ebi.ac.uk>
> Subject: Re: [ensembl-dev] two LastZ.pms
> To: Ensembl developers list <dev at ensembl.org>
> Message-ID: <E4320748-266F-4B64-B0D8-64982E2A669A at ebi.ac.uk>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Sharon,
> We have replaced all the compara pipelines to use the new init_pipeline.plsystem. In the process, there were major modifications to many of the
> associated modules. All the modules associated with the new pipelines can
> be found in Bio::EnsEMBL::Compara::RunnableDB. I have just removed all the
> modules in Bio::EnsEMBL::Compara::Production::GenomicAlignBlock as these
> have either replacements or are no longer supported. This has affected HEAD
> but was done after the up-coming ensembl 67 branch.
>
> Thank you for pointing out the problem with the lastz.conf file. I have
> corrected it so that both modules refer to
> 'Bio::EnsEMBL::Compara::RunnableDB::PairAligner::LastZ'.
>
> { TYPE => PAIR_ALIGNER,
> 'method_link' => [1001, 'LASTZ_RAW'],
> 'analysis_template' => {
> '-program' => 'lastz',
> '-parameters' => "{method_link=>'LASTZ_RAW',options=>'T=1 L=3000
> H=2200 O=400 E=30'}",
> '-module' =>
> 'Bio::EnsEMBL::Compara::RunnableDB::PairAligner::LastZ',
> },
> 'non_reference_collection_name' => 'mouse all',
> 'reference_collection_name' => 'human all',
> },
>
> { TYPE => PAIR_ALIGNER,
> 'method_link' => [1001, 'LASTZ_RAW'],
> 'analysis_template' => {
> '-program' => 'lastz',
> '-parameters' => "{method_link=>'LASTZ_RAW',options=>'T=1 L=3000
> H=2200 O=400 E=30'}",
> '-module' =>
> 'Bio::EnsEMBL::Compara::RunnableDB::PairAligner::LastZ',
> },
> 'non_reference_collection_name' => 'rat all',
> 'reference_collection_name' => 'human all',
> },
>
> Cheers
> Kathryn
>
>
> > Hi Ensembl Compara Developers,
> >
> > I just find there are two LastZ.pm in the ensembl-compara package
> (v66). They were both used in the example configuration files
> > ensembl-compara/modules/Bio/EnsEMBL/Compara/PipeConfig/Example/lastz.conf
> >
> > { TYPE => PAIR_ALIGNER,
> > 'method_link' => [1001, 'LASTZ_RAW'],
> > 'analysis_template' => {
> > '-program' => 'lastz',
> > '-parameters' => "{method_link=>'LASTZ_RAW',options=>'T=1
> L=3000 H=2200 O=400 E=30'}",
> > '-module' =>
> 'Bio::EnsEMBL::Compara::Production::GenomicAlignBlock::LastZ',
> > },
> > 'non_reference_collection_name' => 'mouse all',
> > 'reference_collection_name' => 'human all',
> > },
> >
> > { TYPE => PAIR_ALIGNER,
> > 'method_link' => [1001, 'LASTZ_RAW'],
> > 'analysis_template' => {
> > '-program' => 'lastz',
> > '-parameters' => "{method_link=>'LASTZ_RAW',options=>'T=1
> L=3000 H=2200 O=400 E=30'}",
> > '-module' =>
> 'Bio::EnsEMBL::Compara::RunnableDB::PairAligner::LastZ',
> > },
> > 'non_reference_collection_name' => 'rat all',
> > 'reference_collection_name' => 'human all',
> > },
> >
> >
> > I am wondering what are the differences between these two LastZ.pm
> modules, if they were created for difference uses, when to use which.
> >
> > Thanks,
> >
> >
> > Sharon
> >
> > On Apr 25, 2012, at 4:24 AM, Javier Herrero wrote:
> >
> > Dear Alison
> >
> > The branch lengths are based on a mixture of an estimation based on 4D
> sites and an estimation based on million years since the divergence of two
> species (the data are taken from www.timetree.org<http://www.timetree.org/
> >).
> >
> > At UCSC and Ensembl, we have agreed to use the same species tree for the
> alignments. However, we do not work exactly with the same set of species.
> You can find more information here:
> http://genomewiki.ucsc.edu/index.php/Human/hg19/GRCh37_46-way_multiple_alignment#4D_sites_branch_length_calculations
> >
> > Additional species are included in the middle of an existing branch. An
> initial estimation of the branch lengths is based on the million years
> since the divergence of two species, the data being taken from
> www.timetree.org<http://www.timetree.org/>.
> >
> > I hope this helps
> >
> > Javier
> >
> > On 24/04/12 17:23, Alison Wright wrote:
> >
> > Hi,
> >
> > I have accessed the Ensembl Species Tree generated for use in
> Phylowidget by the Compara team (which includes all the current species for
> the main Ensembl website, plus a few additional mammalian species of
> interest).
> >
> > However, I cant find out what the branch lengths represent (number of
> substitutions per site? PAM units?) and how they were calculated?
> >
> > Thanks very much for any help.
> >
> > Alison Wright
> >
> >
> >
> >
> >
> > _______________________________________________
> > Dev mailing list Dev at ensembl.org<mailto:Dev at ensembl.org>
> > List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> > Ensembl Blog: http://www.ensembl.info/
> >
> >
> >
> > --
> > Javier Herrero, PhD
> > Ensembl Coordinator and Ensembl Compara Project Leader
> > European Bioinformatics Institute (EMBL-EBI)
> > Wellcome Trust Genome Campus, Hinxton
> > Cambridge - CB10 1SD - UK
> >
> > _______________________________________________
> > Dev mailing list Dev at ensembl.org<mailto:Dev at ensembl.org>
> > List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> > Ensembl Blog: http://www.ensembl.info/
> >
> >
> > _______________________________________________
> > Dev mailing list Dev at ensembl.org
> > List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> > Ensembl Blog: http://www.ensembl.info/
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 2 May 2012 10:00:29 +0100
> From: Karyn Megy <kmegy at ebi.ac.uk>
> Subject: Re: [ensembl-dev] caenorhabditis_elegans_core_66_220 import
> error
> To: Ensembl developers list <dev at ensembl.org>
> Message-ID: <83245ECC-7DC7-4881-BCAC-B2CCC1BFF8EC at ebi.ac.uk>
> Content-Type: text/plain; charset=GB2312
>
> Dear Gang Chen,
>
> Where did you get that file from?
>
> If you download it from the EnsemblGenomes FTP site, you have everything
> required:
>
> ftp://ftp.ensemblgenomes.org/pub/metazoa/release-13/mysql/caenorhabditis_elegans_core_13_66_220/
>
> Best regards,
> Karyn.
>
>
>
> On 2 May 2012, at 04:24, ?? wrote:
>
> > Hi All
> >
> > I found caenorhabditis_elegans_core_66_220 has import error, about table
> translation_attrib doesn't exist.
> >
> > Could you re-export the database?
> >
> > Thank you
> >
> > --
> > Gang Chen
> > TILSI
> > Taicang Institute For Life Science Information
> > Address: A2/162, Renmin South Road, Taicang, 215400, Jiangsu Province,
> P.R.China
> > Phone:?+86?512-82782588
> >
> > _______________________________________________
> > Dev mailing list Dev at ensembl.org
> > List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> > Ensembl Blog: http://www.ensembl.info/
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 02 May 2012 10:09:47 +0100
> From: Beth Yates <bp1 at sanger.ac.uk>
> Subject: Re: [ensembl-dev] caenorhabditis_elegans_core_66_220 import
> error
> To: Ensembl developers list <dev at ensembl.org>
> Message-ID: <4FA0F9DB.5000703 at sanger.ac.uk>
> Content-Type: text/plain; charset=GB2312
>
> Hi Gang Chen,
>
> I'm also not sure why you are experiencing a problem as this file is
> also present on the main ensembl FTP site:
>
> ftp://ftp.ensembl.org/pub/release-66/mysql/caenorhabditis_elegans_core_66_220/translation_attrib.txt.gz
> and the table sql is defined correctly in the sql definition file
>
> ftp://ftp.ensembl.org/pub/release-66/mysql/caenorhabditis_elegans_core_66_220/caenorhabditis_elegans_core_66_220.sql.gz
>
> Can you give us any more information to help us diagnose this problem?
>
> Best regards,
> Beth
>
> On 02/05/12 10:00, Karyn Megy wrote:
> > Dear Gang Chen,
> >
> > Where did you get that file from?
> >
> > If you download it from the EnsemblGenomes FTP site, you have everything
> required:
> >
> ftp://ftp.ensemblgenomes.org/pub/metazoa/release-13/mysql/caenorhabditis_elegans_core_13_66_220/
> >
> > Best regards,
> > Karyn.
> >
> >
> >
> > On 2 May 2012, at 04:24, ?? wrote:
> >
> >> Hi All
> >>
> >> I found caenorhabditis_elegans_core_66_220 has import error, about
> table translation_attrib doesn't exist.
> >>
> >> Could you re-export the database?
> >>
> >> Thank you
> >>
> >> --
> >> Gang Chen
> >> TILSI
> >> Taicang Institute For Life Science Information
> >> Address: A2/162, Renmin South Road, Taicang, 215400, Jiangsu Province,
> P.R.China
> >> Phone:?+86?512-82782588
> >>
> >> _______________________________________________
> >> Dev mailing list Dev at ensembl.org
> >> List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> >> Ensembl Blog: http://www.ensembl.info/
> >
> > _______________________________________________
> > Dev mailing list Dev at ensembl.org
> > List admin (including subscribe/unsubscribe):
> http://lists.ensembl.org/mailman/listinfo/dev
> > Ensembl Blog: http://www.ensembl.info/
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 2 May 2012 10:18:38 +0000
> From: Duarte Molha <Duarte.Molha at ogt.co.uk>
> Subject: [ensembl-dev] Question regarding the varian_effect_predictor
> VCF support for multiple samples
> To: "dev at ensembl.org" <dev at ensembl.org>
> Message-ID:
> <
> 9716146486D5534884847D0B9938BA9C0C85FDEF at ExchangeServer.internal.ogtip.com
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> Dear Developers
>
> I have been playing around with the latest version of the VEP and I would
> like to congratulate you for the many nice features you have been able to
> include.
> I particularly like the new plug-in feature support. This will allow me to
> develop new features into my analysis pipeline without having to hack your
> code to much :).
>
> There is however a very important features I would love to be included in
> your VEP - VCF with multiple sample support.
>
> I had to change a lot of your code in a previous version of VEP in order
> to get some sort of support for this and it becomes very complicated to be
> able to merge what I have done with your earlier version of VEP into the
> new versions because the code is evolving very fast.
>
> I noticed that you say that you now support all fields on a VCF. Does this
> mean that your script is reading in the sample fields but disregards them
> for the analysis?
> It would be great if the VEP could do the analysis of each variant and for
> each allelic substitution it could include the sample information for wish
> it is relevant.
>
> Here is an example of what your code outputs and what would I think would
> be very usefull to have it do:
>
> Input VCF entry:
> #CHROM POS ID REF ALT QUAL
> FILTER INFO FORMAT sample_01 sample_02
> sample_03
> 1 50311454 . G A
> 5322.41 PASS
> AC=3;AF=0.500;AN=6;BaseQRankSum=5.991;DP=271;Dels=0.00;FS=3.551;HRun=0;HaplotypeScore=2.6095;MQ=59.14;MQ0=0;MQRankSum=0.759;QD=28.46;ReadPosRankSum=-0.332;SB=-2325.79;SF=0,1,2
> GT:AD:DP:GQ:PL 1/1:0,40:40:99:1456,114,0
> 0/0:37,0:37:99:0,102,1245 0/1:23,26:49:99:839,0,617
>
> Current OUTPUT:
>
> #Uploaded_variatio
>
> Location
>
> Allele
>
> Gene
>
> Feature
>
> Feature_type
>
> Consequence
>
> cDNA_position
>
> CDS_position
>
> Protein_position
>
> Amino_acids
>
> Codons
>
> Existing_variation
>
> Extra
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> ENSG00000186094
>
> ENST00000371839
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360905;HGVSc=ENST00000371839.1:c.157+5614C>T;INTRON=2/13
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> ENSG00000215887
>
> ENST00000502859
>
> Transcript
>
> WITHIN_NON_CODING_GENE
>
> 1348
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> HGVSc=ENST00000502859.1:1348G>A;EXON=3/3
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> ENSG00000186094
>
> ENST00000411952
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000411423;HGVSc=ENST00000411952.2:c.139+5614C>T;INTRON=2/14
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> ENSG00000186094
>
> ENST00000497451
>
> Transcript
>
> WITHIN_NON_CODING_GENE,INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> HGVSc=ENST00000497451.1:123+5614C>T;INTRON=1/2
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> ENSG00000186094
>
> ENST00000371838
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360904;HGVSc=ENST00000371838.1:c.157+5614C>T;INTRON=2/8
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> ENSG00000186094
>
> ENST00000371836
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360902;HGVSc=ENST00000371836.1:c.157+5614C>T;INTRON=2/6
>
>
>
> Same output but containing sample information for non-reference samples:
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_01
>
> GT:AD:DP:GQ:PL
>
> 1/1:0,40:40:99:1456,114,0
>
> ENSG00000186094
>
> ENST00000371839
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360905;HGVSc=ENST00000371839.1:c.157+5614C>T;INTRON=2/13
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_01
>
> GT:AD:DP:GQ:PL
>
> 1/1:0,40:40:99:1456,114,0
>
> ENSG00000215887
>
> ENST00000502859
>
> Transcript
>
> WITHIN_NON_CODING_GENE
>
> 1348
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> HGVSc=ENST00000502859.1:1348G>A;EXON=3/3
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_01
>
> GT:AD:DP:GQ:PL
>
> 1/1:0,40:40:99:1456,114,0
>
> ENSG00000186094
>
> ENST00000411952
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000411423;HGVSc=ENST00000411952.2:c.139+5614C>T;INTRON=2/14
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_01
>
> GT:AD:DP:GQ:PL
>
> 1/1:0,40:40:99:1456,114,0
>
> ENSG00000186094
>
> ENST00000497451
>
> Transcript
>
> WITHIN_NON_CODING_GENE,INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> HGVSc=ENST00000497451.1:123+5614C>T;INTRON=1/2
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_01
>
> GT:AD:DP:GQ:PL
>
> 1/1:0,40:40:99:1456,114,0
>
> ENSG00000186094
>
> ENST00000371838
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360904;HGVSc=ENST00000371838.1:c.157+5614C>T;INTRON=2/8
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_01
>
> GT:AD:DP:GQ:PL
>
> 1/1:0,40:40:99:1456,114,0
>
> ENSG00000186094
>
> ENST00000371836
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360902;HGVSc=ENST00000371836.1:c.157+5614C>T;INTRON=2/6
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_03
>
> GT:AD:DP:GQ:PL
>
> 0/1:23,26:49:99:839,0,617
>
> ENSG00000186094
>
> ENST00000371839
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360905;HGVSc=ENST00000371839.1:c.157+5614C>T;INTRON=2/13
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_03
>
> GT:AD:DP:GQ:PL
>
> 0/1:23,26:49:99:839,0,617
>
> ENSG00000215887
>
> ENST00000502859
>
> Transcript
>
> WITHIN_NON_CODING_GENE
>
> 1348
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> HGVSc=ENST00000502859.1:1348G>A;EXON=3/3
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_03
>
> GT:AD:DP:GQ:PL
>
> 0/1:23,26:49:99:839,0,617
>
> ENSG00000186094
>
> ENST00000411952
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000411423;HGVSc=ENST00000411952.2:c.139+5614C>T;INTRON=2/14
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_03
>
> GT:AD:DP:GQ:PL
>
> 0/1:23,26:49:99:839,0,617
>
> ENSG00000186094
>
> ENST00000497451
>
> Transcript
>
> WITHIN_NON_CODING_GENE,INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> HGVSc=ENST00000497451.1:123+5614C>T;INTRON=1/2
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_03
>
> GT:AD:DP:GQ:PL
>
> 0/1:23,26:49:99:839,0,617
>
> ENSG00000186094
>
> ENST00000371838
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360904;HGVSc=ENST00000371838.1:c.157+5614C>T;INTRON=2/8
>
> 1_50311454_G/A
>
> 1:50311454
>
> A
>
> Sample_03
>
> GT:AD:DP:GQ:PL
>
> 0/1:23,26:49:99:839,0,617
>
> ENSG00000186094
>
> ENST00000371836
>
> Transcript
>
> INTRONIC
>
> -
>
> -
>
> -
>
> -
>
> -
>
> rs4926833
>
> ENSP=ENSP00000360902;HGVSc=ENST00000371836.1:c.157+5614C>T;INTRON=2/6
>
>
>
> I would do this myself if there was a way for the plug-in feature to give
> be the sample information for each variant.
> Any ideas how this can be accomplished?
>
> Best regards,
>
> Duarte Molha
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.ensembl.org/pipermail/dev/attachments/20120502/1a395486/attachment.htm
> >
>
> ------------------------------
>
> _______________________________________________
> Dev mailing list
> Dev at ensembl.org
> http://lists.ensembl.org/mailman/listinfo/dev
>
>
> End of Dev Digest, Vol 23, Issue 4
> **********************************
>
--
Gang Chen
TILSI
Taicang Institute For Life Science Information
Address: A2/162, Renmin South Road, Taicang, 215400, Jiangsu Province,
P.R.China
Phone:（+86）512-82782588
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20120502/ae2a55df/attachment.html>
More information about the Dev
mailing list