https://github.com/keller-mark/vitessce-fom-config-proposals

https://github.com/keller-mark/vitessce-fom-config-proposals

Last synced: about 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/keller-mark/vitessce-fom-config-proposals
• Owner: keller-mark
• Created: 2022-05-25T19:26:24.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2022-06-01T13:40:17.000Z (over 2 years ago)
• Last Synced: 2024-10-12T15:17:39.347Z (3 months ago)
• Size: 46.9 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# vitessce-fom-config-proposals

This repository is meant to manually convert existing Vitessce configs to corresponding upgraded configs under the proposed feature-observation support (basically how they would look at the point when [#1128](https://github.com/vitessce/vitessce/issues/1128) can be closed).

While the upgrading will ultimately occur automatically, it may be a useful exercise to manually convert them and explore the diffs (especially for existing configs being used in the HuBMAP data portal).

The files with `.debug.json` suffixes have been obtained by adding the `debug=true` URL parameter to ensure that we are doing these comparisons both before and after view config initialization.

Existing configs will be on the `main` branch.

Proposed configs will be on separate branches to facilitate diffing with `main`.

[Compare](https://github.com/keller-mark/vitessce-fom-config-proposals/compare/main...keller-mark/fom)

Here I will not try to [break apart the spatial layers](https://github.com/vitessce/vitessce/issues/830) as I think that can be proposed/tackled independently.

For additional info, see these diagrams:

- [Data types and file types](https://docs.google.com/drawings/d/1dxDrtjm0Dax13czJbUUDTipj8EuhODHyIkRyizQCf9c/edit)

- [Data types and entity types](https://docs.google.com/drawings/d/1F1wp8QFMAmLgoIADUK4HOQ1__ECvsDnDCx4pBFnJJ74/edit)