yt documentation: field list

Hi In the new yt2.0 online documentation, the field_list page (http://yt.enzotools.org/doc/reference/field_list.html) no longer contains a list of just the field names. In the old 1.7 documentation there was a column on the left hand side that contained such a list with an in-page link to the more detailed descriptions. I found that to be very useful for quickly looking up what kind of fields are available in yt. Any chance we could bring such a list back? Mike -- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 601 Campbell Hall * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************

Hi Mike, Yes, absolutely. I'm planning on rebuilding and reuploading the docs tonight. I'll ensure there's a list of all the fields. As a quick sidenote, is it useful to have them split up into different pages based on the universality / code-specificity? Or should it all be a single humongous page? -Matt On Thu, Jan 27, 2011 at 5:05 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote:
Hi
In the new yt2.0 online documentation, the field_list page (http://yt.enzotools.org/doc/reference/field_list.html) no longer contains a list of just the field names. In the old 1.7 documentation there was a column on the left hand side that contained such a list with an in-page link to the more detailed descriptions. I found that to be very useful for quickly looking up what kind of fields are available in yt. Any chance we could bring such a list back?
Mike
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 601 Campbell Hall * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org

As a quick sidenote, is it useful to have them split up into different pages based on the universality / code-specificity?
I've actually found that to be a little annoying, since I had to look in two different places (Universal and Enzo), but it may have its utility for people who are using a variety of codes. I could imagine putting the applicability in parentheses next to the name, like so: AbsDivV (Universal) Temperature (Enzo, Orion, FLASH) But the temperature field demonstrates one problem with that: it has a different "Field Source" in each of the three codes... Mike On 01/27/2011 02:07 PM, Matthew Turk wrote:
Hi Mike,
Yes, absolutely. I'm planning on rebuilding and reuploading the docs tonight. I'll ensure there's a list of all the fields.
As a quick sidenote, is it useful to have them split up into different pages based on the universality / code-specificity? Or should it all be a single humongous page?
-Matt
On Thu, Jan 27, 2011 at 5:05 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote:
Hi
In the new yt2.0 online documentation, the field_list page (http://yt.enzotools.org/doc/reference/field_list.html) no longer contains a list of just the field names. In the old 1.7 documentation there was a column on the left hand side that contained such a list with an in-page link to the more detailed descriptions. I found that to be very useful for quickly looking up what kind of fields are available in yt. Any chance we could bring such a list back?
Mike
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 601 Campbell Hall * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 601 Campbell Hall * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************

Hi Mike, On Thu, Jan 27, 2011 at 5:17 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote:
As a quick sidenote, is it useful to have them split up into different pages based on the universality / code-specificity?
I've actually found that to be a little annoying, since I had to look in two different places (Universal and Enzo), but it may have its utility for people who are using a variety of codes. I could imagine putting the applicability in parentheses next to the name, like so:
AbsDivV (Universal) Temperature (Enzo, Orion, FLASH)
That's a better idea. I may not be able to get that into this build, but I'll work on it.
But the temperature field demonstrates one problem with that: it has a different "Field Source" in each of the three codes...
I do [now] think that it's still worthwhile to have a single page, as you pointed out. I will see if I can figure out a solution for this particular problem. -Matt
Mike
On 01/27/2011 02:07 PM, Matthew Turk wrote:
Hi Mike,
Yes, absolutely. I'm planning on rebuilding and reuploading the docs tonight. I'll ensure there's a list of all the fields.
As a quick sidenote, is it useful to have them split up into different pages based on the universality / code-specificity? Or should it all be a single humongous page?
-Matt
On Thu, Jan 27, 2011 at 5:05 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote:
Hi
In the new yt2.0 online documentation, the field_list page (http://yt.enzotools.org/doc/reference/field_list.html) no longer contains a list of just the field names. In the old 1.7 documentation there was a column on the left hand side that contained such a list with an in-page link to the more detailed descriptions. I found that to be very useful for quickly looking up what kind of fields are available in yt. Any chance we could bring such a list back?
Mike
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 601 Campbell Hall * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 601 Campbell Hall * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
participants (2)
-
Matthew Turk
-
Michael Kuhlen