I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
On Tue, Nov 4, 2008 at 8:41 AM, Hamish <hamish_b@yahoo.com> wrote:
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
Maybe it's already there?
set GRASS_VERBOSE=0 ?
No, because some of these jobs runs for many hours and I
would like to see the progress (to estimate the total time).
In this case I am running v.vol.rst...
On Tue, Nov 4, 2008 at 8:23 AM, Markus Neteler <neteler@osgeo.org> wrote:
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
Suggestion: Could this be conditionalized upon the presence of the
GRASS_BATCH_JOB
variable?
On Tue, Nov 4, 2008 at 8:41 AM, Hamish <hamish_b@yahoo.com> wrote:
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
Maybe it's already there?
set GRASS_VERBOSE=0 ?
No, because some of these jobs runs for many hours and I
would like to see the progress (to estimate the total time).
Hi Markus,
I'm interested as to what your log file looks like and how you discern which percentage value is coming from which process. Are they not all mixed together anyway? I was thinking perhaps you could filter the stderr of each GRASS module through a short C program that could strip the backspace characters and print the name of the module with it's progress value on a new line every time there is a new percentage point? Or is the problem not complicated enough to need such a solution?
On Tue, Nov 4, 2008 at 1:52 PM, Paul Kelly
<paul-grass@stjohnspoint.co.uk> wrote:
On Tue, 4 Nov 2008, Markus Neteler wrote:
On Tue, Nov 4, 2008 at 8:41 AM, Hamish <hamish_b@yahoo.com> wrote:
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
Maybe it's already there?
set GRASS_VERBOSE=0 ?
No, because some of these jobs runs for many hours and I
would like to see the progress (to estimate the total time).
Hi Markus,
Hello Paul,
I'm interested as to what your log file looks like and how you discern which
percentage value is coming from which process. Are they not all mixed
together anyway?
The job manager ([SUN] Grid Engine) separates stderr and stdout into
two files. The stderr file contains
I was thinking perhaps you could filter the stderr of each
GRASS module through a short C program that could strip the backspace
characters and print the name of the module with it's progress value on a
new line every time there is a new percentage point? Or is the problem not
complicated enough to need such a solution?
I guess I would have to modify Grid engine... not possible.
I can certainly do a local hack to suppress all these ^H chars but would prefer
a general solution.
It's not a dramatic issue, just to get rid of these chars would be helpful
to debug such script output files.
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
Maybe it's already there?
The closest is:
export GRASS_MESSAGE_FORMAT=gui
That's a bit noisy, but it does eliminate the BS characters.
>>>> control chars from G_percent().
>>>> It would be great to have a switch (or detection magic)
>>>> to output the plain ASCII style 0..10...20.. in this cases.
because the way it is called it can't be like "0..10...20.." as with
gdal tools, but there could be a version which replaced ^H^H^H with " ".
On Tue, Nov 4, 2008 at 8:31 PM, Glynn Clements <glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
I am running a large number of processing jobs on a
cluster and the job manager output is cluttered with
control chars from G_percent().
It would be great to have a switch (or detection magic)
to output the plain ASCII style 0..10...20.. in this cases.
Maybe it's already there?
The closest is:
export GRASS_MESSAGE_FORMAT=gui
That's a bit noisy, but it does eliminate the BS characters.
>> I am running a large number of processing jobs on a
>> cluster and the job manager output is cluttered with
>> control chars from G_percent().
>> It would be great to have a switch (or detection magic)
>> to output the plain ASCII style 0..10...20.. in this cases.
>>
>> Maybe it's already there?
>
> The closest is:
>
> export GRASS_MESSAGE_FORMAT=gui
>
> That's a bit noisy, but it does eliminate the BS characters.
On Wed, Nov 5, 2008 at 11:31 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
>> I am running a large number of processing jobs on a
>> cluster and the job manager output is cluttered with
>> control chars from G_percent().
>> It would be great to have a switch (or detection magic)
>> to output the plain ASCII style 0..10...20.. in this cases.
>>
>> Maybe it's already there?
>
> The closest is:
>
> export GRASS_MESSAGE_FORMAT=gui
>
> That's a bit noisy, but it does eliminate the BS characters.
On Thu, Nov 6, 2008 at 11:21 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Wed, Nov 5, 2008 at 11:31 PM, Glynn Clements wrote:
Markus Neteler wrote:
>> I am running a large number of processing jobs on a
>> cluster and the job manager output is cluttered with
>> control chars from G_percent().
>> It would be great to have a switch (or detection magic)
>> to output the plain ASCII style 0..10...20.. in this cases.
On Sun, Dec 28, 2008 at 12:54 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Thu, Nov 6, 2008 at 11:21 AM, Markus Neteler <neteler@osgeo.org> wrote:
On Wed, Nov 5, 2008 at 11:31 PM, Glynn Clements wrote:
Markus Neteler wrote:
>> I am running a large number of processing jobs on a
>> cluster and the job manager output is cluttered with
>> control chars from G_percent().
>> It would be great to have a switch (or detection magic)
>> to output the plain ASCII style 0..10...20.. in this cases.
On Mon, Dec 29, 2008 at 4:41 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Sun, Dec 28, 2008 at 12:54 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Thu, Nov 6, 2008 at 11:21 AM, Markus Neteler <neteler@osgeo.org> wrote:
Markus Neteler wrote:
>> I am running a large number of processing jobs on a
>> cluster and the job manager output is cluttered with
>> control chars from G_percent().
>> It would be great to have a switch (or detection magic)
>> to output the plain ASCII style 0..10...20.. in this cases.