Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a config schema to map tracks to a MSA location, to help bridge LGV and MSA views #25

Open
cmdcolin opened this issue Apr 29, 2021 · 0 comments

Comments

@cmdcolin
Copy link
Contributor

A config.json file may have something like this

diff --git a/test_data/config_demo.json b/test_data/config_demo.json
index 42b82a680..80218c1a1 100644
--- a/test_data/config_demo.json
+++ b/test_data/config_demo.json
@@ -72,6 +72,11 @@
       }
     }
   ],
+  "configuration": {
+    "msaView": {
+      "ncbi_gff_hg19": "msaView_{geneName}.msa"
+    }
+  },
   "tracks": [
     {
       "type": "FeatureTrack",


This would allow the msaview to know that the ncbi_gff_hg19 track is associated with msa files with the format msaView_{geneName}.msa or some similar remote API with a format like this e.g. rest.ensembl.org/msa/?gene={geneName}

It would be difficult to add this information directly to the track config itself, because it would need a separate config slot, but having it as a top level config with trackId->msa mappings may help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant