Here is my prior example. I confirmed everything is still working exactly the same. Notice how I pulled in all the core data needed for this and some extra reference data most people will like to have around (consider that optional).
This should be simplified enough for students to do but please ask about any questions.
So, three potential solutions
- Do the query at UCSC, and send the results to Galaxy
- Query the index from UCSC and send that to Galaxy, then use tools in Galaxy (extract block, stitch blocks, other MAF functions)
- Maybe more, but let us know about the mm9/mm10 question. Hg19-mm10 is possible but we do not plan to load the other pairwise data, just the N-way types of data indexes. So this option would involve the hg19 100-way I linked above. This may not be immediate, but we do want to be responsive to requests if this is something people will find useful.
And one more…
- Use the hg38-30way hosted on the UseGalaxy servers as a native index. The species included are in the readme where the data was sourced → Index of /goldenPath/hg38/multiz30way