New issue 697: when halo merger tree fails because it runs out of viable halos to track, give an appropriate error message
right now, when the halo merger tree runs out of halos as it tracks back in time (usually in the z>20 regime), it gives a generic error:
========== Cycle 00006 (z=29.999961) ==========
Traceback (most recent call last):
File "enzo.py", line 33, in <module>
File "/home/uni05/mlatif/ytnew/yt-x86_64/src/yt-hg/yt/analysis_modules/halo_merger_tree/enzofof_merger_tree.py", line 507, in save_halo_evolution
halo_id = self.levels[cycle_fin].halo_id
IndexError: list index out of range
It would be nice to have this give an error saying what actually happened--it ran out of halos!
New issue 696: change "how to get help" page into "what to do if you encounter problems" page
there are several things that users should try on their own when they encounter problems *before* contacting us. the presentation that both @ngoldbaum and i have given at a couple of yt demonstration sessions goes through this thought process well. nathan has the most up-to-date version of it available online:
i think we should move our "help" documents to "how to deal with problems" documents.
New issue 695: add subsection in developers docs on how to "dig into the source"
this is sort of a gray section in between yt use and yt development, so perhaps it is better left to the help docs (or at least linked from the help docs). it's for when a user cannot find what they're looking for in the documentation, or the api docs, and they need to just dig into yt and look around.
we need to lay out how the yt installer directory structure is laid out (it is partially done in: developing/developing.html#how-to-read-the-source-code , but it could be more explicit about the overall structure). we should also demonstrate the use of ``grin`` or ``grep -r`` and how one can find what they're looking for that way in the top of the source tree.
i think this is a good stepping stone between being a user and being a developer.
New issue 694: expound on how to read in arbitrary data formats into yt
in the loading grid data format section (examining/loading_data.html#loading-numpy-array), i think we should provide a few more examples of reading in from different file formats: HDF5, tab-delimited text, fits header, since this may be a major hurdle for non-astrophysical-code users in using yt.
New issue 688: Restructure Front Page of Docs
At doc sprint, we identified how to restructure the front page.
--What is yt, what data is supported? Three-pronged approach to computation.
--How do I install it?
--How to get started with yt: Bootcamp
--What can be done: Cookbook and Tutorials
--How to ask for help?
--How to develop in yt?