omicverse-single-cell-sctour-trajectory

Compute scTour pseudotime, latent embeddings, and vector-field outputs from raw-count AnnData.

13|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Starlitnightly/omicverse-skills --skill omicverse-single-cell-sctour-trajectory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omicverse-single-cell-sctour-trajectory
Source: https://github.com/Starlitnightly/omicverse-skills/tree/main/src/omicverse_skills/skills/single-cell-sctour-trajectory
Command: npx skills add https://github.com/Starlitnightly/omicverse-skills --skill omicverse-single-cell-sctour-trajectory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Provide a focused, trainer-based trajectory inference path that computes scTour pseudotime, latent-space embeddings, and vector-field outputs from raw-count single-cell AnnData when graph-based methods are not appropriate or the sctour backend is required.

Core Features & Use Cases

  • Produces notebook-aligned outputs: a pseudotime column in adata.obs, mixed latent embeddings in adata.obsm['X_TNODE'], and a vector field in adata.obsm['X_VF'].
  • Ensures the wrapper uses a negative-binomial loss path by requiring raw UMI counts in adata.X and documents constraints when the external sctour package is unavailable.
  • Use cases include developmental pseudotime estimation, latent dynamics analysis, and vector-field visualization for datasets that need trainer-based latent dynamics rather than graph diffusion methods.

Quick Start

Run sctour on my raw-count AnnData to produce sctour_pseudotime, X_TNODE, and X_VF and write them into adata.obs and adata.obsm.

Frequently Asked Questions about omicverse-single-cell-sctour-trajectory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compute pseudotime and vector fields from raw-count AnnData?

To compute pseudotime and vector fields from raw-count AnnData, use a trainer-based trajectory inference method that processes raw UMI counts with a negative-binomial loss to generate latent embeddings and vector-field outputs.

What is scTour trajectory inference used for in single-cell analysis?

scTour trajectory inference is used for single-cell developmental pseudotime estimation, latent dynamics analysis, and vector-field visualization when datasets require trainer-based latent dynamics rather than graph diffusion methods.

Does trajectory inference with scTour require raw UMI counts in adata.X?

Yes, trajectory inference with scTour requires raw UMI counts present in adata.X because the wrapper uses a negative-binomial loss path to accurately compute pseudotime and latent-space embeddings.

What is the best way to estimate latent dynamics when graph-based methods are not appropriate?

When graph-based methods are not appropriate, the best way to estimate latent dynamics is using trainer-based trajectory inference that computes pseudotime, mixed latent embeddings, and vector fields directly from raw counts.

What outputs does scTour pseudotime analysis write to AnnData objects?

scTour pseudotime analysis writes a pseudotime column to adata.obs, mixed latent embeddings to adata.obsm['X_TNODE'], and a vector field to adata.obsm['X_VF'] for downstream analysis and plotting.

Why does single-cell trajectory inference fail if the sctour package is unavailable?

Single-cell trajectory inference fails if the sctour package is unavailable because the wrapper depends on this external package to execute the trainer-based inference and generate the required pseudotime and vector-field outputs.