If I read in a dataset like: ds = yt.load("ActiveParticleCosmology/DD0046/DD0046") (that file is from the data page) and then do print ds.max_level it gives 99. This happens for the boxlib frontend too. Is there any meaning to the ds.max_level parameter? should we be setting it somewhere? or else remove it? As it is, it is confusing (and tempting to use it) seeing it there. -- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
Hi Mike, Once you do ds.index, it gets filled. That operation gets called lots of places, for instance any time you touch the data. For now maybe we should either make max_level call it (other parameters do this) or have it default to None. -Matt On Fri, Nov 21, 2014 at 3:48 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
If I read in a dataset like:
ds = yt.load("ActiveParticleCosmology/DD0046/DD0046")
(that file is from the data page)
and then do
print ds.max_level
it gives 99. This happens for the boxlib frontend too.
Is there any meaning to the ds.max_level parameter? should we be setting it somewhere? or else remove it? As it is, it is confusing (and tempting to use it) seeing it there.
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
It was my understanding that you could set it to limit the data you were selecting to truncate at a certain level. By setting to 99, it's effectively always selecting the highest res data. But maybe i'm wrong on this? Cameron On Fri, Nov 21, 2014 at 2:48 PM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:
If I read in a dataset like:
ds = yt.load("ActiveParticleCosmology/DD0046/DD0046")
(that file is from the data page)
and then do
print ds.max_level
it gives 99. This happens for the boxlib frontend too.
Is there any meaning to the ds.max_level parameter? should we be setting it somewhere? or else remove it? As it is, it is confusing (and tempting to use it) seeing it there.
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
Hi Cameron, It's a descriptive parameter, not prescriptive, and it defaults to 99 for some reason buried in the mists of time. I think it should just not be defined, or default to something more clearly not real, than give 99. -Matt On Fri, Nov 21, 2014 at 3:50 PM, Cameron Hummels <chummels@gmail.com> wrote:
It was my understanding that you could set it to limit the data you were selecting to truncate at a certain level. By setting to 99, it's effectively always selecting the highest res data. But maybe i'm wrong on this?
Cameron
On Fri, Nov 21, 2014 at 2:48 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
If I read in a dataset like:
ds = yt.load("ActiveParticleCosmology/DD0046/DD0046")
(that file is from the data page)
and then do
print ds.max_level
it gives 99. This happens for the boxlib frontend too.
Is there any meaning to the ds.max_level parameter? should we be setting it somewhere? or else remove it? As it is, it is confusing (and tempting to use it) seeing it there.
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Ok, that's interesting. Doing ds.index doesn't make it set for me with that same dataset. On Fri, Nov 21, 2014 at 4:50 PM, Cameron Hummels <chummels@gmail.com> wrote:
It was my understanding that you could set it to limit the data you were selecting to truncate at a certain level. By setting to 99, it's effectively always selecting the highest res data. But maybe i'm wrong on this?
Cameron
On Fri, Nov 21, 2014 at 2:48 PM, Michael Zingale < michael.zingale@stonybrook.edu> wrote:
If I read in a dataset like:
ds = yt.load("ActiveParticleCosmology/DD0046/DD0046")
(that file is from the data page)
and then do
print ds.max_level
it gives 99. This happens for the boxlib frontend too.
Is there any meaning to the ds.max_level parameter? should we be setting it somewhere? or else remove it? As it is, it is confusing (and tempting to use it) seeing it there.
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- Michael Zingale Associate Professor Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 *phone*: 631-632-8225 *e-mail*: Michael.Zingale@stonybrook.edu *web*: http://www.astro.sunysb.edu/mzingale
Sounds like a bug! I'll try issuing a fix shortly. On Fri, Nov 21, 2014 at 3:52 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
Ok, that's interesting.
Doing ds.index doesn't make it set for me with that same dataset.
On Fri, Nov 21, 2014 at 4:50 PM, Cameron Hummels <chummels@gmail.com> wrote:
It was my understanding that you could set it to limit the data you were selecting to truncate at a certain level. By setting to 99, it's effectively always selecting the highest res data. But maybe i'm wrong on this?
Cameron
On Fri, Nov 21, 2014 at 2:48 PM, Michael Zingale <michael.zingale@stonybrook.edu> wrote:
If I read in a dataset like:
ds = yt.load("ActiveParticleCosmology/DD0046/DD0046")
(that file is from the data page)
and then do
print ds.max_level
it gives 99. This happens for the boxlib frontend too.
Is there any meaning to the ds.max_level parameter? should we be setting it somewhere? or else remove it? As it is, it is confusing (and tempting to use it) seeing it there.
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- Cameron Hummels Postdoctoral Researcher Steward Observatory University of Arizona http://chummels.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- Michael Zingale Associate Professor
Dept. of Physics & Astronomy • Stony Brook University • Stony Brook, NY 11794-3800 phone: 631-632-8225 e-mail: Michael.Zingale@stonybrook.edu web: http://www.astro.sunysb.edu/mzingale
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
participants (3)
-
Cameron Hummels
-
Matthew Turk
-
Michael Zingale