<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[BOL: Related items]]></title>
	<link>https://bioinformaticsonline.com/related/37049?offset=200</link>
	<atom:link href="https://bioinformaticsonline.com/related/37049?offset=200" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/45231/the-giant-who-walked-across-ancient-taiwan</guid>
	<pubDate>Sat, 15 Aug 2026 14:48:45 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/45231/the-giant-who-walked-across-ancient-taiwan</link>
	<title><![CDATA[The Giant Who Walked Across Ancient Taiwan]]></title>
	<description><![CDATA[<p>Thousands of years ago, long before Taiwan became the island we know today, a large-bodied human walked across the landscape. We will probably never know what this individual looked like or where they travelled. But part of their story survived&mdash;in two ancient leg bones recovered from the seabed of the Penghu Channel.</p><p>The bones sat quietly in a fossil collection for years. One was part of a femur; the other, a tibia. They looked like the remains of an unusually large ancient human. But who did they belong to?</p><p>The answer came from an unexpected source: ancient proteins.</p><p>Using palaeoproteomic analysis, researchers found a molecular signature in both bones that matches the Denisovan lineage. The discovery identifies the two Penghu fossils as Denisovan and, more importantly, gives scientists their first substantial glimpse of the Denisovans' body size.</p><p>And the picture is striking.</p><p>One individual is estimated to have been about 1.8 metres tall and weighed around 83 kilograms. The other may have reached 1.9 metres and about 91 kilograms. Their leg bones rank among the largest known from Pleistocene Homo.</p><p>These were not small or fragile people.</p><p>They were powerful, heavily built humans moving through Ice Age eastern Asia.</p><p>But the bones tell an even more intriguing story. The femur has a pronounced ridge called a femoral pilaster&mdash;a feature particularly associated with modern human hunter-gatherers and increased mechanical strength during terrestrial movement. Why would a Denisovan, with an otherwise strongly archaic skeleton, possess this modern-looking feature?</p><p>Perhaps these Denisovans travelled extensively across the landscape. Perhaps their bodies were shaped by a demanding hunting lifestyle. Or perhaps, the researchers suggest, genetic exchange with early modern humans contributed to some of these features.</p><p>Their extraordinary size raises another mystery. A common expectation in human evolution is that populations living closer to the tropics tend to be smaller. Yet these Denisovans lived around 23&deg;N latitude and were exceptionally large. The researchers argue that cold climate alone cannot explain their size, pointing instead toward lifestyle and diet&mdash;including evidence that at least one Penghu individual relied heavily on meat.</p><p>So, piece by piece, the Denisovans are becoming less mysterious.</p><p>What was once a shadowy population known mainly from DNA is beginning to take physical form: large, robust, mobile humans who lived across eastern Asia and whose bodies carried a fascinating mixture of ancient and modern traits.</p><p>And perhaps the most remarkable part of this story is where it began&mdash;not in a spectacular cave discovery, but with two weathered bones lying among thousands of fossils.</p><p>The Denisovans may have left no written history. But their bones are beginning to tell one.</p><p>*Note: This research is currently a bioRxiv preprint and has not yet undergone peer review.&nbsp; Detail at&nbsp;https://www.biorxiv.org/content/10.64898/2026.08.07.743438v1.full.pdf</p>]]></description>
	<dc:creator>Jitendra Narayan</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/42987/public-databases-for-bioinformatics</guid>
	<pubDate>Tue, 23 Mar 2021 05:32:15 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/42987/public-databases-for-bioinformatics</link>
	<title><![CDATA[Public Databases for Bioinformatics !]]></title>
	<description><![CDATA[<pre>https://www.nature.com/articles/s41467-020-17155-y<br><br>Server Infrastructure:

File Server:

dhara: Synology 3614 Storage Appliance
4 Core Xeon
108TB disk storage
10Gb ethernet to SCG3
Access atx: dhara:5000
Has btsync server (try it - its much better than dropbox)

Compute Servers:

nandi: Kundaje and Phi Server
24 intel cores
256GB RAM
500GB of SSD storage 
36TB RAID6 local storage
4 Intel Phi's (space for 4 more GPU's)


durga: Montgomery and sensitive data
24 intel cores
256GB RAM
500GB of SSD RAID0 storage 
60TB RAID6 local storage

mitra: Bassik and Web/DB Server
24 core
256GB RAM 
500GB of SSD RAID0 storage 
36TB RAID6 local storage

vayu: Kundaje GPU server
4 core
64GB RAM 
200GB of SSD storage 
8TB RAID10 local storage
4 Nvidia GTX 970 4GB GPUs

amold: Bickel and SGE server
32 AMD core
128GB RAM 
200GB of SSD storage 
12TB RAID5 local storage

wotan: Bickel and SGE server
64 AMD core
256GB RAM 
200GB of SSD storage 
12TB RAID5 local storage

Filesystem:

/users/$USER
default home directory
full backups nightly 
nfs mount to dhara
should store code, papers, and other highly processed data here

/mnt/data/
globally accessible data
should store common data here
e.g. genomes and indexes, annotations, ENCODE data  
if you dont want this to count towards your quote you must chown

/mnt/lab_data/$LAB/
lab accessible data
should store lab project data here 
e.g. ATAC-seq prediction data, enhancer prediction, motif calls

/srv/scratch/$USER
fast local storage
not backed up, but on raid and data will never be deleted
most analysis should be performed here

/srv/persistent/$USER
fast local storage
synced nightly, but not backed up
       ie if the hard drives fail or you delete something and notice 
       within 24 hours we can recover. Otherwise not. (vs home which is 
       properly backed up )  
intermediate analysis products that would be hard to recover should be stored here 
       e.g. stochastic analysis results that need to be kept so that paper 
       results can be reproduced

/srv/www/$LABNAME/
web accessible from mitra.stanford.edu
*NOT BACKED UP*

Some parallel programming patterns:

# gzip a bunch of files
parallel gzip -- *.FILESTOGZIP

# fork example in python:
(for more detailed examples look at 
 https://github.com/nboley/grit/ grit/lib/multiprocessing_utils.py)

import os
import time
import random

import multiprocessing

class ProcessSafeOPStream( object ):
    def __init__( self, writeable_obj ):
        self.writeable_obj = writeable_obj
        self.lock = multiprocessing.Lock()
        self.name = self.writeable_obj.name
        return
    
    def write( self, data ):
        self.lock.acquire()
        self.writeable_obj.write( data )
        self.writeable_obj.flush()
        self.lock.release()
        return
    
    def close( self ):
        self.writeable_obj.close()

def worker(queue, ofp):
    # Try without this
    random.seed()
    while True:
        i = queue.get()
        if i == 'FINISHED': return
        # simulate an expensive function
        x = random.random()
        time.sleep(x/10)
        print i, x
        ofp.write("%i\t%s\n" % (i, x))

NSIMS = 10000
NPROC = 25

# populate queue
todo = multiprocessing.Queue()
for i in xrange(NSIMS): todo.put(i)
for i in xrange(NPROC): todo.put('FINISHED')

ofp = ProcessSafeOPStream( open("output.txt", "w") )

pids = []
for i in xrange(NPROC):
    pid = os.fork()
    if pid == 0:
       worker(todo, ofp)
       os._exit(0)
    else:
       pids.append(pid)  

for pid in pids:
    os.waitpid(pid, 0)

ofp.close()

print "FINISHED"<br><br></pre>
<p>For use case 1 we obtained the following ENCODE and ROADMAP datasets&nbsp;<a href="https://www.encodeproject.org/files/ENCFF446WOD/@@download/ENCFF446WOD.bed.gz">https://www.encodeproject.org/files/ENCFF446WOD/@@download/ENCFF446WOD.bed.gz</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF546PJU/@@download/ENCFF546PJU.bam">https://www.encodeproject.org/files/ENCFF546PJU/@@download/ENCFF546PJU.bam</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF059BEU/@@download/ENCFF059BEU.bam">https://www.encodeproject.org/files/ENCFF059BEU/@@download/ENCFF059BEU.bam</a>. Blacklisted regions were obtained from&nbsp;<a href="http://mitra.stanford.edu/kundaje/akundaje/release/blacklists/hg38-human/hg38.blacklist.bed.gz">http://mitra.stanford.edu/kundaje/akundaje/release/blacklists/hg38-human/hg38.blacklist.bed.gz</a>. The human genome version hg38 was obtained from&nbsp;<a href="http://hgdownload.cse.ucsc.edu/goldenPath/hg38/bigZips/hg38.fa.gz">http://hgdownload.cse.ucsc.edu/goldenPath/hg38/bigZips/hg38.fa.gz</a>.</p>
<p>For use case 2 we used the set of narrowPeak files summarized in&nbsp;<a href="https://github.com/wkopp/janggu_usecases/tree/master/extra/urls.txt">https://github.com/wkopp/janggu_usecases/tree/master/extra/urls.txt</a>&nbsp;(archived version v1.0.1). The human genome version hg19 was obtained from&nbsp;<a href="http://hgdownload.cse.ucsc.edu/goldenPath/hg19/bigZips/hg19.fa.gz">http://hgdownload.cse.ucsc.edu/goldenPath/hg19/bigZips/hg19.fa.gz</a></p>
<p>For use case 3 we used the ENCODE datasets&nbsp;<a href="https://www.encodeproject.org/files/ENCFF591XCX/@@download/ENCFF591XCX.bam">https://www.encodeproject.org/files/ENCFF591XCX/@@download/ENCFF591XCX.bam</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF736LHE/@@download/ENCFF736LHE.bigWig">https://www.encodeproject.org/files/ENCFF736LHE/@@download/ENCFF736LHE.bigWig</a>,&nbsp;<a href="https://www.encodeproject.org/files/ENCFF177HHM/@@download/ENCFF177HHM.bam">https://www.encodeproject.org/files/ENCFF177HHM/@@download/ENCFF177HHM.bam</a>&nbsp;as we as the GENCODE annotation v29 from&nbsp;<a href="ftp://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_human/release_29/gencode.v29.annotation.gtf.gz">ftp://ftp.ebi.ac.uk/pub/databases/gencode/Gencode_human/release_29/gencode.v29.annotation.gtf.gz</a>.</p><p>Address of the bookmark: <a href="http://mitra.stanford.edu/" rel="nofollow">http://mitra.stanford.edu/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/news/view/40416/5700-year-old-human-genome</guid>
	<pubDate>Thu, 19 Dec 2019 11:22:18 -0600</pubDate>
	<link>https://bioinformaticsonline.com/news/view/40416/5700-year-old-human-genome</link>
	<title><![CDATA[5700 year-old human genome !]]></title>
	<description><![CDATA[<p>A Landmark in genomics, scientists have done something that hasn't been done ever.</p><p>Scientists have reconstructed the genome of an ancient human who lived nearly 5,700 years ago in Southern Denmark from the birch pitch- an ancient tar-like substance.</p><p>By sequencing the sample, researchers not only discovered the ancient human DNA but also microbial DNA reflecting the oral microbiome of the person who chewed the pitch, along with plant and animal DNA that could be the recent<span> meal she might have consumed.</span></p><p><span style="font-size: 12.8px;">The DNA sample is comparable in quality to well-preserved teeth and skull bones. The DNA suggests that the chewer was a female, most likely with dark skin, dark brown hair and blue eyes.</span></p><div><p><a href="https://www.nature.com/articles/s41467-019-13549-9?fbclid=IwAR0FPk0Cl25YjHVdcfK4tqFhCsPx00SCSMUwlU6zNwMDNrKi1QynwtJKDfE" target="_blank">https://www.nature.com/articles/s41467-019-13549-9</a></p><p><img src="https://i.kinja-img.com/gawker-media/image/upload/c_scale,f_auto,fl_progressive,q_80,w_800/ykcvh491evenyvlrjb9r.jpg" width="800" height="450" alt="image" style="border: 0px;"></p><p>Artistic reconstruction. (Tom Bj&ouml;rklund)</p><p>More at&nbsp;<a href="https://gizmodo.com/scientists-reconstruct-lola-after-finding-her-dna-in-1840481633">https://gizmodo.com/scientists-reconstruct-lola-after-finding-her-dna-in-1840481633</a></p></div>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/44783/when-chromosomes-shift-understanding-chromosome-rearrangement-and-human-disease</guid>
	<pubDate>Fri, 11 Apr 2025 01:07:17 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/44783/when-chromosomes-shift-understanding-chromosome-rearrangement-and-human-disease</link>
	<title><![CDATA[When Chromosomes Shift: Understanding Chromosome Rearrangement and Human Disease]]></title>
	<description><![CDATA[<p>In the vast and complex world of genetics, our chromosomes are like carefully arranged bookshelves &mdash; each holding critical information that defines who we are. But what happens when those books are shuffled, inverted, or swapped? The answer lies in a phenomenon known as <strong>chromosome rearrangement</strong>, a powerful force behind many human diseases, from developmental disorders to cancer.</p><h2>What Are Chromosome Rearrangements?</h2><p><strong>Chromosome rearrangements</strong> are structural changes that alter the normal configuration of chromosomes. These changes can involve large segments of DNA &mdash; from thousands to millions of base pairs &mdash; and can occur <strong>spontaneously</strong>, be <strong>inherited</strong>, or result from <strong>exposure to mutagens</strong> (like radiation or chemicals).</p><h3>Common Types of Rearrangements:</h3><ol>
<li>
<p><strong>Deletions</strong> &ndash; Loss of a chromosome segment</p>
</li>
<li>
<p><strong>Duplications</strong> &ndash; Repetition of a segment</p>
</li>
<li>
<p><strong>Inversions</strong> &ndash; A segment breaks off, flips, and reattaches</p>
</li>
<li>
<p><strong>Translocations</strong> &ndash; Segments exchange places between non-homologous chromosomes</p>
</li>
<li>
<p><strong>Insertions</strong> &ndash; A segment is inserted into another part of the genome</p>
</li>
</ol><p>These changes can disrupt genes directly or affect gene regulation, leading to disease.</p><h2>How Do Chromosome Rearrangements Cause Disease?</h2><p>The impact of a rearrangement depends on <strong>which genes are involved</strong>, <strong>how much DNA is affected</strong>, and <strong>when the rearrangement occurs</strong> (in development vs. adulthood). Here are some key mechanisms:</p><ul>
<li>
<p><strong>Gene disruption</strong>: Breaking a gene can lead to loss of function or the creation of a non-functional protein.</p>
</li>
<li>
<p><strong>Gene fusion</strong>: Joining parts of two genes may form a novel hybrid gene with new functions (common in cancer).</p>
</li>
<li>
<p><strong>Dosage effects</strong>: Extra or missing gene copies can disturb the balance of gene expression.</p>
</li>
<li>
<p><strong>Position effects</strong>: Moving a gene to a new regulatory environment may silence or over-activate it.</p>
</li>
</ul><h2>Chromosome Rearrangements in Human Disease</h2><h3>1. <strong>Developmental Disorders</strong></h3><ul>
<li>
<p><strong>Cri-du-chat syndrome</strong>: Caused by a deletion on chromosome 5p. Affected infants often have a high-pitched cry and intellectual disability.</p>
</li>
<li>
<p><strong>Williams syndrome</strong>: Results from a microdeletion on chromosome 7q, affecting genes related to cardiovascular and cognitive function.</p>
</li>
</ul><h3>2. <strong>Cancer</strong></h3><p>Cancer is perhaps the most striking example of disease caused by chromosome rearrangements.</p><ul>
<li>
<p><strong>Chronic Myeloid Leukemia (CML)</strong>: Caused by a translocation between chromosomes 9 and 22, forming the <em>Philadelphia chromosome</em>. This creates the <strong>BCR-ABL fusion gene</strong>, which drives uncontrolled cell growth.</p>
</li>
<li>
<p><strong>Burkitt lymphoma</strong>: Involves translocation of the <strong>MYC</strong> gene, leading to excessive cell division.</p>
</li>
<li>
<p><strong>Ewing sarcoma</strong>: A fusion of EWSR1 and FLI1 genes through translocation promotes tumor development.</p>
</li>
</ul><h3>3. <strong>Infertility and Miscarriages</strong></h3><p>Balanced rearrangements (like inversions or translocations) in carriers may not cause disease directly but can result in:</p><ul>
<li>
<p><strong>Recurrent miscarriages</strong></p>
</li>
<li>
<p><strong>Infertility</strong></p>
</li>
<li>
<p><strong>Birth defects in offspring</strong></p>
</li>
</ul><h2>Detecting Rearrangements</h2><p>Thanks to modern genomics, chromosome rearrangements can now be detected with high precision using:</p><ul>
<li>
<p><strong>Karyotyping</strong> &ndash; Classic method for detecting large rearrangements</p>
</li>
<li>
<p><strong>FISH (Fluorescence In Situ Hybridization)</strong> &ndash; Uses fluorescent probes to target specific DNA sequences</p>
</li>
<li>
<p><strong>Array CGH (Comparative Genomic Hybridization)</strong> &ndash; Detects copy number changes across the genome</p>
</li>
<li>
<p><strong>Whole Genome Sequencing (WGS)</strong> &ndash; Identifies even small or complex rearrangements at base-pair resolution</p>
</li>
</ul><h2>Looking Forward: The Future of Chromosome Medicine</h2><p>Understanding chromosome rearrangements is now central to:</p><ul>
<li>
<p><strong>Personalized medicine</strong></p>
</li>
<li>
<p><strong>Genetic counseling</strong></p>
</li>
<li>
<p><strong>Targeted therapies</strong>, especially in cancer (e.g., tyrosine kinase inhibitors for BCR-ABL fusion)</p>
</li>
</ul><p>With the rise of long-read sequencing and single-cell genomics, even previously &ldquo;invisible&rdquo; rearrangements are being uncovered, offering new insights into both rare diseases and common conditions.</p><h2>Final Thoughts</h2><p>Chromosome rearrangements remind us that genetics isn't just about which genes we have &mdash; but where they are, how they're arranged, and when they're active. As our tools grow sharper, so does our ability to diagnose, understand, and treat diseases rooted in genomic architecture.</p><p>In a way, the genome is like a book not just defined by its words, but also by how the chapters are ordered. Rearranging them can create a new story &mdash; sometimes harmful, sometimes insightful &mdash; and understanding these changes is key to writing a healthier future.</p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/35173/dot-an-interactive-viewer-for-genome-genome-comparison</guid>
	<pubDate>Sun, 14 Jan 2018 11:57:34 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/35173/dot-an-interactive-viewer-for-genome-genome-comparison</link>
	<title><![CDATA[Dot, an interactive viewer for genome-genome comparison]]></title>
	<description><![CDATA[<p><span>Dot, an interactive dot plot viewer that allows genome scientists to visualize genome-genome alignments in order to evaluate new assemblies and perform exploratory comparative genomics.&nbsp;</span></p>
<p><span>Dot supports the output of MUMmer&rsquo;s nucmer aligner the most commonly used software method for aligning genome assemblies. A quick script called DotPrep.py converts the delta file to a more streamlined coordinates file with an index that enables Dot to read in more alignments in certain regions on demand.</span></p>
<p><strong><span>Dot, an interactive viewer for genome-genome comparison</span></strong></p>
<p>https://dnanexus.github.io/dot/</p><p>Address of the bookmark: <a href="https://github.com/dnanexus/dot" rel="nofollow">https://github.com/dnanexus/dot</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/40969/leaflet-javascript-libraries-for-interactive-maps</guid>
	<pubDate>Mon, 10 Feb 2020 01:35:07 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/40969/leaflet-javascript-libraries-for-interactive-maps</link>
	<title><![CDATA[Leaflet: JavaScript libraries for interactive maps]]></title>
	<description><![CDATA[<p><a href="http://leafletjs.com/">Leaflet</a><span>&nbsp;is one of the most popular open-source JavaScript libraries for interactive maps.</span></p>
<h3>Features</h3>
<ul>
<li>Interactive panning/zooming</li>
<li>Compose maps using arbitrary combinations of:
<ul>
<li>Map tiles</li>
<li>Markers</li>
<li>Polygons</li>
<li>Lines</li>
<li>Popups</li>
<li>GeoJSON</li>
</ul>
</li>
<li>Create maps right from the R console or RStudio</li>
<li>Embed maps in&nbsp;<a href="http://yihui.name/knitr/">knitr</a>/<a href="http://rmarkdown.rstudio.com/">R Markdown</a>&nbsp;documents and&nbsp;<a href="http://shiny.rstudio.com/">Shiny</a>&nbsp;apps</li>
<li>Easily render spatial objects from the&nbsp;<code>sp</code>&nbsp;or&nbsp;<code>sf</code>&nbsp;packages, or data frames with latitude/longitude columns</li>
<li>Use map bounds and mouse events to drive Shiny logic</li>
<li>Display maps in non spherical mercator projections</li>
<li>Augment map features using chosen plugins from&nbsp;<a href="http://leafletjs.com/plugins">leaflet plugins repository</a></li>
</ul>
<p><a href="https://rstudio.github.io/leaflet/">https://rstudio.github.io/leaflet/</a></p><p>Address of the bookmark: <a href="https://rstudio.github.io/leaflet/" rel="nofollow">https://rstudio.github.io/leaflet/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/44904/termal-a-fast-and-interactive-terminal-based-viewer-for-multiple-sequence-alignments</guid>
	<pubDate>Mon, 22 Sep 2025 23:51:02 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/44904/termal-a-fast-and-interactive-terminal-based-viewer-for-multiple-sequence-alignments</link>
	<title><![CDATA[Termal: a fast and interactive terminal-based viewer for multiple sequence alignments]]></title>
	<description><![CDATA[<p>termal, a fast, interactive, terminal-based viewer for multiple sequence alignments (MSAs), designed for use on remote systems such as high-performance computing (HPC) clusters.</p>
<p>https://academic.oup.com/bioinformaticsadvances/advance-article/doi/10.1093/bioadv/vbaf208/8257678?login=true</p><p>Address of the bookmark: <a href="https://github.com/sib-swiss/termal" rel="nofollow">https://github.com/sib-swiss/termal</a></p>]]></description>
	<dc:creator>LEGE</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/36508/mitobim-mitochondrial-baiting-and-iterative-mapping</guid>
	<pubDate>Tue, 08 May 2018 04:15:25 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/36508/mitobim-mitochondrial-baiting-and-iterative-mapping</link>
	<title><![CDATA[MITObim - mitochondrial baiting and iterative mapping]]></title>
	<description><![CDATA[<p>This document contains instructions on how to use the MITObim pipeline described in Hahn et al. 2013. The full article can be found&nbsp;<a href="http://nar.oxfordjournals.org/content/41/13/e129" title="MITObim full article at NAR">here</a>. Kindly cite the article if you are using MITObim in your work. The pipeline was originally developed for&nbsp;<span>Illumina</span>&nbsp;data, but thanks to the versatility of the MIRA assembler, MITObim supports in principle also data from the&nbsp;<span>Iontorrent</span>,&nbsp;<span>454</span>&nbsp;and&nbsp;<span>PacBio</span>&nbsp;sequencing platforms.</p>
<p>Below you can find a few basic tutorials for how to run MITObim and I encorage you to give them a try with the testdata that comes with this Repo, just to make sure everything is running smoothly on your system. It'll only take a few minutes and will potentially safe you a lot of time down the line.</p>
<p>I provide further examples&nbsp;<a href="https://github.com/chrishah/MITObim/tree/master/examples">here</a>&nbsp;as Jupyter notebooks. Get in touch if you feel like sharing your particular MITObim solution and I'd be happy to put it up here, too!</p><p>Address of the bookmark: <a href="https://github.com/chrishah/MITObim" rel="nofollow">https://github.com/chrishah/MITObim</a></p>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/37800/heatmapper-web-enabled-heat-mapping-for-all</guid>
	<pubDate>Mon, 01 Oct 2018 08:34:41 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/37800/heatmapper-web-enabled-heat-mapping-for-all</link>
	<title><![CDATA[Heatmapper: web-enabled heat mapping for all]]></title>
	<description><![CDATA[<p><span>Heatmapper is a freely available web server that allows users to interactively visualize their data in the form of heat maps through an easy-to-use graphical interface. Heatmapper is a versatile tool that allows users to easily create a wide variety of heat maps for many different data types and applications. Heatmapper allows users to generate, cluster and visualize: </span></p>
<p><span>1)&nbsp;</span><span>expression-based heat maps</span><span>&nbsp;from transcriptomic, proteomic and metabolomic experiments; 2)&nbsp;</span><span>pairwise distance maps</span><span>; </span></p>
<p><span>3)&nbsp;</span><span>correlation maps</span><span>; </span></p>
<p><span>4)&nbsp;</span><span>image overlay heat maps</span><span>; </span></p>
<p><span>5)&nbsp;</span><span>latitude and longitude heat maps</span><span>&nbsp;and </span></p>
<p><span>6)&nbsp;</span><span>geopolitical (choropleth) heat maps</span><span>. </span></p>
<p><span>Heatmapper offers a number of simple and intuitive customization options for easy adjustments to each heat map&rsquo;s appearance and plotting parameters. Heatmapper also allows users to interactively explore their numeric data values by hovering their cursor over each heat map, or by using a searchable/sortable data table view.</span></p>
<p><span>Ref&nbsp;https://www.ncbi.nlm.nih.gov/pubmed/27190236</span></p><p>Address of the bookmark: <a href="http://www2.heatmapper.ca/" rel="nofollow">http://www2.heatmapper.ca/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/news/view/11144/scientists-map-17294-proteins-produced-in-human-body</guid>
	<pubDate>Thu, 29 May 2014 01:57:55 -0500</pubDate>
	<link>https://bioinformaticsonline.com/news/view/11144/scientists-map-17294-proteins-produced-in-human-body</link>
	<title><![CDATA[Scientists map 17,294 proteins produced in human body]]></title>
	<description><![CDATA[<p>Indian scientists missed the genomic profiling bus, but they've more than made up for it by creating the first human proteome map which is an extension of the genomic study. Till now, here is no direct equivalent for the human proteome. But recently two groups present mass spectrometry-based analysis of human tissues, body fluids and cells mapping the large majority of the human proteome.</p><p>The Indian scientists working in Bangalore, along with their American counterparts, have mapped more than 17,000 proteins in 30 organs of the human body. Just like the human genome was sequenced around the turn of the millennium, this is an equivalent mapping of the human proteome.<br /><br />The researcher estimated there are around 20,500 proteins in the human body. These scientists have profiled around 17,294, which account for around 84% of the total proteins. Apart from this, the team also traced around 2,500 of 3,000 proteins that had been categorised as "missing proteins".</p><p>The work, done by group of Indian scientists, and Johns Hopkins University, published in the renowned journal Nature ( http://www.nature.com/nature/journal/v509/n7502/full/nature13302.html ). Of the 72 people who worked on the project, 46 are Indians.</p><p>Reference:</p><p>http://www.nature.com/nature/journal/v509/n7502/full/nature13302.html</p><p>http://www.proteinatlas.org/ -The antibody-based Human Protein Atlas programme</p><p>http://www.humanproteomemap.org/ -Proteogenomic analysis by identifying translated proteins from annotated pseudogenes, non-coding RNAs and untranslated regions.</p><p>https://www.proteomicsdb.org/ -Assembled protein evidence for 18,097 genes in ProteomicsDB</p><p>&nbsp;</p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>

</channel>
</rss>