ENCODE Pre-QA: Difference between revisions

From Genecats
Jump to navigationJump to search
Line 27: Line 27:


==Note Pre-QA Pass in PushQ and Redmine==
==Note Pre-QA Pass in PushQ and Redmine==
Once you have completed pre-QA and all issues you found have been addressed/fixed:
[[Pre-QA#Note_Pre-QA_Pass_in_Redmine_and_PushQ|instructions here]]
# Add comment to redmine ticket, "Passed pre-QA" and reassign to wrangler
# Add comment to 'Notes' section of PushQ entry, "<date> Passed pre-QA (<name>)", and remove your name from the "reviewer" field.


[[Category:Browser QA ENCODE]][[Category:Browser QA]]
[[Category:Browser QA ENCODE]][[Category:Browser QA]]

Revision as of 17:00, 25 October 2011

Start at the more generic Pre-QA page, then return to this page for specifics.

ENCODE QA wiki

The ENCODE QA wiki page is where we keep the step-by-step instructions for QAing an ENCODE track. For pre-QA, you'll work on the hgTrackUi and Files (except 8.1.1) sections.

Pre-QA pushQ Entry

Follow the Review PushQ Entry wiki section

  • skip making sure that the Notes file exists

Pre-QA hgTrackUi

Follow the hgTrackUi wiki section (content = most important, jury still out on functionality)

Content

Functionality

  • Config Settings of Views: skip "Check that expId is hidden in "..." on hgwbeta. If it isn't, there is an issue."
  • MetaData: skip "in dense, default fixed range should result in meaningful banding at full chromosome (not all gray)"
  • Links: skip "...where applicable, are relative"

Pre-QA Files

Follow the Files wiki section,

Update Redmine ticket & Get fixes

instructions here

Note Pre-QA Pass in PushQ and Redmine

instructions here

Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=ENCODE_Pre-QA&oldid=588"