Requests for liftOver files: Difference between revisions

From Genecats
Jump to navigationJump to search
(Adding a request for liftOver files from the mailing list page)
 
(→‎Overview: Overview linking to MLM FAQ)
Line 2: Line 2:


==Overview==
==Overview==
The [http://redmine.soe.ucsc.edu/projects/maillists/wiki/MLM_FAQs#LiftOver-Files MLM FAQ on LiftOver files] shares some guidelines:
===liftOver files for assemblies with no browser===
We do not provide liftOver files for assemblies for which we do not have at least a minimal browser. If a user requests such a file, please point them to this [http://genomewiki.ucsc.edu/index.php/LiftOver_Howto wiki page] and wish them luck!
===liftOver file requests for assemblies with a browser===
When a specific liftOver file is requested from a user for an existing browser, we should definitely consider making it. It should go through the usual process (make a redmine, assign to an engineer, place in pushQ, QA and release). QA can do a minimal QA job on it (does it work? does it show up?) before pushing it to hgdownload and enabling it on the RR. There is no need to create companion net/chain tracks (unless the user specifically asked for that). The MLM who received the question is not responsible for QAing the liftOver file (it should just go into the pushQ like all data). After it is released, whoever QAd it should contact the user to let them know that it's available.


==Topic 1==
==Topic 1==

Revision as of 18:15, 17 March 2016


Overview

The MLM FAQ on LiftOver files shares some guidelines:

liftOver files for assemblies with no browser

We do not provide liftOver files for assemblies for which we do not have at least a minimal browser. If a user requests such a file, please point them to this wiki page and wish them luck!

liftOver file requests for assemblies with a browser

When a specific liftOver file is requested from a user for an existing browser, we should definitely consider making it. It should go through the usual process (make a redmine, assign to an engineer, place in pushQ, QA and release). QA can do a minimal QA job on it (does it work? does it show up?) before pushing it to hgdownload and enabling it on the RR. There is no need to create companion net/chain tracks (unless the user specifically asked for that). The MLM who received the question is not responsible for QAing the liftOver file (it should just go into the pushQ like all data). After it is released, whoever QAd it should contact the user to let them know that it's available.

Topic 1

  • insert line into to hgcentralbeta on hgwbeta:
First check to make sure that this line isn't already on hgcentralbeta (duplicate lines are hard to remove):
hgwdev~$ hgsql -h mysqlbeta
mysql> use hgcentralbeta

Topic 2