[GRASS-dev] d.rast still noisy

d.rast is still noisy, even with the quiet flag. Can we turn this stuff off somehow?

d.rast agro_soils --q
WARNING: ‘cell/agro_soils’ was found in more mapsets (also found in user1).
WARNING: using ‘agro_soils@PERMANENT’.

Michael


Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Michael Barton wrote:

d.rast is still noisy, even with the quiet flag. Can we turn this
stuff off somehow?

d.rast agro_soils --q
WARNING: 'cell/agro_soils' was found in more mapsets (also found in
user1).
WARNING: using 'agro_soils@PERMANENT'.

WARNINGs are not affected by verbosity controls. The above warning is
there for a reason, as you have requested an ambiguous action.

Hamish

On 3/22/07, Hamish <hamish_nospam@yahoo.com> wrote:
[...]

WARNINGs are not affected by verbosity controls. The above warning is
there for a reason, as you have requested an ambiguous action.

In that case, warnings should be logged prominently to the console or
have their own "errors and warnings" tab in the manager, shouldn't
they?

Daniel.

--
-- Daniel Calvelo Aros

This is not an ambiguous action. I'm picking the version of the file in the
current mapset. For that, it is unnecessary to specify the mapset. So what
if there is another file with the same name in another mapset? I may have 10
files with that name in different places. What does this matter. If I want
to pick any file outside the current mapset, I should specify it. I realize
that if I pick a file in another mapset that has a unique name, I don't
*have* to specify the mapset. But I probably should. I *must* specify the
mapset if I pick a file outside the current mapset that does *not* have a
unique name. So I don't see what the purpose of this warning is.

Michael

On 3/22/07 7:30 PM, "Hamish" <hamish_nospam@yahoo.com> wrote:

Michael Barton wrote:

d.rast is still noisy, even with the quiet flag. Can we turn this
stuff off somehow?

d.rast agro_soils --q
WARNING: 'cell/agro_soils' was found in more mapsets (also found in
user1).
WARNING: using 'agro_soils@PERMANENT'.

WARNINGs are not affected by verbosity controls. The above warning is
there for a reason, as you have requested an ambiguous action.

Hamish

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Hamish wrote:
> WARNINGs are not affected by verbosity controls. The above warning
> is there for a reason, as you have requested an ambiguous action.

Daniel wrote:

In that case, warnings should be logged prominently to the console or

aren't they already? They get a big "!" or "X" icon next to them in the
GUI output and capitol letters in the terminal output.

FWIW, if you have a GIS_ERROR_LOG file in your home dir or $GISBASE they
get logged there too.

have their own "errors and warnings" tab in the manager, shouldn't
they?

but then you lose context. If interspursed with the module output (if
any) they show you exactly when/where in the processing the error
happened.

Hamish

We're working on wxgrass and trying to figure out what to do with them in
that context.

Sorry about the earlier rant.

Michael

On 3/22/07 8:07 PM, "Hamish" <hamish_nospam@yahoo.com> wrote:

Hamish wrote:

WARNINGs are not affected by verbosity controls. The above warning
is there for a reason, as you have requested an ambiguous action.

Daniel wrote:

In that case, warnings should be logged prominently to the console or

aren't they already? They get a big "!" or "X" icon next to them in the
GUI output and capitol letters in the terminal output.

FWIW, if you have a GIS_ERROR_LOG file in your home dir or $GISBASE they
get logged there too.

have their own "errors and warnings" tab in the manager, shouldn't
they?

but then you lose context. If interspursed with the module output (if
any) they show you exactly when/where in the processing the error
happened.

Hamish

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Michael Barton wrote:

> > d.rast is still noisy, even with the quiet flag. Can we turn this
> > stuff off somehow?
> >
> > d.rast agro_soils --q
> > WARNING: 'cell/agro_soils' was found in more mapsets (also found in
> > user1).
> > WARNING: using 'agro_soils@PERMANENT'.
>
> WARNINGs are not affected by verbosity controls. The above warning is
> there for a reason, as you have requested an ambiguous action.

This is not an ambiguous action.

Only in the sense that, ultimately, all actions are unambiguous,
insofar as that they have a concrete end result.

OTOH, the action may well have non-obvious consequences, which is
probably a more useful classification than whether or not it is
ambiguous.

I'm picking the version of the file in the
current mapset. For that, it is unnecessary to specify the mapset.

Incorrect.

If you want the version which comes first in the mapset search path,
then it's unnecessary to specify the mapset. The current mapset
doesn't have to be the first one in the search path; that's just the
default if you don't specify an explicit search path.

So what if there is another file with the same name in another
mapset?

That file may well have been the one which you intended to use.

I may have 10
files with that name in different places. What does this matter. If I want
to pick any file outside the current mapset, I should specify it.

You are free to set an explicit search path containing only the
current mapset (and not PERMANENT), but that isn't the default. The
default is the current mapset followed by PERMANENT. If you set a
search path which only contains one mapset (e.g. the current mapset),
you will never get more than one match for an unqualified name, and
thus will never see the warning.

--
Glynn Clements <glynn@gclements.plus.com>

OK. I understand your and Hamish's points. It just seems I'm being warned
that I'm doing what I intended to do. But others may do the same thing
unintentionally, hence the warning.

Michael

On 3/22/07 10:06 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:

Michael Barton wrote:

d.rast is still noisy, even with the quiet flag. Can we turn this
stuff off somehow?

d.rast agro_soils --q
WARNING: 'cell/agro_soils' was found in more mapsets (also found in
user1).
WARNING: using 'agro_soils@PERMANENT'.

WARNINGs are not affected by verbosity controls. The above warning is
there for a reason, as you have requested an ambiguous action.

This is not an ambiguous action.

Only in the sense that, ultimately, all actions are unambiguous,
insofar as that they have a concrete end result.

OTOH, the action may well have non-obvious consequences, which is
probably a more useful classification than whether or not it is
ambiguous.

I'm picking the version of the file in the
current mapset. For that, it is unnecessary to specify the mapset.

Incorrect.

If you want the version which comes first in the mapset search path,
then it's unnecessary to specify the mapset. The current mapset
doesn't have to be the first one in the search path; that's just the
default if you don't specify an explicit search path.

So what if there is another file with the same name in another
mapset?

That file may well have been the one which you intended to use.

I may have 10
files with that name in different places. What does this matter. If I want
to pick any file outside the current mapset, I should specify it.

You are free to set an explicit search path containing only the
current mapset (and not PERMANENT), but that isn't the default. The
default is the current mapset followed by PERMANENT. If you set a
search path which only contains one mapset (e.g. the current mapset),
you will never get more than one match for an unqualified name, and
thus will never see the warning.

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Hi Michael,

I agree, the warnings are feature and not a bug. We shoudl always
specify mapset, otherwise it could happen, that the user wilå operate
with other map, than desired..

jachym

2007/3/23, Michael Barton <michael.barton@asu.edu>:

OK. I understand your and Hamish's points. It just seems I'm being warned
that I'm doing what I intended to do. But others may do the same thing
unintentionally, hence the warning.

Michael

On 3/22/07 10:06 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:

>
> Michael Barton wrote:
>
>>>> d.rast is still noisy, even with the quiet flag. Can we turn this
>>>> stuff off somehow?
>>>>
>>>> d.rast agro_soils --q
>>>> WARNING: 'cell/agro_soils' was found in more mapsets (also found in
>>>> user1).
>>>> WARNING: using 'agro_soils@PERMANENT'.
>>>
>>> WARNINGs are not affected by verbosity controls. The above warning is
>>> there for a reason, as you have requested an ambiguous action.
>>
>> This is not an ambiguous action.
>
> Only in the sense that, ultimately, all actions are unambiguous,
> insofar as that they have a concrete end result.
>
> OTOH, the action may well have non-obvious consequences, which is
> probably a more useful classification than whether or not it is
> ambiguous.
>
>> I'm picking the version of the file in the
>> current mapset. For that, it is unnecessary to specify the mapset.
>
> Incorrect.
>
> If you want the version which comes first in the mapset search path,
> then it's unnecessary to specify the mapset. The current mapset
> doesn't have to be the first one in the search path; that's just the
> default if you don't specify an explicit search path.
>
>> So what if there is another file with the same name in another
>> mapset?
>
> That file may well have been the one which you intended to use.
>
>> I may have 10
>> files with that name in different places. What does this matter. If I want
>> to pick any file outside the current mapset, I should specify it.
>
> You are free to set an explicit search path containing only the
> current mapset (and not PERMANENT), but that isn't the default. The
> default is the current mapset followed by PERMANENT. If you set a
> search path which only contains one mapset (e.g. the current mapset),
> you will never get more than one match for an unqualified name, and
> thus will never see the warning.

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

_______________________________________________
grassgui mailing list
grassgui@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassgui

--
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub

Do you want me to explicitly add @mapset for selecting items in the current
maset (already the case for items chosen from other mapsets) in
select.Select?

Michael

On 3/23/07 1:47 AM, "Jachym Cepicky" <jachym.cepicky@gmail.com> wrote:

Hi Michael,

I agree, the warnings are feature and not a bug. We shoudl

always

specify mapset, otherwise it could happen, that the user wilå

operate

with other map, than desired..

jachym

2007/3/23, Michael Barton

<michael.barton@asu.edu>:
OK. I understand your and Hamish's points. It just
seems I'm being warned
that I'm doing what I intended to do. But others may
do the same thing
unintentionally, hence the warning.

Michael

On
3/22/07 10:06 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:

>
>
Michael Barton wrote:
>
>>>> d.rast is still noisy, even with the quiet
flag. Can we turn this
>>>> stuff off somehow?
>>>>
>>>> d.rast
agro_soils --q
>>>> WARNING: 'cell/agro_soils' was found in more mapsets
(also found in
>>>> user1).
>>>> WARNING: using 'agro_soils@PERMANENT'.

>>>
>>> WARNINGs are not affected by verbosity controls. The above warning
is
>>> there for a reason, as you have requested an ambiguous action.
>>

>> This is not an ambiguous action.
>
> Only in the sense that,
ultimately, all actions are unambiguous,
> insofar as that they have a
concrete end result.
>
> OTOH, the action may well have non-obvious
consequences, which is
> probably a more useful classification than whether
or not it is
> ambiguous.
>
>> I'm picking the version of the file in
the
>> current mapset. For that, it is unnecessary to specify the mapset.

>
> Incorrect.
>
> If you want the version which comes first in the
mapset search path,
> then it's unnecessary to specify the mapset. The
current mapset
> doesn't have to be the first one in the search path; that's
just the
> default if you don't specify an explicit search path.
>
>> So
what if there is another file with the same name in another
>> mapset?
>

> That file may well have been the one which you intended to use.
>
>> I
may have 10
>> files with that name in different places. What does this
matter. If I want
>> to pick any file outside the current mapset, I should
specify it.
>
> You are free to set an explicit search path containing
only the
> current mapset (and not PERMANENT), but that isn't the default.
The
> default is the current mapset followed by PERMANENT. If you set a
>
search path which only contains one mapset (e.g. the current mapset),
> you
will never get more than one match for an unqualified name, and
> thus will
never see the warning.

__________________________________________

Michael Barton, Professor of Anthropology
School of Human Evolution & Social
Change
Center for Social Dynamics & Complexity
Arizona State
University

phone: 480-965-6213
fax: 480-965-7671
www:
http://www.public.asu.edu/~cmbarton

_______________________________________________
grassgui mailing list

grassgui@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassgui

--

Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG:

http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

Michael Barton wrote:

Do you want me to explicitly add @mapset for selecting items in the current
maset (already the case for items chosen from other mapsets) in
select.Select?

That would be a good idea.

Have you checked what happens when the current mapset *doesn't* come
first in the search path?

--
Glynn Clements <glynn@gclements.plus.com>

Done.

Michael

On 3/23/07 1:05 PM, "Glynn Clements" <glynn@gclements.plus.com> wrote:

Michael Barton wrote:

Do you want me to explicitly add @mapset for selecting items in the current
maset (already the case for items chosen from other mapsets) in
select.Select?

That would be a good idea.

Have you checked what happens when the current mapset *doesn't* come
first in the search path?

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton