For more background see also the publication at BMC Bioinformatics.

https://github.com/clwgg/nQuire

Address of the bookmark: https://github.com/clwgg/nQuire

gapFinisher can fill gaps in draft genomes quickly and reliably.

Address of the bookmark: https://github.com/kammoji/gapFinisher

ADVERTISEMENT NO. 03/2014

PRINCIPAL SCIENTIST

Pay Band: Minimum pay of `43,000 in the PB-4 of `37400-67000/- + RGP of `10,000/-.

Age: The candidates must not have attained the age of 52 years as on 19.01.2015. There shall be no age limit for the Council’s employees.

ICAR-Indian Institute for Agricultural Biotechnology, (IIAB) Ranchi (Jharkhand)

151. Principal Scientist (Bioinformatics) (One post)

SENIOR SCIENTIST/PROGRAMME COORDINATOR

Pay Band: PB-4 of ` 37400-67000/- + RGP of ` 9,000/-.

Age: The candidates must not have attained the age of 47 years as on 19.01.2015. There shall be no age limit for the Council’s employees.

National Institute of Biotic Stress Management, Raipur (Chhattishgarh)

166. Senior Scientist (Bioinformatics) (One post)

IMPORTANT NOTE
I. (i) CLOSING DATE

THE CLOSING DATE FOR RECEIPT OF APPLICATIONS IN AGRICULTURAL SCIENTISTS RECRUITMENT BOARD IS 19.01.2015 (For applications posted from abroad and in the Andaman and Nicobar Islands, Lakshdweep, Minicoy and Amindivi islands, States/ Union Territories in the North-Eastern Region, Ladakh Division of J & K State, Sikkim, Pangi, Sub-division of Chamba, Lahul and Spiti Districts of Himachal Pradesh, the last date for receipt of application will be 02.02.2015). Non receipt of the application by the closing date will result in rejection of the application.

More Info: http://asrb.org.in/administrator/uploads_dir/1418978057english.pdf

Parliament2 runs a combination of tools to generate structural variant calls on whole-genome sequencing data. It can run the following callers: Breakdancer, Breakseq2, CNVnator, Delly2, Manta, and Lumpy. Because of synergies in how the programs use computational resources, these are all run in parallel. Parliament2 will produce the outputs of each of the tools for subsequent investigation.

Address of the bookmark: https://github.com/dnanexus/parliament2

Project Scientist-I
Experimental / Computation analysis experience in highthroughput genomics/ clinical application.

Project Manager
Experience in handling large biological projects involving high-throughput genomics/ clinical application.

Scientific Administrative Assistant
Lab Work.

More at https://vinodscaria.genomes.in/positionsopen

The "Ifs" of NGS QC and Trimming

1. Ensures Data Integrity
   If you want to minimize errors in downstream analyses, QC and trimming remove low-quality reads and bases, ensuring high-confidence data. This step is essential for reliable variant calling, assembly, and other applications.

2. Removes Contaminants
   If adapter sequences or contaminants are present in the raw reads, trimming can eliminate them. This prevents issues like misalignment or incorrect biological interpretations, ensuring cleaner data for analysis.

3. Improves Mapping and Assembly
   If your goal is better alignment to a reference genome or improved de novo assembly, trimming low-quality bases and adapters is critical. High-quality reads map more efficiently and generate more accurate assemblies.

4. Reduces Computational Load
   If you want to save computational resources, trimming reduces the dataset size, which speeds up processing and analysis. Clean datasets mean less computational time spent on processing low-quality data.

5. Prepares for Standardized Analyses
   If your project involves multiple datasets, QC and trimming ensure uniformity across them. This standardization makes comparisons valid and reproducible, particularly in large collaborative studies.

The "Buts" of NGS QC and Trimming

1. Risk of Over-Trimming
   But excessive trimming can lead to the loss of informative sequences, reducing read depth and potentially discarding biologically relevant data. This is especially critical in studies with limited sequencing depth.

2. Bias Introduction
   But trimming algorithms might introduce biases, especially if they inadvertently remove sequences with specific biological patterns. This can skew results and compromise biological insights.

3. Loss of Context in Paired-End Reads
   But trimming one read in a pair more than the other can lead to loss of pairing information. This complicates downstream analyses that rely on paired-end data, such as structural variant detection.

4. Time and Resource Intensive
   But running QC and trimming for large datasets can be computationally expensive and time-consuming. As sequencing depth increases, preprocessing becomes a bottleneck in the analysis pipeline.

5. Variable Standards
   But the criteria for trimming (e.g., quality threshold, minimum read length) can vary between tools and datasets. This variability may affect reproducibility and comparability of results across studies.

Balancing the "Ifs" and "Buts"

To maximize the benefits of QC and trimming while mitigating the challenges, consider the following best practices:

• Use QC Tools Wisely: Start with tools like FastQC to identify quality issues in your raw data. Visualizing quality metrics helps tailor your trimming parameters.

• Choose Reliable Trimming Tools: Tools like Trimmomatic, Cutadapt, and BBduk offer adaptive and customizable trimming options. Select one that aligns with your dataset and project goals.

• Set Reasonable Parameters: Avoid over-trimming by setting quality thresholds and minimum read lengths that balance data retention and quality improvement.

• Test Downstream Effects: Validate the impact of QC and trimming on downstream analyses, such as alignment efficiency, variant calling accuracy, or assembly quality.

• Document Your Workflow: Maintain detailed records of the parameters and tools used for QC and trimming. This ensures reproducibility and enables better troubleshooting.

Conclusion

NGS quality control and trimming are essential steps to ensure reliable and accurate data for analysis. While the "ifs" highlight the clear benefits of these steps, the "buts" remind us of the potential pitfalls. By adopting best practices and carefully balancing these considerations, you can optimize your preprocessing workflow and unlock the full potential of your sequencing data.

Reference

http://blog.bina.com/news/bina-technologies-acquired-by-roche?&__hssc=109677338.1.1419953400266&__hstc=109677338.b8350f2729889b08f1325906d5236cd3.1419953400266.1419953400266.1419953400266.1&hsCtaTracking=96cac941-9372-4bbf-bacb-3ca6f1ff8cfd|3fce0f18-835b-4086-9345-388880861732

http://www.the-scientist.com/?articles.view/articleNo/41750/title/Roche-Buys-Bioinformatics-Firm/

Address of the bookmark: https://github.com/broadinstitute/VariantBam

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’s latest proposal, 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.

Reference

https://quip.com/r69HA9GhGa7J