Macdonald, J. M. | bioRxiv Science

bioRxiv2026

Sequential Penta-Omic Extraction Method Using Single Biospecimens of Post-mortem Human Brain

A multi-omic approach utilizing a single biospecimen is important to avoid intra-sample heterogeneity associated with testing multiple omic single-samples, and for more efficient use of small volumes of precious biopsies (<30 mg). This is especially true for the microanatomy of post-mortem human brain samples. Using post-mortem human brain biospecimens from the NIH NeuroBioBank, a penta-omic sequential extraction method is described, Simultaneous Metabolomic, Proteomic, Lipidomic - DNA, RNA Extraction (SiMPL-DREx). Each sequential omic extract was compared to those obtained by the gold standard single omic method. Preserving RIN is critical for brain and tissue banks, as it is a primary measure of tissue quality. For all five omic extracts, the tissue integrity numbers and omic profiles did not significantly differ from those obtained by the respective omic gold standard method. Unlike past multi-omic studies, this study quantified the relative solvent percentages and upstream losses for both the organic and aqueous phases, confirming an omics loss of under 5%.

biochemistry↗

bioRxiv2018

HPCI: A Perl module for writing cluster-portable bioinformatics pipelines

BackgroundMost biocomputing pipelines are run on clusters of computers. Each type of cluster has its own API (application programming interface). That API defines how a program that is to run on the cluster must request the submission, content and monitoring of jobs to be run on the cluster. Sometimes, it is desirable to run the same pipeline on different types of cluster. This can happen in situations including when:\n\nO_LIdifferent labs are collaborating, but they do not use the same type of cluster\nC_LIO_LIa pipeline is released to other labs as open source or commercial software\nC_LIO_LIa lab has access to multiple types of cluster, and wants to choose between them for scaling, cost or other purposes\nC_LIO_LIa lab is migrating their infrastructure from one cluster type to another\nC_LIO_LIduring testing or travelling, it is often desired to run on a single computer\nC_LI\n\nHowever, since each type of cluster has its own API, code that runs jobs on one type of cluster needs to be re-written if it is desired to run that application on a different type of cluster. To resolve this problem, we created a software module to generalize the submission of pipelines across computing environments, including local compute, clouds and clusters.\n\nResultsHPCI (High Performance Computing Interface) is a Perl module that provides the interface to a standardized generic cluster.\n\nWhen the HPCI module is used, it accepts a parameter to specify the cluster type. The HPCI module uses this to load a driver HPCD:: . This is used to translate the abstract HPCI interface to the specific software interface.\n\nSimply by changing the cluster parameter, the same pipeline can be run on a different type of cluster with no other changes.\n\nConclusionThe HPCI module assists in writing Perl programs that can be run in different lab environments, with different site configuration requirements and different types of hardware clusters. Rather than having to re-write portions of the program, it is only necessary to change a configuration file.\n\nUsing HPCI, an application can manage collections of jobs to be runs, specify ordering dependencies, detect success or failure of jobs run and allow automatic retry of failed jobs (allowing for the possibility of a changed configuration such as when the original attempt specified an inadequate memory allotment).

bioinformatics↗