mirror of
https://github.com/chanzuckerberg/cellxgene.git
synced 2026-09-25 09:38:11 +08:00
cziscience landing page (#1347)
* fix dead link in launch page * first cut at landing page * wording changes * add additional refinements * fixes from PR review
This commit is contained in:
@@ -16,10 +16,10 @@
|
||||
<meta property="og:url" content="http://localhost:4000/cellxgene/posts/troubleshooting.html" />
|
||||
<meta property="og:site_name" content="cellxgene" />
|
||||
<script type="application/ld+json">
|
||||
{"description":"Troubleshooting","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"http://localhost:4000/cellxgene/cellxgene-logo.png"}},"@type":"WebPage","url":"http://localhost:4000/cellxgene/posts/troubleshooting.html","headline":"Troubleshooting","@context":"http://schema.org"}</script>
|
||||
{"description":"Troubleshooting","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"http://localhost:4000/cellxgene/cellxgene-logo.png"}},"@type":"WebPage","headline":"Troubleshooting","url":"http://localhost:4000/cellxgene/posts/troubleshooting.html","@context":"http://schema.org"}</script>
|
||||
<!-- End Jekyll SEO tag -->
|
||||
|
||||
<link rel="stylesheet" href="/cellxgene/assets/css/style.css?v=d2171b9a2f9935b8b92c3103c93405d1d74ef2b3">
|
||||
<link rel="stylesheet" href="/cellxgene/assets/css/style.css?v=88411ae4b44d899609d211ed2db5c41e4fba3068">
|
||||
<!--[if lt IE 9]>
|
||||
<script src="https://cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv.min.js"></script>
|
||||
<![endif]-->
|
||||
@@ -85,6 +85,10 @@
|
||||
<a href="/cellxgene/posts/contact" class="btn">Contact & finding help</a><br>
|
||||
|
||||
|
||||
|
||||
<a href="/cellxgene/posts/cellxgene_cziscience_com" class="btn">cellxgene.cziscience.com</a><br>
|
||||
|
||||
|
||||
|
||||
<a href="https://github.com/chanzuckerberg/cellxgene" class="btn" target="_blank">Code</a>
|
||||
</p>
|
||||
@@ -93,18 +97,18 @@
|
||||
<section>
|
||||
<h1 id="troubleshooting-tips--tricks">Troubleshooting tips & tricks</h1>
|
||||
|
||||
<h4 id="i-tried-to-pip-install-cellxgene-and-got-a-weird-error-i-dont-understand">I tried to <code class="highlighter-rouge">pip install cellxgene</code> and got a weird error I don’t understand</h4>
|
||||
<h4 id="i-tried-to-pip-install-cellxgene-and-got-a-weird-error-i-dont-understand">I tried to <code class="language-plaintext highlighter-rouge">pip install cellxgene</code> and got a weird error I don’t understand</h4>
|
||||
|
||||
<p>This may happen, especially as we work out bugs in our installation process! Please create a new <a href="https://github.com/chanzuckerberg/cellxgene/issues">Github issue</a>, explain what you did, and include all the error messages you saw. It’d also be super helpful if you call <code class="highlighter-rouge">pip freeze</code> and include the full output alongside your issue.</p>
|
||||
<p>This may happen, especially as we work out bugs in our installation process! Please create a new <a href="https://github.com/chanzuckerberg/cellxgene/issues">Github issue</a>, explain what you did, and include all the error messages you saw. It’d also be super helpful if you call <code class="language-plaintext highlighter-rouge">pip freeze</code> and include the full output alongside your issue.</p>
|
||||
|
||||
<h4 id="i-have-a-big-dataset-how-can-i-make-cellxgene-run-as-fast-as-possible">I have a BIG dataset, how can I make cellxgene run as fast as possible?</h4>
|
||||
|
||||
<p>If your dataset requires gigabytes of disk space, you may need to select an appropriate storage format in order to effectively utilize <code class="highlighter-rouge">cellxgene</code>. Tips and tricks:</p>
|
||||
<p>If your dataset requires gigabytes of disk space, you may need to select an appropriate storage format in order to effectively utilize <code class="language-plaintext highlighter-rouge">cellxgene</code>. Tips and tricks:</p>
|
||||
|
||||
<ul>
|
||||
<li><code class="highlighter-rouge">cellxgene</code> is optimized for columnar data access. For large datasets, format the expression matrix (<code class="highlighter-rouge">.X</code>) as either a <a href="https://docs.scipy.org/doc/scipy/reference/generated/scipy.sparse.csc_matrix.html">SciPy CSC sparse matrix</a> or a dense Numpy array (whichever creates a smaller <code class="highlighter-rouge">h5ad</code> file). If you are using <code class="highlighter-rouge">cellxgene prepare</code>, include the <code class="highlighter-rouge">--sparse</code> flag to ensure <code class="highlighter-rouge">.X</code> is formatted as a CSC sparse matrix (by default, <code class="highlighter-rouge">.X</code> will be a dense matrix).</li>
|
||||
<li>By default, <code class="highlighter-rouge">cellxgene</code> loads the dataset into memory, and start time is directly proportional to <code class="highlighter-rouge">h5ad</code> file size and the speed of your file system. Expect that large (e.g., million cell) datasets will take minutes to load, even on relatively fast computers with a high performance local hard drive. Once loaded, exploring metadata should still be quick. If this start time is a problem, try the <code class="highlighter-rouge">--backed</code> flag, which will attempt to lazily load data as needed (caveat: subsequent data access may be slower).</li>
|
||||
<li>If your dataset size exceeds the size of memory (RAM) on the host computer, differential expression calculations will be extremely slow (or fail, if you run out of virtual memory). In this case, we recommend running with the <code class="highlighter-rouge">--disable-diffexp</code> flag. For datasets that are extremely large, you may also find the <code class="highlighter-rouge">--backed</code> flag improves your ability to explore them.</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">cellxgene</code> is optimized for columnar data access. For large datasets, format the expression matrix (<code class="language-plaintext highlighter-rouge">.X</code>) as either a <a href="https://docs.scipy.org/doc/scipy/reference/generated/scipy.sparse.csc_matrix.html">SciPy CSC sparse matrix</a> or a dense Numpy array (whichever creates a smaller <code class="language-plaintext highlighter-rouge">h5ad</code> file). If you are using <code class="language-plaintext highlighter-rouge">cellxgene prepare</code>, include the <code class="language-plaintext highlighter-rouge">--sparse</code> flag to ensure <code class="language-plaintext highlighter-rouge">.X</code> is formatted as a CSC sparse matrix (by default, <code class="language-plaintext highlighter-rouge">.X</code> will be a dense matrix).</li>
|
||||
<li>By default, <code class="language-plaintext highlighter-rouge">cellxgene</code> loads the dataset into memory, and start time is directly proportional to <code class="language-plaintext highlighter-rouge">h5ad</code> file size and the speed of your file system. Expect that large (e.g., million cell) datasets will take minutes to load, even on relatively fast computers with a high performance local hard drive. Once loaded, exploring metadata should still be quick. If this start time is a problem, try the <code class="language-plaintext highlighter-rouge">--backed</code> flag, which will attempt to lazily load data as needed (caveat: subsequent data access may be slower).</li>
|
||||
<li>If your dataset size exceeds the size of memory (RAM) on the host computer, differential expression calculations will be extremely slow (or fail, if you run out of virtual memory). In this case, we recommend running with the <code class="language-plaintext highlighter-rouge">--disable-diffexp</code> flag. For datasets that are extremely large, you may also find the <code class="language-plaintext highlighter-rouge">--backed</code> flag improves your ability to explore them.</li>
|
||||
</ul>
|
||||
|
||||
<h4 id="im-following-the-developer-instructions-and-get-an-error-about-missing-files-and-directories-when-trying-to-build-the-client">I’m following the developer instructions and get an error about “missing files and directories” when trying to build the client</h4>
|
||||
|
||||
Reference in New Issue
Block a user