ENCODE Pre-QA

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

Enter any issues in the redmine ticket for that track (can be done as you pre-QA).

1. Go to redmine to your "My Page" and select the appropriate ticket.
2. Click "update", enter your comments. At the bottom, where you see "Assign question to," enter the wrangler (person you added as watcher, also listed as the "Sponsor" in the pushQ), then click "preview" to see how your comment will look, you can edit more, click "Submit" when satisfied.

Note Pre-QA Pass in PushQ and Redmine

Once you have completed pre-QA and all issues you found have been addressed/fixed:

1. Add comment to redmine ticket, "Passed pre-QA" and reassign to wrangler
2. Add comment to 'Notes' section of PushQ entry, "<date> Passed pre-QA (<name>)", and remove your name from the "reviewer" field.