Duke,

priority=N allow you to specify the order in the submission itself.
For example, if you lost all your tracks (power outage here?) and
had to reload them from your backup file, they would be in the order
you prefer without having to go to the configure page.  Priority 1
is displayed above priority 2, etc.

                        --b0b kuhn
                        ucsc genome biofinformatics group


On 8/4/2010 8:32 AM, Duke wrote:
>   Hi Hiram,
> 
> On 8/4/10 11:21 AM, Hiram Clawson wrote:
>> You can control the order of your tracks at the time of submission
>> by placing a priority=N variable on your track line.
>>
>> After they are loaded, go to the "configure" page and turn on
>> the option to "reorder tracks" and adjust their priorities there.
> 
> Thanks so much! I did not know this feature before. Anyway, I just went 
> directly to Congifure, enabled Re-order tracks and it works (without 
> using priority=N). So what does priority=N do?
> 
> Thanks,
> 
> D.
> 
>> --Hiram
>>
>> ----- Original Message -----
>> From: "Duke"<[email protected]>
>> To: "ra soemedi"<[email protected]>
>> Cc: [email protected]
>> Sent: Wednesday, August 4, 2010 8:16:43 AM GMT -08:00 US/Canada Pacific
>> Subject: Re: [Genome] rearrange tracks in a custom track
>>
>>    Hi Rachel,
>>
>> On 8/4/10 10:58 AM, Rachel A. Soemedi wrote:
>>> hi Duke,
>>> i had the same problem.. and then i realized they are showed in
>>> alphabetical order!! so make your track name somehow in alphabetical
>>> order, and you can put whatever description name you want that will
>>> show on the browser.
>> Thanks for your response. I thought the same thing, but unfortunately
>> the tracks do not follow exactly alphabetcical order. I mentioned that I
>> named them so that they can be close to each other, but they are
>> actually not. For example:
>>
>> IL6-uni-COV-BWA
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL6uniCOVBWA_5667>
>> IL6-uni-COV-BWA      bedGraph                4314855         chr1:
>> <../cgi-bin/hgTracks?hgsid=507&position=chr1:714000-714300&hgTracksConfigPage=notSet>
>>      
>> IL6-uni-COV-BT
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL6uniCOVBT_2937>
>> IL6-uni-COV-BT       bedGraph                5133628         chr1:
>> <../cgi-bin/hgTracks?hgsid=507&position=chr1:14400-14700&hgTracksConfigPage=notSet>
>>      
>> IL1b-uni-COV-BWA
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL1buniCOVBWA_8520>
>> IL1b-uni-COV-BWA     bedGraph                3558648         chr1:
>> <../cgi-bin/hgTracks?hgsid=507&position=chr1:714000-714300&hgTracksConfigPage=notSet>
>>      
>> IL1b-uni-COV-BT
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL1buniCOVBT_7272>
>> IL1b-uni-COV-BT      bedGraph                4274897         chr1:
>> <../cgi-bin/hgTracks?hgsid=507&position=chr1:15000-15300&hgTracksConfigPage=notSet>
>>      
>> IL61b-uni-COV-BWA
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL61buniCOVBWA_6174>
>> IL61b-uni-COV-BWA    bedGraph                5320584         chr1:
>> <../cgi-bin/hgTracks?hgsid=507&position=chr1:715500-715800&hgTracksConfigPage=notSet>
>>      
>> IL61b-uni-COV-BT
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL61buniCOVBT_9658>
>> IL61b-uni-COV-BT     bedGraph                6263206         chr1:
>> <../cgi-bin/hgTracks?hgsid=507&position=chr1:14700-15000&hgTracksConfigPage=notSet>
>>      
>> IL1b-uni-READS-BT
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL1buniREADSBT_224>
>> IL1b-uni-READS-BT    bam                             
>> IL1b-uni-READS-BWA
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL1buniREADSBWA_5934>
>> IL1b-uni-READS-BWA   bam                             
>> IL6-uni-READS-BT
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL6uniREADSBT_1329>
>> IL6-uni-READS-BT     bam                             
>> IL6-uni-READS-BWA
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL6uniREADSBWA_3537>
>> IL6-uni-READS-BWA    bam                             
>> IL61b-uni-READS-BT
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL61buniREADSBT_8237>
>> IL61b-uni-READS-BT   bam                             
>> IL61b-uni-READS-BWA
>> <../cgi-bin/hgCustom?hgsid=507&hgct_table=ct_IL61buniREADSBWA_1901>
>> IL61b-uni-READS-BWA  ba
>>
>>
>>
>> then the order of the tracks are:
>>
>> IL1b-uni-COV-BT
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL1buniCOVBT_7272>
>> IL1b-uni-COV-BWA
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL1buniCOVBWA_8520>
>> IL1b-uni-READS-BT
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL1buniREADSBT_224>
>> IL6-uni-COV-BT
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL6uniCOVBT_2937>
>> IL6-uni-COV-BWA
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL6uniCOVBWA_5667>
>> IL61b-uni-COV-BT
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL61buniCOVBT_9658>
>> IL61b-uni-COV-BWA
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL61buniCOVBWA_6174>
>> IL1b-uni-READS-BWA
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL1buniREADSBWA_5934>
>> IL6-uni-READS-BT
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL6uniREADSBT_1329>
>> IL6-uni-READS-BWA
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL6uniREADSBWA_3537>
>> IL61b-uni-READS-BT
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL61buniREADSBT_8237>
>> IL61b-uni-READS-BWA
>> <../cgi-bin/hgTrackUi?hgsid=507&c=chr1&g=ct_IL61buniREADSBWA_1901>
>>
>>
>>
>> As you can see, IL1b-uni-READS-BWA should be next to IL1b-uni group, but
>> it is not!
>>
>> Any other experience/suggestion?
>>
>> Thanks,
>>
>> D.
>>
>>> r
>>>
>>> On Wed, Aug 4, 2010 at 3:53 PM, Duke<[email protected]
>>> <mailto:[email protected]>>  wrote:
>>>
>>>       Hi all,
>>>
>>>      I upload several tracks (in different lanes of a run) to UCSC mirror,
>>>      but the way they are shown are weird as they do not follow any order
>>>      despite the fact that I named them so that the tracks with very
>>>      similar
>>>      name should be close to each other, for example: track1-uni-READ and
>>>      track1-uni-COV. Unfortunately in the Manage Custom Track, I do not see
>>>      any feature to move a track up or down. This is quite annoying.
>>>
>>>      I might have missed something, but anybody can suggest me how to
>>>      rearrange the tracks so that they can display as I want (for example,
>>>      move one track close to another track)?
>>>
>>>      Thanks,
>>>
>>>      D.
>>>      _______________________________________________
>>>      Genome maillist  - [email protected]
>>>      <mailto:[email protected]>
>>>      https://lists.soe.ucsc.edu/mailman/listinfo/genome
>>>
>>>
>> _______________________________________________
>> Genome maillist  -  [email protected]
>> https://lists.soe.ucsc.edu/mailman/listinfo/genome
>>
> 
> _______________________________________________
> Genome maillist  -  [email protected]
> https://lists.soe.ucsc.edu/mailman/listinfo/genome
_______________________________________________
Genome maillist  -  [email protected]
https://lists.soe.ucsc.edu/mailman/listinfo/genome

Reply via email to