ENCODE Pre-QA: Difference between revisions
From Genecats
Jump to navigationJump to search
(split this page off of Pre-QA page) |
|||
| Line 24: | Line 24: | ||
==Update Redmine ticket & Get fixes== | ==Update Redmine ticket & Get fixes== | ||
[[Pre-QA#Update_Redmine_ticket_.26_Get_fixes|instructions here]] | |||
# | |||
==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: | Once you have completed pre-QA and all issues you found have been addressed/fixed: | ||
Revision as of 16:59, 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
- skip Labels section
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,
- skip the File Count sub-section.
Update Redmine ticket & Get fixes
Note Pre-QA Pass in PushQ and Redmine
Once you have completed pre-QA and all issues you found have been addressed/fixed:
- 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.
