Good Morning Ariel: Your sessions have not expired. Login to the wiki, go to the hgSessions page, your sessions are there to use. Other users can use the sessions with the links provided on that page.
If you have a saved sessions text file, we have no information about that data and can save nothing that belongs to it. --Hiram Paulson, Ariel wrote: > Luvina, > > I am using a session settings text file, which is stored on an ftp. The > session does load alright, or so it says -- but there are no tracks left in > it. It was working before the weekend but then stopped, and I have not made > any changes to it. I can go to my own session mgmt page and load the session > (that one seems to work), but none of my collaborators can do that, so that > is not a solution for me. > > I suppose I can just re-save the settings to a new text file and refresh the > ftp version, but if my tracks inexplicably expire in another two weeks this > is going to be a problem. So I'm trying to figure out what happened first. > > Thanks, > Ariel > > -----Original Message----- > From: Luvina Guruvadoo [mailto:[email protected]] > Sent: Tuesday, September 06, 2011 6:22 PM > To: Paulson, Ariel > Cc: '[email protected]' > Subject: Re: [Genome] Session expiration > > Hi Ariel, > > Your session seems to be working fine. It's possible you are using a URL that > contains an hgsid string that is obsolete. If you go to the Session > Management page, you should see your three sessions to use. > > Please contact us again at [email protected] if you are still experiencing > problems. > > --- > Luvina Guruvadoo > UCSC Genome Bioinformatics Group > > > On 9/6/2011 1:12 PM, Paulson, Ariel wrote: >> 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 >> > > > _______________________________________________ > Genome maillist - [email protected] > https://lists.soe.ucsc.edu/mailman/listinfo/genome > _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
