DReichLab / DReichLab/waldo

Non-bam-analysis-related annotations not in database

Open
#276 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Description

There are a handful of columns in the anno file that are not metrics and currently do not have representation in the database and/or are not generated by anno_file_generate. These are:

  • Index
  • Pulldown Strategy
  • Suffices (indicating data types used for sources which can be a subset of that in bam)
  • Data type
  • No. Libraries
  • Data original pulldown logfile location
  • Data repulldown logfile location
  • Library type (minus=no.damage.correction, half=damage.retained.at.last.position, plus=damage.fully.corrected, ds=double.stranded.library.preparation, ss=single.stranded.library.preparation)

There are also a couple of columns which do pertain to metrics but cannot be calculated just by running bam analysis blindly on the nuclear/MT bams. These are:

  • Mean length of shotgun sequences (merged data)
  • endogenous by library (computed on shotgun data)

Do we plan to represent any and/or all of these in the database? Would some be better dropped or combined?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating anno_file_generate and the database representation for annotation columns, then determine which listed fields are supported or computable; done requires an agreed scope for retaining, combining, or dropping them and a corresponding implementation plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.