Guillaume Gaullier<p><span class="h-card" translate="no"><a href="https://fediscience.org/@posertinlab" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>posertinlab</span></a></span> I have used <a href="https://fediscience.org/tags/CryoSPARC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CryoSPARC</span></a>'s tree view since forever because it's a lot easier to understand the relationships between jobs. Even when it was slow on large projects, I put up with it because this view is so helpful. Back when I learned single-particle <a href="https://fediscience.org/tags/cryoEM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryoEM</span></a>, with <a href="https://fediscience.org/tags/RELION" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RELION</span></a>, I used to draw the job graph by hand as I set up new jobs, so I could remain oriented within large projects.</p><p>The performance of the tree view in CryoSPARC 4.6 is really excellent, it's a big improvement in usability compared to previous versions.<br>Now the only thing that could make the tree view better is an export function as I described here: <a href="https://discuss.cryosparc.com/t/job-graph-figure/15228" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">discuss.cryosparc.com/t/job-gr</span><span class="invisible">aph-figure/15228</span></a></p>