Input

Jabba takes as input a concatenated de Bruijn graph and a set of sequences:

the de Bruijn graph should appear in fasta format with 1 entry per node, the meta information should be in the format:
>NODE
the set of sequences should be in fasta or fastq format. These sequences will be corrected (e.g. PacBio reads). The corrections will be written to a file Jabba fasta.
The output is a file in fasta format with corrections of the long reads, and additionally a file in the input format containing uncorrected reads.

https://github.com/biointec/jabba/wiki

https://almob.biomedcentral.com/articles/10.1186/s13015-016-0075-7

Address of the bookmark: https://github.com/biointec/jabba

Address of the bookmark: http://www.genome.umd.edu/

Before you go down that path, consider this critical biological question:
Are you sequencing human cells—or bacterial contamination?

The Silent Saboteur: Mycoplasma in Cell Cultures

Mycoplasma contamination remains one of the most widespread and underdiagnosed issues in tissue culture work. Studies suggest that 15–35% of cell lines in use may be contaminated, often without visible signs. Unlike other microbial infections, Mycoplasma does not produce cloudiness, odor, or a change in pH. Many researchers won’t detect it unless they specifically test for it.

The consequences, however, are profound. Mycoplasma can significantly alter:

• Host gene expression patterns

• Cell proliferation rates

• Epigenetic profiles and chromatin accessibility

• Cytokine signaling and immune responses

In short, it can skew your results, compromise your biological conclusions, and invalidate weeks or months of research.

A Simple Diagnostic Step: Map Against Mycoplasma Genomes

If you encounter poor alignment rates to the human genome, consider mapping your reads to a Mycoplasma reference genome—or better yet, use a combined human + Mycoplasma reference. There have been cases where over half of all reads, initially assumed to be from human cells, were in fact bacterial in origin. This check is fast, easy, and could save your project.

How Contamination Happens—and Persists

Mycoplasma is small (0.1–0.3 μm), lacks a cell wall, and can pass through standard filters undetected. Common sources include:

• Contaminated reagents (e.g., FBS)

• Infected cell lines obtained from other labs

• Poor aseptic technique or shared equipment

Once present, it spreads quickly between cultures and can persist for months, silently affecting results.

Why Treatment Is Difficult

While antibiotics such as Plasmocin or BM-Cyclin are sometimes used, they often offer only partial resolution and may themselves alter cell behavior. In many cases, the best course of action is to discard the contaminated culture and start with a fresh, verified stock.

Practical Recommendations for Researchers

• Routinely test for Mycoplasma using PCR, qPCR, or fluorescence-based assays

• Incorporate contamination screens into your sequencing QC pipeline

• Use combined reference genomes when mapping ambiguous reads

• Practice strict aseptic technique and monitor all incoming cell lines

• Don’t ignore unexplained data anomalies—they might point to contamination

Closing Thought: Contamination Is a Biological Variable

It’s easy to view poor mapping as a technical issue, but sometimes the problem lies deeper—in the biology itself. Mycoplasma contamination doesn’t just interfere with sequencing; it interferes with science. As a research community, we must treat contamination not as an afterthought, but as a key variable to control.

So next time your reads won’t align, don’t just tune the aligner. Ask if your cells are telling the truth—or if they're hiding something.

Prerequisites

• A fresh Vultr Cloud Compute instance with Ubuntu 18.04 and root access.

Step 1: Install Apache, MySQL, and PHP

Elgg requires MySQL, PHP, and a web server. Before you can install Elgg, you will need to install the Apache web server, MySQL, and PHP.

Update the repository list.

apt-get update

Install the Apache web server.

apt-get install apache2 -y

Install MySQL.

apt-get install mysql-server -y

Complete the MySQL installation by executing the following command.

/usr/bin/mysql_secure_installation

During the installation, you will be asked to enter a root password. Enter a secure password. This will be the MySQL root password.

Would you like to setup VALIDATE PASSWORD plugin? [Y/N] N
New password: password
Re-enter new password: password
Remove anonymous users? [Y/N] Y
Disallow root login remotely? [Y/N] Y
Remove test database and access to it? [Y/N] Y
Reload privilege tables now? [Y/N] Y

Install PHP 7.2, as well as the PHP modules required by Elgg.

apt-get install php7.2 libapache2-mod-php7.2 php7.2-common php7.2-sqlite3 php7.2-curl php7.2-intl php7.2-mbstring php7.2-xmlrpc php7.2-mysql php7.2-gd php7.2-xml php7.2-cli php7.2-zip -y

Step 2: Create a MySQL database for Elgg

Elgg will require a MySQL database. Log into the MySQL console.

mysql -u root -p

When prompted for a password, enter the MySQL root password you set in step 1. Once you are logged in to the MySQL console, create a new database.

CREATE DATABASE elgg;

Create a new MySQL user and grant it privileges to the newly created database. You can replace username and password with the username and password of your choice.

GRANT ALL PRIVILEGES on elgg.* to 'username'@'localhost' identified by 'password';
FLUSH PRIVILEGES;

Exit the MySQL console.

exit

Step 3: Download and Install Elgg

Download the latest version of Elgg.

cd /var/www/html
rm -r index.html
wget https://elgg.org/download/elgg-2.3.7.zip

Unzip the downloaded archive and move the files to the root of the Apache web server.

apt install unzip
unzip elgg-2.3.7.zip
mv ./elgg-2.3.7/* . && rm elgg-2.3.7.zip && rm -r elgg-2.3.7

Create a data directory for Elgg.

sudo mkdir -p /var/www/html/data

Set the appropriate file permissions.

sudo chown -R www-data:www-data /var/www/html/
sudo chmod -R 755 /var/www/html/

Step 4: Configure Apache for Elgg

Elgg requires the Apache rewrite module. Enable the Apache rewrite module.

sudo a2enmod rewrite

Create an Apache configuration file for the Elgg installation.

sudo nano /etc/apache2/sites-available/elgg.conf

Paste the following snippet to the file, replacing example.com with your own domain name.

<VirtualHost *:80>
     DocumentRoot /var/www/html/
     ServerName example.com
     <Directory /var/www/html/>
          Options FollowSymlinks
          AllowOverride All
          Require all granted
     </Directory>
     ErrorLog ${APACHE_LOG_DIR}/error.log
     CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Enable the configuration and restart the Apache server.

 sudo a2ensite elgg.conf
 sudo systemctl restart apache2.service