[GRASS-dev] Re: need a truly quiet quiet

GRASS GIS GRASS GIS developer
1

On Nov 1, 2007, at 5:49 PM, grass-dev-request@grass.itc.it wrote:

Initial Comment:

Hi,

I have just experienced, how expensive it can be, to write a WARNING out for every point, when buffering. I try to build simple buffers (only 8 points needed) around a lot of points - in one case 370.000 - and for the reason I choose a high tolerance value (to be sure, it will be reset to the max allowed one). THis works, but takes unbelievably long with all the warnings:

“WARNING: The tolerance was reset to …”

Now I have commented out the warning in main.c of v.buffer, and suddenly it is running like mad (30 seconds instead of over 10 minutes). So maybe it would be nice to :

  • either add another switch to turn off this warning

  • or include it under the “–quiet” option (NO warning if “–quiet” set).

Andras Fabian

You can respond by visiting:

http://wald.intevation.org/tracker/?func=detail&atid=188&aid=525&group_id=21

Andras,

I really really agree with you. This has been an endless source of problems for me trying to script a GUI around modules that will not be quiet.

Michael

C. Michael Barton, Professor of Anthropology

Director of Graduate Studies

School of Human Evolution & Social Change

Center for Social Dynamics & Complexity

Arizona State University

Phone: 480-965-6262

Fax: 480-965-7671

www: <www.public.asu.edu/~cmbarton>

2

Michael Barton wrote:

> I have just experienced, how expensive it can be, to write a
> WARNING out for every point, when buffering. I try to build simple
> buffers (only 8 points needed) around a lot of points - in one case
> 370.000 - and for the reason I choose a high tolerance value (to be
> sure, it will be reset to the max allowed one). THis works, but
> takes unbelievably long with all the warnings:
> "WARNING: The tolerance was reset to ..."
>
> Now I have commented out the warning in main.c of v.buffer, and
> suddenly it is running like mad (30 seconds instead of over 10
> minutes). So maybe it would be nice to :
> - either add another switch to turn off this warning
> - or include it under the "--quiet" option (NO warning if "--quiet"
> set).

I really really agree with you. This has been an endless source of
problems for me trying to script a GUI around modules that will not
be quiet.

With the exception of Tcl's exec and open| treating stderr output as
an error, scripts shouldn't care whether modules are writing anything
to stderr.

If a script has problems with modules writing to stderr, that's the
fault of the script, not the module.

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