JBrowse 2 dump: translate every organism's tracks.conf tracks to v5

未关闭
#268 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@jbrestel 已经在做这个了。

开始于 2026年11月12日。

评估

这个 Issue 还没有评估数据。

描述

Under VEuPathDB/agentic-project-management#5 (track configs at scale). Decision 0008 (John, 2026-11-11): every static tracks.conf track goes to v5. Today none does: the v5 dump only carries tracks the Perl producers emit, and these 122 tracks (pfal3D7 17 + 104 across 51 other organisms, Model/lib/jbrowse/<abbrev>/tracks.conf) are hand-written JBrowse 1 stanzas.

Approach: the dump reads each organism's tracks.conf and translates every stanza into a v5 track. One translator, no per-track code; tracks.conf stays the one list curators edit, now feeding JBrowse 1 and v5. JBrowse 1 is untouched (read only).

Rules:

  • Store class → v5 adapter by an explicit table: GFF3Tabix → Gff3TabixAdapter, BEDTabix → BedTabixAdapter, BigBed → BigBedAdapter, BigWig → BigWigAdapter (Quantitative), MultiBigWig → MultiWiggle (MultiQuantitative), BAM → BamAdapter (Alignments), GTF → v5's GTF adapter if beta.18 registers one.

  • REST stanzas: not translatable (v5 has no REST store); listed in the dump report, not emitted. Any other unknown store class fails the dump, so a newly curated track can't silently vanish.

  • Track contract (0007): trackId <abbrev>_<label> sanitized and deterministic; assemblyNames; locations stay store URLs; category from the stanza; passes the validator and jbrowse validate.

  • Styling callbacks in a stanza ({...} / function(...) colour, height, details): mapped to a VEuPathDBDisplay veupath* call when one exists, else stock; unmapped ones listed in the report.

  • Translator in JBrowseConfigRelease (hub build), with the store table and report

  • Tests per store class, REST skip, unknown-class failure, styling mapping

  • All 51 + pfal3D7 organisms translate; counts per kind vs 0008's table; REST list

  • Render checks: tgonME49 (35 tracks), tbruTREU927 (9), one signal and one microarray track

  • JBrowse 1 / Apollo output identical

  • PR merged

Starts after the full UniDB dump lands (VEuPathDB/ApiCommonModel#265).

主要语言
Perl
星标
1
派生
1
平均合并
1 小时 35 分钟
30 天内合并 PR
20

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

VEuPathDB/ApiCommonModel 的其他 Issue

查看 VEuPathDB/ApiCommonModel 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。