#510: bad display in the Output window for r.report and r.stats with aspect maps.
-------------------------+--------------------------------------------------
Reporter: clerici | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: default | Version: 6.4.0 RCs
Keywords: | Platform: Linux
Cpu: Unspecified |
-------------------------+--------------------------------------------------
r.report and r.stats for aspect maps produce ordered tables if saved in a
file but randomly disordered if displayed in the Output window.[[BR]]
In detail:[[BR]]
1) r.report for aspect map in Spearfish gives always bad (and different)
results as reported in the attachment N.1[[BR]]
2) r.stats has a random behaviour as usually displays correct results, but
sometimes the table is incorrect as in the example of the attachment N.2
the only problem I see is that there is too much whitespace after the
"#|description" in the header for FP range mode.
{{{
|-----------------------------------------------------------------------------|
|MAP: aspect in degrees from east (aspect@PERMANENT in PERMANENT)
|
|-----------------------------------------------------------------------------|
| Category Information | square |
% |
| #|description
|kilometers| cover|
|-----------------------------------------------------------------------------|
| 0-1.411765|from no aspect to 1 degree from east | 0.537300|
0.20|
| 1.411765-2.823529|from 1 degree from east to 3 degrees | 0.827100|
0.30|
| |from east | |
|
}}}
#510: bad display in the Output window for r.report and r.stats with aspect maps.
----------------------+-----------------------------------------------------
Reporter: clerici | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: default | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: Linux | Cpu: Unspecified
----------------------+-----------------------------------------------------
Comment (by mlennert):
Replying to [comment:2 hamish]:
> can anyone else reproduce this?
No for r.report, but yes for r.stats (both in gis.m, not on the command
line). There seems to be a serious sorting issue with the r.stats output
in the Output windows of gis.m. The output is not missing any lines, but
these lines show up later.
Maybe an issue of speed of output and redirection to the output window ?
#510: bad display in the Output window for r.report and r.stats with aspect maps.
----------------------+-----------------------------------------------------
Reporter: clerici | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Tcl | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: All | Cpu: Unspecified
----------------------+-----------------------------------------------------
Changes (by hamish):
* platform: Linux => All
* component: default => Tcl
Comment:
> Replying to [comment:2 hamish]:
> > can anyone else reproduce this?
Replying to [comment:3 mlennert]:
> No for r.report, but yes for r.stats (both in gis.m, not on
> the command line). There seems to be a serious sorting issue
> with the r.stats output in the Output windows of gis.m. The
> output is not missing any lines, but these lines show up later.
>
> Maybe an issue of speed of output and redirection to the output
> window ?
ah, yes. I can reproduce it from both modules in gis.m (both linux/latest
6.5svn and wingrass 6.4.0svn native installer), and d.m on linux.
#510: bad display in the Output window for r.report and r.stats with aspect maps.
----------------------+-----------------------------------------------------
Reporter: clerici | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Tcl | Version: 6.4.0 RCs
Resolution: | Keywords:
Platform: All | Cpu: Unspecified
----------------------+-----------------------------------------------------
Comment (by cmbarton):
I can replicate this too with r.stats. It seems to happen if you have a
lot of data. The gronsole.tcl is fairly mysterious code in places. My only
guess is that this output window was not designed to handle that much data
coming in at once and the formatting lags the data stream.