Cell Browser data flow and architecture: Difference between revisions
From Genecats
Jump to navigationJump to search
mNo edit summary |
|||
| Line 11: | Line 11: | ||
1. Data is first deposited in a dataset directory inside <code>/hive/data/inside/cells</code> on <code>hgwdev</code> and then gets built onto [https://cells-test.gi.ucsc.edu/ cells-test] using the command: | 1. Data is first deposited in a dataset directory inside <code>/hive/data/inside/cells</code> on <code>hgwdev</code> and then gets built onto [https://cells-test.gi.ucsc.edu/ cells-test] using the command: | ||
<pre> | <pre> | ||
# For datasets with no additional subsets | |||
cbBuild -o alpha | cbBuild -o alpha | ||
# For dataset collections you will use the recursive option "-r" | |||
cbBuild -r -o alpha | cbBuild -r -o alpha | ||
</pre> | </pre> | ||
Revision as of 23:07, 25 August 2022
How does data flow between the different machines?
How does building a cell browser work?
What files are copied over? Which ones are transformed into another format?
1. Data is first deposited in a dataset directory inside /hive/data/inside/cells on hgwdev and then gets built onto cells-test using the command:
# For datasets with no additional subsets cbBuild -o alpha # For dataset collections you will use the recursive option "-r" cbBuild -r -o alpha
2. The output files from cbBuild are placed inside /usr/local/apache/htdocs-cells. Note that the original configuration files and expression matrices inside the dataset directory are converted into either JSON or binary files (BIN). These files are used by the Cell Browser to ....... (help) build a cell browser.
