Changes between Version 48 and Version 49 of InhouseMeetingQuestions


Ignore:
Timestamp:
Dec 9, 2011, 2:48:35 PM (10 years ago)
Author:
antonialock
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InhouseMeetingQuestions

    v48 v49  
    1313'''Feedback from retreat''' [[BR]]
    1414•       Genome visualization in Ensembl. A feature that allows scrolling left and right like in X-map would be useful [[BR]]
    15 •       RNA-seq data (and chip-seq). Does Ensembl support squiggly data tracks or only boxes? Comparison between species would be useful, showing conserved refions, like in UCSC. [[BR]]
    16         o Intra-species variation and SNP’s – wiggle tracks for gene diversity [[BR]]
     15•       RNA-seq data (and chip-seq). Does Ensembl support squiggly data tracks or only boxes? Comparison between species would be useful, showing conserved refions, like in UCSC.
     16        o Intra-species variation and SNP’s – wiggle tracks for gene diversity
    1717•       Multiple data-sets on tracks. Make them searchable. Show one as consensus and the others beneath. Data-sets should be searchable and suppressible. [[BR]]
    1818•       Will our data be loaded into Biogrid? Many people who do not use PomBase may use Biogrid. [[BR]]
     
    2121•       Protein modifications – show on the protein sequence. Also map out functional regions, catalytic residues.[[BR]]
    2222•       All data should be downloadable. [[BR]]
    23 •       Support a repository for alignmemts. Dan had problems with a publication once because there was nowhere where he could publically store his alignment. [[BR]]
    24         o Genome scale alignments [[BR]]
    25 •       Transcript boxes: this needs to be referenced and show what data-sets that have been used to define UTR’s etc. [[BR]]
     23•       Support a repository for alignmemts. Dan had problems with a publication once because there was nowhere where he could publically store his alignment.
     24        o Genome scale alignments
     25•       Transcript boxes: this needs to be referenced and show what data-sets that have been used to define UTR’s etc.
    2626        o Evidence codes could also be shown. [[BR]]
    2727        o If multiple alternatives the data could be shown on tracks. [[BR]]