HelixProtX

Closed weights Baidu July 2024

No estimate

No hardware requirements for this model

The weights for this model have not been published, so it cannot be downloaded or run on your own hardware at any size. It is reachable only through its provider, and no graphics card changes that.

On record

Full specification

Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.

Origin

Who built this model, where, and when it was published.

Organisation
Baidu
Organisation type
Industry
Country
China
Published
12 July 2024
Authors
Zhiyuan Chen, Tianhao Chen, Chenggang Xie, Yang Xue, Xiaonan Zhang, Jingbo Zhou, Xiaomin Fang

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Biology
Task
Protein generation
Numerical format
BF16

Size

How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.

Training data
1,330,310,800 tokens

2168498 instances, 80% training data -> 1734798 estimated tokens per instance 512 1734798*512=888216576

Epochs
52

Training compute

The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.

How it was established
Hardware

The training run

What it physically took to train: which chips, how many, for how long, and what that drew from the wall.

Training hardware
NVIDIA A100 SXM4 40 GB
Chips used
8
Power draw
6.3 kW

Availability

Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.

Weights
Closed — provider access only
Model access
Unreleased

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Confident

Sources

Where this record came from and when it was last checked.

Reference
Unifying Sequences, Structures, and Descriptions for Any-to-Any Protein Generation with the Large Multimodal Model HelixProtX
Last updated
28 November 2025

What the numbers mean

What this model is

HelixProtX was published by Baidu, in the country recorded as China, during July 2024. The publishing organisation is categorised as industry.

It works in the domain of Biology, and is recorded as performing the task of protein generation.

Its weights were never published, so it can only be reached through its provider. No graphics card changes that.

Training and provenance

Training consumed a corpus of around 1,330,310,800 tokens of text.

Answers

HelixProtX — common questions

01

HelixProtX— who created it?

It was published by Baidu, based in China, an organisation categorised as industry.

02

HelixProtX— when was it released?

It was published in July 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

03

HelixProtX— what is it used for?

It works in the domain of Biology, and is recorded as handling the task of protein generation. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.

04

HelixProtX— what GPU do I need to run it?

None. This is a closed model — its weights were never published, so it cannot be downloaded or run on your own hardware at any price. It is reachable only through its provider.

05

HelixProtX— is it open source?

No. Its weights have not been published, so it exists only as a service controlled by its owner.

06

HelixProtX— how many parameters does it have?

No parameter count has been published for it, which is why no memory or speed figure appears on this page.

Source

Original publication

Record last updated 28 November 2025

The other direction

Looking at it from the other side?

This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.