iiinova — where your digital self keeps evolving

Reposted by EVOQUANT

EVOQUANT @evoquant.bsky.social · 21/04/2026

Heading to Stanford next week for #SDDS2026. In 7 months, Evoquant has built: - A 5.2M biosynthetic gene cluster atlas - An AI platform predicting natural product–target interactions - A wet-lab pipeline with confirmed bioactivity in 6/6 validation cases (15 in progress) 🧵

"A Platform for the Discovery of Novel Microbial Natural Product Chemical Scaffolds and Their Biological Targets"

152

EVOQUANT @evoquant.bsky.social · 21/04/2026

152

EVOQUANT @evoquant.bsky.social · 24/03/2026

The biosynthetic gene cluster universe (5 million BGCs)

Graph depiction the relation of 5 million BGCs

161

Reposted by EVOQUANT

EVOQUANT @evoquant.bsky.social · 27/02/2026

First extracts went out for antibiotic testing this week. Still waiting for some additional pipettes from Thermo Fisher (to the point they are sending loaners in the meantime) at which point we can finally start our anticancer and immune modulator assays.

Photo of PCR plate with chemical extracts

053

EVOQUANT @evoquant.bsky.social · 27/02/2026

053

EVOQUANT @evoquant.bsky.social · 13/02/2026

Claude is in a tizzy

$Given the user says both should be int, and chembl_id is a string, the molecule uid should likely be molregno. But in load_molecules, chembl_id is renamed to uid and used throughout. Let me check the compound section where ChemblMolecule(properties={"uid": row.chembl_id}) is used — that's a string. The user wants int, so these should use molregno instead, or the chembl_id should not be renamed. Actually, re-reading: the user is just saying the types are int — meaning str() wrapping on TAXID uid is wrong, and the chembl_id rename to uid in molecules is wrong (should keep molregno as uid). But wait — in the original code, molecules used chembl_id as uid too. And in compounds, ChemblMolecule(properties={"uid": row.chembl_id}) uses the string chembl_id.$

110

EVOQUANT @evoquant.bsky.social · 06/02/2026

Not enough people seem to be concerned about the cost of owning computers right now. The price of the RAM in Evoquant's workstation computer:

Alt text: Line chart showing a two-year price history for a computer component, with prices around $250–$320 through 2024–2025 before sharply rising above $1,100 by early 2026.

012

EVOQUANT @evoquant.bsky.social · 30/01/2026

Evoquant's first set of bacterial strains are growing. We now have several strains in culture as we begin evaluating our novel strategy for obtaining bioactive and novel natural products. Photo is of one of the strains growing on a minimal agar media.

Photo of bacteria colonies growing on agar

032

Reposted by EVOQUANT

EVOQUANT @evoquant.bsky.social · 18/01/2026

Evoquant received SBIR funding from the NIH in 2025 to develop new/better methods for finding anti-cancer and antibacterial small molecules produced by bacteria With success, we would apply for a Phase 2 grant, which would allow the company to stay alive & commercialize. Unfortunately...

the-scientist.com

The Federal Government’s Research Innovation Lifeline Has Gone Dark

Congressional inaction has led to the expiration of the federal government’s SBIR/STTR program, cutting off a biotechnology lifeline.

286

EVOQUANT @evoquant.bsky.social · 18/01/2026

the-scientist.com

The Federal Government’s Research Innovation Lifeline Has Gone Dark

Congressional inaction has led to the expiration of the federal government’s SBIR/STTR program, cutting off a biotechnology lifeline.

286

Reposted by EVOQUANT

chasingmicrobes @chasingmicrobes.bsky.social · 17/11/2025

I have been struggling with transfers in AWS between EC2 and S3 being way slower than the advertised EC2 bandwidth Last week I learned about: aws configure set s3.preferred_transfer_client crt and now transfers are super duper fast. The more you know

Otherwise, it resolves to classic. Between versions of the AWS CLI, auto resolution criteria may change. To guarantee use of a specific transfer client, set the preferred_transfer_client configuration variable to the appropriate transfer client listed below.

classic - Use the builtin, Python-based transfer client that supports all s3 commands, parameters, and most configuration values.

crt - Use the AWS Common Runtime (CRT) transfer client when possible. It is a C-based S3 transfer client that can improve transfer throughput. Currently, the CRT transfer client does not support all of the functionality available in the classic transfer client. The list below details what functionality is currently not supported by the crt transfer client option and the corresponding behavior of the AWS CLI if it is configured to prefer the crt transfer client:

S3 to S3 copies - Falls back to using the classic transfer client
Region redirects - Transfers fail for requests sent to a region that does not match the region of the targeted S3 bucket.
max_concurrent_requests, max_queue_size, multipart_threshold, and max_bandwidth configuration values - Ignores these configuration values.

031

EVOQUANT @evoquant.bsky.social · 16/09/2025

🚀 Evoquant has been awarded a $300k Small Business Grant from the National Institutes of Health for our project: "Leveraging Large-Scale Bioinformatics & AI for Natural Product Drug Discovery and Target Selection" Hitting the ground running 🏃and excited for the year to come!

Public Health Relevance Statement
This research addresses challenges in predicting bioactivity in natural product drug discovery by leveraging advanced AI, computational biology, and multi-omics knowledge graphs. This approach has the potential to accelerate the discovery of new, effective drugs for treating a range of conditions, including cancer, infections, and immune-related diseases, by identifying promising leads that could inform the next generation of therapeutics.

030