d.rast still noisy

[Michael Barton]

Some javascript/style in this post has been disabled (why?)

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: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton


_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Daniel Calvelo]

On 3/22/07, Hamish <[hidden email]> 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

_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Michael Barton]

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" <[hidden email]> 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: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton


_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Michael Barton]

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" <[hidden email]> 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: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton


_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Glynn Clements]

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 <[hidden email]>

_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Michael Barton]

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" <[hidden email]> 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: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton


_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Jachym Cepicky]

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 <[hidden email]>:

> 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" <[hidden email]> 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: [phone]
> fax: [phone]
> www: http://www.public.asu.edu/~cmbarton
>
>
> _______________________________________________
> grassgui mailing list
> [hidden email]
> 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

_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Michael Barton]

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" <[hidden email]> 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

> <[hidden email]>:
> 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" <[hidden email]> 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: [phone]
> fax: [phone]
> www:
> http://www.public.asu.edu/~cmbarton
>
>
>
> _______________________________________________
> grassgui mailing list
>
> [hidden email]
> 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: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton



_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Michael Barton]

This can't happen internally due to the behavior of the combox tree. But it
isn't a problem to added it explicitly. I just did it. This should avoid
warnings over ambiguous map selection


On 3/23/07 8:00 AM, "Jachym Cepicky" <[hidden email]> wrote:

> can this not happen internaly? display "clean" map name but, for
rendering
> (AddCommandLayer) use map@mapset form?

j

2007/3/23, Michael Barton
> <[hidden email]>:
> 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
>


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

phone: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton


_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Glynn Clements]

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 <[hidden email]>

_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui

[Michael Barton]

Done.

Michael


On 3/23/07 1:05 PM, "Glynn Clements" <[hidden email]> 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: [phone]
fax: [phone]
www: http://www.public.asu.edu/~cmbarton


_______________________________________________
grassgui mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/grassgui