codonfm-finetune
Fine-tune public CodonFM Encodon checkpoints on labeled coding-sequence or coding-variant data using LoRA, head-only, or full fine-tuning. Use when a user explicitly asks to fine-tune CodonFM or Encodon for regression or classification. Support generic public-v1 Encodon workflows only; reject Decodo
- 0
- Installs
- —
- Rating
- —
- Success rate
- 9
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 77520775319d8d36… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Fine-tune public Encodon
Use --pretrained_ckpt_path for public v1. Do not substitute
--checkpoint_path: the public runner does not forward that argument to the
fine-tuning task.
Instructions
Resolve the target label, dataset, checkpoint, and output directory from the request and available files. Reuse existing data and weights. For training, check the project's ML dependencies and a compatible NVIDIA GPU before launch. If a required resource is unavailable, complete the available data preparation and return the command with the missing prerequisite clearly identified. When training is requested and the prerequisites are met, execute it and check the resulting checkpoints and metrics. A request for preparation ends with the validated inputs and command.
Use the user's labeled dataset when provided. For a demonstration of sequence regression without a dataset, use the public human RiboNN translation-efficiency data below and state that choice. This is not a substitute for a user's intended assay or for labeled coding variants. If variant labels are missing, return the required schema and a command template promptly; do not search for labels or invent measured effects.
Default demonstration checkpoint: nvidia/NV-CodonFM-Encodon-80M-v1, revision
399ca9fe17b57941a7bebc6788033919b417413c, file
NV-CodonFM-Encodon-80M-v1.safetensors with sibling config.json.
The public weights
are about 307 MB. Download them when needed for the requested work; input
preparation can record an intended checkpoint path. These are the original Encodon weights; the -TE-
checkpoints use the separate TransformerEngine implementation.
For an unsupported Decodon or missense-aggregation request, inspect the public parser/model configuration, explain the missing feature, and finish. Do not implement the missing model or search private repositories.
Examples
Prepare a small public-data example with the standard-library helper
prepare_ribonn.py, running from the repository root.
Set CODONFM_DATA_PATH to the CSV you want to create:
python skills/codonfm-finetune/scripts/prepare_ribonn.py \
--output "$CODONFM_DATA_PATH"
With an existing raw file, add --input "$RIBONN_DATA_PATH". The default reads
at most eight accepted rows per split; --max-rows-per-split 0 processes the full
input. Remote streaming has a time budget and no automatic retries; use a local
file if it fails. The helper follows the CDS slicing in the
RiboNN notebook:
- Read the upstream
.csvwith a tab delimiter. - Set
ref_seq = tx_sequence[utr5_size:utr5_size + cds_size],id = transcript_id, andvalue = mean_teunchanged. Do not take another logarithm. - Preserve source fold groups: 0–7 become
train, 8 becomesval, 9 becomestest. This is a demonstration holdout, not the notebook's cross-validation. - Exclude invalid/non-finite rows and CDSs exceeding 2046 codons instead of
silently truncating labeled examples. Record counts and source in the adjacent
.metadata.json. A small subset does not establish predictive performance.
The pinned dataset URL is in the helper; its source is CenikLab/TE_classic_ML. The notebook extracts frozen Encodon embeddings and trains a random-forest regressor with fold-based cross-validation. This skill reuses its data source, CDS extraction, and target for a separate fine-tuning example; it does not reproduce the notebook's training procedure or results.
Supported strategies
lora: adapter fine-tuning; default choice for smaller datasets.head_only_random: freeze the backbone and train a new head.head_only_pretrained: train an existing compatible pretrained head.full: update the complete model.
Accept only encodon_80m, encodon_600m, or encodon_1b.
Sequence-level regression or classification
Require id, ref_seq, value, and split columns. Extra columns are allowed.
Map the user's columns to this loader schema; the RiboNN helper is only for
RiboNN source data. Training needs train rows and, when validation is enabled,
val rows. A test split is needed only for later evaluation. Labels in unused
splits need not be populated. Regression targets must be finite numbers;
classification targets must be integer class indices from zero through
num_classes - 1. Use a downstream head for scalar targets.
Check sequence preparation with the user’s assay in mind. The loader converts
uppercase RNA U to T, and the tokenizer uppercases bases. Ambiguous bases and
incomplete codons can produce unknown tokens; overlength sequences are truncated.
Review these cases rather than silently dropping user records. Choose batches
and a training budget appropriate to the dataset; small training sets may be
resampled by the loader.
Set CODONFM_CHECKPOINT_PATH to the checkpoint file and CODONFM_RUN_DIR to
your chosen output directory. This example runs ten steps to check the workflow;
choose the training budget for the actual dataset and task:
python -m src.runner finetune \
--exp_name property_finetune \
--model_name encodon_80m \
--pretrained_ckpt_path "$CODONFM_CHECKPOINT_PATH" \
--data_path "$CODONFM_DATA_PATH" \
--process_item codon_sequence \
--dataset_name CodonBertDataset \
--finetune_strategy lora \
--lora_alpha 32 \
--lora_r 16 \
--lora_dropout 0.1 \
--loss_type regression \
--use_downstream_head \
--lr 2e-5 \
--max_steps 10 \
--warmup_iterations 1 \
--check_val_every_n_epoch 1 \
--train_batch_size 4 \
--val_batch_size 4 \
--num_workers 0 \
--num_nodes 1 \
--num_gpus 1 \
--out_dir "$CODONFM_RUN_DIR" \
--checkpoints_dir "$CODONFM_RUN_DIR/checkpoints"
For classification, replace --loss_type regression with
--loss_type classification and pass the correct --num_classes.
Generic coding-variant classification
Use MutationDataset only for an ordinary labeled variant head, not the newer
synonymous-codon aggregation loss. Require id, the reference-sequence column
(ref_seq by default), ref_codon, alt_codon, codon_position, and the chosen
label column. Select existing sequence/label columns with --ref_seq_col and
--label_col; these overrides apply to MutationDataset only. Starting from
the sequence-level command, change/add:
--process_item mutation_pred_mlm
--dataset_name MutationDataset
--label_col label
--loss_type classification
--num_classes 2
--use_downstream_head
--extract-seq
--mask_mutation
--train_val_test_ratio 0.8 0.1 0.1
Always keep --mask_mutation for masked-codon variant inputs.
Use --extract-seq to construct the context around a variant in a full CDS;
already prepared contexts can omit it. Choose split ratios for the dataset;
a held-out test split is optional for training. Public v1 reuses existing
train_idx.npy, val_idx.npy, and test_idx.npy files without checking that
they belong to the current CSV. Verify their provenance before reusing them.
Execute and outputs
Check prepared data directly against the selected loader's schema above using ordinary CSV inspection. Verify required columns, finite labels in the splits used for training, class indices when applicable, sequence preparation, and variant reference positions. The RiboNN helper checks its output during preparation. These checks do not require installing CodonFM's ML dependencies. For preparation requests, report what was checked and provide the training command. For execution requests, run it once data, weights, and compute are ready.
The existing runner has an optional --dryrun flag that
builds runtime configuration and skips execution. It requires the ML dependencies
and does not read the dataset or load weights. It is not a data-validation step
or a prerequisite for preparing inputs and commands.
Set validation frequency for the planned training length: for a small example,
--check_val_every_n_epoch 1 or a smaller --val_check_interval avoids public
v1's default interval of 1,000 batches exceeding an epoch.
- Checkpoints are written under the explicitly supplied
--checkpoints_dir, includinglast.ckptand configured best checkpoints. - CSV metrics are written below
--out_dir/<exp_name>/version_*unless W&B is enabled. - W&B requires
--enable_wandb,--project_name, and--entitytogether. - Fine-tuning does not produce prediction arrays; run an evaluation task separately against the resulting checkpoint.
Boundaries
- Do not use
MissenseDataset,missense_seq,missense_inference,missense_synom_agg, or any--missense_*flag. They are absent publicly. - Do not use Decodon model names, CLM preprocessing, organism tokens, or generation datasets.
- Require an explicit learning rate. Public v1 passes
lr=Noneotherwise. - Treat scientific and clinical validity as a separate validation problem; successful training does not certify the resulting model.
Files
9- BENCHMARK.md
89d7cd545f7.3 KB - SKILL.md
5b55cd91649.4 KB - agents/openai.yaml
79ecd99821233 B - evals/evals.json
610aa39a274.4 KB - evals/files/encodon_checkpoint.json
698fa354141.0 KB - evals/files/ribonn_smoke.provenance.json
4c23517940606 B - evals/files/variants_labeled.provenance.json
eb2eac28e7313 B - scripts/prepare_ribonn.py
8f0e0460ec6.1 KB - skill-card.md
d64aa99c5e4.7 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from NVIDIA/skills8
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and multi-GPU DataFrame workloads.
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Customize NVIDIA Nemotron Voice Agent's Generic Pipecat example for healthcare appointment, five-field patient intake, or custom tool-calling workflows without a separate backend.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, then runs calibration.
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
Calibrates pre-recorded `cam_*.mp4` datasets through the AutoMagicCalib REST API. Use for user-supplied local MP4s; route live RTSP streams to `amc-run-rtsp-calibration`.
Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key.
Related ai-ml skillsscan passed
Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.
Pair a remote AI agent with your browser. (gstack)
Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content. Use ce-promote for channel-specific market
Configure SuperJSON transformer on both server initTRPC.create({ transformer: superjson }) and every client terminating link (httpBatchLink, httpLink, wsLink, httpSubscriptionLink) to support Date, Map, Set, BigInt over the wire. Transformer must match on both sides. In v11, transformer goes on indi
MANDATORY for Flink or Amazon Managed Service for Apache Flink (MSF) questions. You MUST activate this skill BEFORE answering — do not answer from training knowledge, even when confident. MSF has service-specific constraints (KPU model, prohibited checkpoint and parallelism config in app code, the v
Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agent_memory/) and resolves project