Hi,

I made a session with 16 custom bigWig tracks on 8/25/2011, and today when I 
load it I get the message:

"Note: the session has at least one expired custom track (in database mm9), so 
it may not appear as originally intended."

Specifically, all 16 tracks have expired.  In the session help documentation it 
mentions the 4-month session lifespan and also:

"Note that it is possible for user-generated 
tracks<http://genome.ucsc.edu/goldenPath/help/hgSessionHelp.html#CTs> contained 
within sessions to expire before the session does."

But the user-generated tracks link goes nowhere and I can't find any other 
references to the conditions under which individual tracks expire.  One way or 
the other, this is nowhere near the ostensible 4-month lifespan.

Please clarify what is going on with my session.  I can provide the url to the 
session file on request.

Thanks,
Ariel

_______________________________________________
Genome maillist  -  [email protected]
https://lists.soe.ucsc.edu/mailman/listinfo/genome

Reply via email to