<?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/44373?offset=280</link>
	<atom:link href="https://bioinformaticsonline.com/related/44373?offset=280" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/43550/basic-structure-of-snakemake-pipeline-run</guid>
	<pubDate>Thu, 14 Oct 2021 07:01:38 -0500</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/43550/basic-structure-of-snakemake-pipeline-run</link>
	<title><![CDATA[Basic Structure of Snakemake Pipeline Run !]]></title>
	<description><![CDATA[<div>/user/snakemake-demo$ ls</div><div>config.json data envs scripts slurm-240702.out Snakefile</div><ul>
<li>data = mock data for the snakefile to use</li>
<li>Snakefile = name of the snakemake &ldquo;formula&rdquo; file
<ul>
<li>Note: The default file that snakemake looks for in the current working directory is the&nbsp;<code>Snakefile</code>. If you would like to override that you can specify it following the&nbsp;<code>-s</code>
<ul>
<li><code>snakemake -s snakefile.py</code></li>
</ul>
</li>
</ul>
</li>
<li>envs = directory for storing the conda environments that the workflow will use.</li>
<li>scripts = directory for storing python scripts called by the snakemake formula.</li>
<li>config.json = json format file with extra parameters for our snakemake file to use.</li>
<li>cluster.json = json format file with specification for running on the HPC</li>
<li>samples.txt = file we will use later relating to the config.json file.</li>
</ul><p><span>Run the snakemake file as a dry run (the example workflow shown above).</span></p><ul>
<li>This will build a DAG of the jobs to be run without actually executing them.</li>
<li><code>snakemake --dry-run</code></li>
</ul><p>User can e<span>xecute rules of interest.</span></p><ul>
<li><code>snakemake --dry-run all</code>&nbsp;VS.&nbsp;<code>snakemake --dry-run call</code>&nbsp;VS.&nbsp;<code>snakemake --dry-run bwa</code></li>
</ul><p><span>Run the snakemake file in order to produce an image of the DAG of jobs to be run.</span></p><ul>
<li><code>snakemake --dag | dot -Tsvg &gt; dag.svg</code>&nbsp;OR&nbsp;<code>snakemake --dag | dot -Tsvg &gt; dag.svg</code></li>
</ul><p>Run the snakemake (this time not as a dry run)</p><ol>
<li><code>snakemake --use-conda</code></li>
</ol>]]></description>
	<dc:creator>Abhi</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/44675/variant-calling-pipeline</guid>
	<pubDate>Sat, 19 Oct 2024 12:23:40 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/44675/variant-calling-pipeline</link>
	<title><![CDATA[Variant Calling Pipeline]]></title>
	<description><![CDATA[<p dir="auto">The&nbsp;<a href="https://github.com/Tom-Jenkins/maerl-wgs-pipelines/blob/main/src/variantcalling.nf"><code>variantcalling.nf</code></a>&nbsp;nextflow script will take any number of samples with paired-end reads in FASTQ format, map reads using Bowtie2, process BAM files, and finally call variants using BCFtools v1.21 and/or Freebayes v1.3.6. If part of the pipeline is unsuccessful for a sample then these errors are ignored.</p>
<p dir="auto">Pipeline flowchart:</p>
<div dir="auto">
<div dir="auto">
<div>&nbsp;</div>
<div></div>
</div>
<div>&nbsp;</div>
<div dir="auto">
<h2 dir="auto">Dependencies (version tested)</h2>
<a href="https://github.com/Tom-Jenkins/nextflow-pipelines/blob/main/docs/variant-calling.md#dependencies-version-tested"></a></div>
<ul dir="auto">
<li>Nextflow (24.04.4)</li>
<li>Java (18.0.2.1)</li>
<li>Python (3.10)</li>
<li>Perl (5.32.1)</li>
<li>Bowtie2 (2.5.3)</li>
<li>SAMtools (1.19.2)</li>
<li>GATK4 (4.5)</li>
<li>BCFtools (1.21)</li>
<li>Freebayes (1.3.6)</li>
</ul>
</div><p>Address of the bookmark: <a href="https://github.com/Tom-Jenkins/nextflow-pipelines/blob/main/docs/variant-calling.md" rel="nofollow">https://github.com/Tom-Jenkins/nextflow-pipelines/blob/main/docs/variant-calling.md</a></p>]]></description>
	<dc:creator>LEGE</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/34525/hic-pro-an-optimized-and-flexible-pipeline-for-hi-c-data-processing</guid>
	<pubDate>Wed, 06 Dec 2017 01:05:21 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/34525/hic-pro-an-optimized-and-flexible-pipeline-for-hi-c-data-processing</link>
	<title><![CDATA[HiC-Pro: an optimized and flexible pipeline for Hi-C data processing]]></title>
	<description><![CDATA[<p><span>HiC-Pro was designed to process Hi-C data, from raw fastq files (paired-end Illumina data) to the normalized contact maps. Since version 2.7.0, HiC-Pro supports the main Hi-C protocols, including digestion protocols as well as protocols that do not require restriction enzyme such as DNase Hi-C. In practice, HiC-Pro can be used to process dilution Hi-C, in situ Hi-C, DNase Hi-C, Micro-C, capture-C, capture Hi-C or HiChip data.</span></p>
<p>&nbsp;</p>
<p>http://nservant.github.io/HiC-Pro/</p><p>Address of the bookmark: <a href="http://nservant.github.io/HiC-Pro/" rel="nofollow">http://nservant.github.io/HiC-Pro/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/38666/mcat-motif-combining-and-association-tool</guid>
	<pubDate>Sun, 13 Jan 2019 06:27:28 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/38666/mcat-motif-combining-and-association-tool</link>
	<title><![CDATA[MCAT: Motif Combining and Association Tool]]></title>
	<description><![CDATA[<p>This is a pipeline for finding motifs in fasta files.<br>It can be run from the command line as follows:</p>
<p>usage: orange_pipeline_refine.py [-h] [-w W] [--nmotifs NMOTIFS] [--iter ITER] [-c C]<br>[-s S] [-d] [-ff] [-v V]<br>positive_seq negative_seq</p>
<p>positional arguments:<br>positive_seq the fasta file for the positive sequences<br>negative_seq the fasta file for the negative sequences</p>
<p>&nbsp;</p><p>Address of the bookmark: <a href="https://github.com/yanshen43/MCAT" rel="nofollow">https://github.com/yanshen43/MCAT</a></p>]]></description>
	<dc:creator>Neel</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/40409/haplotypo-a-variant-calling-pipeline-for-phased-genomes</guid>
	<pubDate>Thu, 19 Dec 2019 07:33:40 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/40409/haplotypo-a-variant-calling-pipeline-for-phased-genomes</link>
	<title><![CDATA[HaploTypo: a variant-calling pipeline for phased genomes]]></title>
	<description><![CDATA[<p>An increasing number of phased (i.e. with resolved haplotypes) reference genomes are available. However, most genetic variant calling tools do not explicitly account for haplotype structure. Here, we present HaploTypo, a pipeline tailored to resolve haplotypes in genetic variation analyses. HaploTypo infers the haplotype correspondence for each heterozygous variant called on a phased reference genome.</p>
<div>Availability and Implementation</div>
<p>HaploTypo is implemented in Python 2.7 and Python 3.5, and is freely available at&nbsp;<a href="https://github.com/gabaldonlab/haplotypo" target="">https://github.com/gabaldonlab/haplotypo</a>, and as a Docker image.</p><p>Address of the bookmark: <a href="https://github.com/gabaldonlab/haplotypo" rel="nofollow">https://github.com/gabaldonlab/haplotypo</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/41675/gapfinisher-a-reliable-gap-filling-pipeline-for-sspace-longread-scaffolder-output</guid>
	<pubDate>Thu, 14 May 2020 15:13:30 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/41675/gapfinisher-a-reliable-gap-filling-pipeline-for-sspace-longread-scaffolder-output</link>
	<title><![CDATA[gapFinisher: A reliable gap filling pipeline for SSPACE-LongRead scaffolder output]]></title>
	<description><![CDATA[<p>gapFinisher to process SSPACE-LongRead output to fill gaps after the scaffolding. gapFinisher is based on the controlled use of a previously published gap filling tool FGAP and works on all standard Linux/UNIX command lines.</p>
<p>https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6733440/</p><p>Address of the bookmark: <a href="https://github.com/kammoji/gapFinisher" rel="nofollow">https://github.com/kammoji/gapFinisher</a></p>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/43384/lncpipea-nextflow-based-pipeline-for-comprehensive-analyses-of-long-non-coding-rnas-from-rna-seq-datasets</guid>
	<pubDate>Fri, 17 Sep 2021 01:57:02 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/43384/lncpipea-nextflow-based-pipeline-for-comprehensive-analyses-of-long-non-coding-rnas-from-rna-seq-datasets</link>
	<title><![CDATA[LncPipe:A Nextflow-based pipeline for comprehensive analyses of long non-coding RNAs from RNA-seq datasets]]></title>
	<description><![CDATA[<p><span>The pipeline was developed based on a popular workflow framework&nbsp;</span><a href="https://github.com/nextflow-io/nextflow">Nextflow</a><span>, composed of four core procedures including reads alignment, assembly, identification and quantification. It contains various unique features such as well-designed lncRNAs annotation strategy, optimized calculating efficiency, diversified classification and interactive analysis report.&nbsp;</span><a href="https://github.com/likelet/LncPipe">LncPipe</a><span>&nbsp;allows users additional control in interuppting the pipeline, resetting parameters from command line, modifying main script directly and resume analysis from previous checkpoint.</span></p>
<p>Ref&nbsp;https://www.lncrnablog.com/lncpipe-a-nextflow-based-pipeline-for-identification-and-analysis-of-long-non-coding-rnas-from-rna-seq-data/</p>
<p><img src="https://ars.els-cdn.com/content/image/1-s2.0-S1673852718301176-gr1.jpg" alt="image" style="border: 0px;"></p><p>Address of the bookmark: <a href="https://github.com/likelet/LncPipe" rel="nofollow">https://github.com/likelet/LncPipe</a></p>]]></description>
	<dc:creator>LEGE</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/44597/imagine-in-silico-metagenomics-pipeline</guid>
	<pubDate>Sat, 06 Jul 2024 04:32:18 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/44597/imagine-in-silico-metagenomics-pipeline</link>
	<title><![CDATA[iMAGine - in silico MetAGenomics pipeline]]></title>
	<description><![CDATA[<p dir="auto"><span>iMAGine</span>&nbsp;is a metagenomic workflow which includes filtering, assembling, and binning.</p>
<p dir="auto">This workflow includes the following tools which are needed to be installed in the system.</p>
<ol dir="auto">
<li><a href="https://github.com/OpenGene/fastp">fastp</a></li>
<li><a href="https://github.com/ablab/spades">spades assembler</a></li>
<li><a href="https://github.com/ablab/quast">QUAST</a></li>
<li><a href="https://github.com/lh3/bwa">bwa</a></li>
<li><a href="https://github.com/samtools/samtools">samtools</a></li>
<li><a href="https://bitbucket.org/berkeleylab/metabat/src/master/">metabat2</a></li>
<li><a href="https://github.com/Ecogenomics/CheckM">CheckM</a></li>
</ol><p>Address of the bookmark: <a href="https://github.com/avishekdutta14/iMAGine" rel="nofollow">https://github.com/avishekdutta14/iMAGine</a></p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/3013/python-and-biopython-tutorial</guid>
	<pubDate>Fri, 23 Aug 2013 06:47:40 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/3013/python-and-biopython-tutorial</link>
	<title><![CDATA[Python and BioPython Tutorial]]></title>
	<description><![CDATA[<p>A quickstart tutorial that allows to become familiar with the Python language. The exercises expect knowledge of basic concepts of programming. A group of 2nd year computer science students with no previous Python knowledge required 60'-90' to complete the exercises. With about 3 hours time, the exercise is suitable for non-programmers as well.</p><p>Address of the bookmark: <a href="http://www.biotnet.org/training-materials/python-programmers" rel="nofollow">http://www.biotnet.org/training-materials/python-programmers</a></p>]]></description>
	<dc:creator>Manshi Raghubanshi</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/news/view/20331/type-hinting</guid>
	<pubDate>Fri, 09 Jan 2015 22:26:13 -0600</pubDate>
	<link>https://bioinformaticsonline.com/news/view/20331/type-hinting</link>
	<title><![CDATA[Type Hinting]]></title>
	<description><![CDATA[<p>Python creator Guido van Rossum&rsquo;s proposal for static type-checking annotations is inching closer to reality, and the feature has taken on a new name: type hinting.</p><p><img src="http://sdtimes.com/wp-content/uploads/2015/01/0107.sdt-python-typehinting.png" alt="image" width="619" height="219" style="border: 0px; border: 0px;"></p><p>Back in August, van Rossum published a proposal on the Python mailing list recommending type-checking annotations as a valuable feature for the next version of Python to improve the performance of editors and IDEs, linter capabilities, standard notation, and refactoring. Van Rossum&rsquo;s <a href="http://lwn.net/Articles/627558/">latest proposal</a>, posted late last month, outlined plans to publish a Python Enhancement Proposal (PEP) in early January to put the feature now known as type hinting on track for inclusion in Python 3.5, slated for release this September.</p><p>Reference</p><p>https://quip.com/r69HA9GhGa7J</p>]]></description>
	<dc:creator>Pranjali Yadav</dc:creator>
</item>

</channel>
</rss>