Send Yt-dev mailing list submissions to
yt-dev@lists.spacepope.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
or, via email, send a message with subject or body 'help' to
yt-dev-request@lists.spacepope.org
You can reach the person managing the list at
yt-dev-owner@lists.spacepope.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yt-dev digest..."
Today's Topics:
1. Verbosity Increase (Matthew Turk)
2. Re: Verbosity Increase (Stephen Skory)
3. Re: Verbosity Increase (j s oishi)
4. Re: Verbosity Increase (Britton Smith)
---------- Forwarded message ----------
From: Matthew Turk <matthewturk@gmail.com>
To: yt-dev@lists.spacepope.org
Date: Tue, 7 Dec 2010 10:10:15 -0800
Subject: [Yt-dev] Verbosity Increase
Hi all,
I would like to propose that we increase the verbosity of two operations:
1) When a parameter file is parsed, I would like several pieces of
information output via the "INFO" level of the logging handler. This
would be the current simulation time, the dimensions of the domain,
and any cosmological parameters.
2) When print_stats is called in the hierarchy, I would like to
include all of the cosmological parameters.
The reason I'm bringing this up rather than just changing it is that
in the past yt has (rightly) been accused of being too verbose (in
fact, it was one of the first things Jeff said to me the first time we
met to talk about yt!) and I don't want to increase that
unnecessarily. But, I feel strongly that as we move into more codes
we need to be more upfront about what yt thinks of a given simulation
output. I think that this will also help ensure that errors are
avoided.
+1/-1?
-Matt
---------- Forwarded message ----------
From: Stephen Skory <stephenskory@yahoo.com>
To: "yt-dev@lists.spacepope.org" <yt-dev@lists.spacepope.org>
Date: Tue, 7 Dec 2010 10:13:33 -0800 (PST)
Subject: Re: [Yt-dev] Verbosity Increase
+1.
Stephen Skory
stephenskory@yahoo.com
http://stephenskory.com/
510.621.3687 (google voice)
----- Original Message -----
> From:Matthew Turk <matthewturk@gmail.com>
> To:yt-dev@lists.spacepope.org
> Cc:
> Sent:Tuesday, December 7, 2010 11:10:15 AM
> Subject:[Yt-dev] Verbosity Increase
>
>
> Hi all,
I would like to propose that we increase the verbosity of two
> operations:
1) When a parameter file is parsed, I would like several
> pieces of
information output via the "INFO" level of the logging
> handler. This
would be the current simulation time, the dimensions of
> the domain,
and any cosmological parameters.
2) When print_stats is called
> in the hierarchy, I would like to
include all of the cosmological
> parameters.
The reason I'm bringing this up rather than just changing it
> is that
in the past yt has (rightly) been accused of being too verbose
> (in
fact, it was one of the first things Jeff said to me the first time
> we
met to talk about yt!) and I don't want to increase
> that
unnecessarily. But, I feel strongly that as we move into more
> codes
we need to be more upfront about what yt thinks of a given
> simulation
output. I think that this will also help ensure that errors
> are
avoided.
+1/-1?
-Matt
_______________________________________________
Yt-dev
> mailing list
> href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
---------- Forwarded message ----------
From: j s oishi <jsoishi@gmail.com>
To: yt-dev@lists.spacepope.org
Date: Tue, 7 Dec 2010 10:21:14 -0800
Subject: Re: [Yt-dev] Verbosity Increase
These kinds of simulation parameters are good to print. I'm a solid
+1
on both of these changes. I also love print_stats, and having more
data there is a good thing.
j
On Tue, Dec 7, 2010 at 10:10 AM, Matthew Turk <matthewturk@gmail.com> wrote:
> Hi all,
>
> I would like to propose that we increase the verbosity of two operations:
>
> 1) When a parameter file is parsed, I would like several pieces of
> information output via the "INFO" level of the logging handler. This
> would be the current simulation time, the dimensions of the domain,
> and any cosmological parameters.
> 2) When print_stats is called in the hierarchy, I would like to
> include all of the cosmological parameters.
>
> The reason I'm bringing this up rather than just changing it is that
> in the past yt has (rightly) been accused of being too verbose (in
> fact, it was one of the first things Jeff said to me the first time we
> met to talk about yt!) and I don't want to increase that
> unnecessarily. But, I feel strongly that as we move into more codes
> we need to be more upfront about what yt thinks of a given simulation
> output. I think that this will also help ensure that errors are
> avoided.
>
> +1/-1?
>
> -Matt
> _______________________________________________
> Yt-dev mailing list
> Yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
---------- Forwarded message ----------
From: Britton Smith <brittonsmith@gmail.com>
To: yt-dev <yt-dev@lists.spacepope.org>
Date: Tue, 7 Dec 2010 13:29:00 -0500
Subject: Re: [Yt-dev] Verbosity Increase
+1On Tue, Dec 7, 2010 at 1:21 PM, j s oishi <jsoishi@gmail.com> wrote:
These kinds of simulation parameters are good to print. I'm a solid
+1
on both of these changes. I also love print_stats, and having more
data there is a good thing.
j
On Tue, Dec 7, 2010 at 10:10 AM, Matthew Turk <matthewturk@gmail.com> wrote:
> Hi all,
>
> I would like to propose that we increase the verbosity of two operations:
>
> 1) When a parameter file is parsed, I would like several pieces of
> information output via the "INFO" level of the logging handler. This
> would be the current simulation time, the dimensions of the domain,
> and any cosmological parameters.
> 2) When print_stats is called in the hierarchy, I would like to
> include all of the cosmological parameters.
>
> The reason I'm bringing this up rather than just changing it is that
> in the past yt has (rightly) been accused of being too verbose (in
> fact, it was one of the first things Jeff said to me the first time we
> met to talk about yt!) and I don't want to increase that
> unnecessarily. But, I feel strongly that as we move into more codes
> we need to be more upfront about what yt thinks of a given simulation
> output. I think that this will also help ensure that errors are
> avoided.
>
> +1/-1?
>
> -Matt
> _______________________________________________
> Yt-dev mailing list
> Yt-dev@lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org