More recently, we've been enthused about using k-mer based similarity measures and computing and searching k-mer-based sketch search databases for all the things.

But I haven't spent too much talking about using k-mers for taxonomy, although that has become an ahem area of interest recently, if you read into our papers a bit.

In this blog post I'm going to fix this by doing a little bit of a literature review and waxing enthusiastic about other people's work. Then in a future blog post I'll talk about how we're building off of this work in fun! and interesting? ways!

Address of the bookmark: http://ivory.idyll.org/blog/2017-something-about-kmers.html

General information.

Field terminator is "\t|\t"

Row terminator is "\t|\n"

nodes.dmp file consists of taxonomy nodes. The description for each node includes the following

fields:

tax_id -- node id in GenBank taxonomy database

  parent tax_id -- parent node id in GenBank taxonomy database

  rank -- rank of this node (superkingdom, kingdom, ...) 

  embl code -- locus-name prefix; not unique

  division id -- see division.dmp file

  inherited div flag  (1 or 0) -- 1 if node inherits division from parent

  genetic code id -- see gencode.dmp file

  inherited GC  flag  (1 or 0) -- 1 if node inherits genetic code from parent

  mitochondrial genetic code id -- see gencode.dmp file

  inherited MGC flag  (1 or 0) -- 1 if node inherits mitochondrial gencode from parent

  GenBank hidden flag (1 or 0)            -- 1 if name is suppressed in GenBank entry lineage

  hidden subtree root flag (1 or 0)       -- 1 if this subtree has no sequence data yet

  comments -- free-text comments and citations

Taxonomy names file (names.dmp):

tax_id -- the id of node associated with this name

name_txt -- name itself

unique name -- the unique variant of this name if name not unique

name class -- (synonym, common name, ...)

Divisions file (division.dmp):

division id -- taxonomy database division id

division cde -- GenBank division code (three characters)

division name -- e.g. BCT, PLN, VRT, MAM, PRI...

comments

Genetic codes file (gencode.dmp):

genetic code id -- GenBank genetic code id

abbreviation -- genetic code name abbreviation

name -- genetic code name

cde -- translation table for this genetic code

starts -- start codons for this genetic code

Deleted nodes file (delnodes.dmp):

tax_id -- deleted node id

Merged nodes file (merged.dmp):

old_tax_id                              -- id of nodes which has been merged

new_tax_id                              -- id of nodes which is result of merging

Citations file (citations.dmp):

cit_id -- the unique id of citation

cit_key -- citation key

pubmed_id -- unique id in PubMed database (0 if not in PubMed)

medline_id -- unique id in MedLine database (0 if not in MedLine)

url -- URL associated with citation

text -- any text (usually article name and authors).

-- The following characters are escaped in this text by a backslash:

-- newline (appear as "\n"),

-- tab character ("\t"),

-- double quotes ('\"'),

-- backslash character ("\\").

taxid_list -- list of node ids separated by a single space

http://bioinformaticsonline.com/videolist/watch/19555/a-3d-map-of-the-human-genome

Researchers have been working to determine how cells regulate gene expression for nearly as long as we’ve known about DNA. How, for example, do nerve cells know to turn off only nerve cell genes and turn off bone cell genes? DNA folding loops are part of the answer. This research team, which published their findings in a paper in Cell http://www.cell.com/cell/abstract/S0092-8674%2814%2901497-4 , found that the number of loops is much lower than expected. There are only 10,000 loops instead of the predicted millions, and they form on/off switches in DNA.

More at http://www.eurekalert.org/pub_releases/2014-12/ru-3mr121114.php

Reference http://www.cell.com/cell/abstract/S0092-8674%2814%2901497-4

We have sequenced the CHM13hTERT human cell line with a number of technologies. Human genomic DNA was extracted from the cultured cell line. As the DNA is native, modified bases will be preserved. The data includes 30x PacBio HiFi, 120x coverage of Oxford Nanopore, 70x PacBio CLR, 50x 10X Genomics, as well as BioNano DLS and Arima Genomics HiC. Most raw data is available from this site, with the exception of the PacBio data which was generated by the University of Washington/PacBio and is available from NCBI SRA.

A UCSC browser is available for v2.0 (as well as legacy v1.0 and v1.1 versions). An interactive dotplot visualization of all genomic repeats is also available from resgen.io. Known issues identified in the assembly are tracked at CHM13 issues.

MORE at https://github.com/marbl/CHM13

Address of the bookmark: https://www.science.org/doi/10.1126/science.abj6987

There are Neanderthal bones. Denisovan remains. Fossils from ancient relatives of our species. Each specimen gives us another piece of the story of how Homo sapiens came to be.

But now imagine that one of the most important characters in that story has left behind no fossil, no skull, no bone, and no genome.

Nothing that a paleontologist could put behind glass.

And yet, somehow, that ancient population is still speaking.

It is speaking through us.

A fascinating new study published in Science (https://www.science.org/doi/10.1126/science.aef8874?) introduces a computational method called TRACE, which allows scientists to search modern human genomes for genetic traces of ancient populations that have never been directly identified.

For years, scientists have known that our ancestors interacted with Neanderthals and Denisovans. Their DNA still survives in modern human populations. But these may not have been the only ancient humans who crossed paths with our ancestors.

Using TRACE, researchers found evidence of an unknown archaic population that contributed DNA to the ancestors of modern humans before humans spread beyond Africa.

Even more surprisingly, they found evidence of a much older lineage—possibly around 1.8 million years old—whose genetic legacy may have reached some modern humans indirectly through Denisovans.

The extraordinary part is that researchers did not need DNA from these mysterious populations to detect them. Instead, they studied the ancestry of modern genomes and looked for genetic patterns that revealed unusually ancient branches of our family history.

It is almost like finding the footprints of someone who disappeared thousands of years ago—without ever finding the person themselves.

These discoveries suggest that human evolution was far more complicated than a simple family tree. Ancient human populations repeatedly separated, migrated, met and exchanged genes. Some eventually disappeared, but pieces of their genetic legacy survived.

And that means our DNA is more than a biological instruction manual.

It is also an archive of human history.

Some of the people recorded in that archive may never have a name or a fossil. But thanks to methods like TRACE, their genetic echoes are finally becoming visible.

The next big discovery about our ancient past may not come from a fossil in the ground.

It may already be inside us.

Reference: Zhang et al., “Recovering signatures of archaic hominin introgression using ancestral recombination graphs,” Science (2026), DOI: 10.1126/science.aef8874. Detail paper @ https://www.science.org/doi/10.1126/science.aef8874?

The TRACE repository (https://github.com/YulinZhang9806/trace) contains the Python package and command-line tools used to infer archaic admixture tracts from ancestral recombination graphs.

TRRUST database also provides information of mode of regulation (activation or repression). Currently 8,972 (59.8%) regulatory relationships are known for mode of regulation.

Search at : http://www.grnpedia.org/trrust/Network_search_form.php

Address of the bookmark: http://www.grnpedia.org/trrust/

Address of the bookmark: http://www.weizmann.ac.il/Biological_Regulation/IgorUlitsky/PLAR

To cite BioNumbers please refer to: Milo et al. Nucl. Acids Res. (2010) 38: D750-D753. When using a specific entry from the database it is highly recommended that you also specify the BioNumbers 6 digit ID, e.g. "BNID 100986, Milo et al 2010". 

Address of the bookmark: http://bionumbers.hms.harvard.edu/

More at http://www.ncbi.nlm.nih.gov/projects/HistoneDB2.0/index.fcgi/browse/

Address of the bookmark: http://www.ncbi.nlm.nih.gov/projects/HistoneDB2.0/index.fcgi/browse/

https://gold.jgi.doe.gov/

Address of the bookmark: https://gold.jgi.doe.gov/