Visualization specification: Is tsv the right choice?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 66
- Forks
- 16
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 10
Description
Regarding the visualization specification in PEtab1.0:
I was wondering whether the tsv format was really a good choice there. Currently each line in the visualization table corresponds to one data series. The lines are grouped into plots based on plotId. For each data series one can set plot-level properties such as axis labels, axis scaling, etc. This makes it unnecessarily complex, as only one of those values can actually be used. Maybe this would be better done in YAML in a future version, which would be more able to account for a hierarchical specification of plotting properties? Any opinions?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PEtab 1.0 visualization specification, focusing on the TSV table’s plotId grouping and plot-level properties. Compare whether a hierarchical YAML representation should replace or revise it; done requires a settled specification decision and documented scope, not just an opinion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100