Moritz Lennert wrote:
Ok. In any case, this probably a candidate for backporting to
grass70release before the upcoming release. Can it be backported as such ?
Yes.
--
Glynn Clements gl...@gclements.plus.com
___
grass-dev mailing list
2015-07-21 20:36 GMT+02:00 Glynn Clements gl...@gclements.plus.com:
Ok. In any case, this probably a candidate for backporting to
grass70release before the upcoming release. Can it be backported as such ?
Yes.
I backported r65591 to relbr70 as r65764. Martin
--
Martin Landa
Thank you guys, this has been an ongoing issue for me for the last
year or two. I have experienced this error sporadically but could not
recreate it and thus figured it was something specific to my machine.
I noticed this error when using r.series and some of the new temporal
modules-- in each
Moritz Lennert wrote:
One thing I noticed is that on the one test case I used here for
testing your fix, running with WORKERS=0 is slightly faster than without
setting it. I didn't test rigorously, but is that expected ?
Maybe. It avoids the overhead of switching threads. And using multiple
On 18/07/15 11:59, Glynn Clements wrote:
Moritz Lennert wrote:
One thing I noticed is that on the one test case I used here for
testing your fix, running with WORKERS=0 is slightly faster than without
setting it. I didn't test rigorously, but is that expected ?
Maybe. It avoids the overhead
On 15/07/15 05:21, Glynn Clements wrote:
Moritz Lennert wrote:
So, for me, the best solution at this stage is to just set WORKERS
to 0 ?
That should work. Also, the issue should be fixed by r65591.
Seems to work nicely. Thanks for the quick fix !
One thing I noticed is that on the one
Moritz Lennert wrote:
I don't know how to debug this...
Can you identify a repeatable test case?
If I could make it happen, I could debug it.
You can get a location names TEST here:
http://tomahawk.ulb.ac.be/moritz/mask_bug_testlocation.tgz
This contains only a PERMANENT
On 14/07/15 09:46, Glynn Clements wrote:
Moritz Lennert wrote:
I don't know how to debug this...
Can you identify a repeatable test case?
If I could make it happen, I could debug it.
You can get a location names TEST here:
http://tomahawk.ulb.ac.be/moritz/mask_bug_testlocation.tgz
This
Moritz Lennert wrote:
So, for me, the best solution at this stage is to just set WORKERS to 0 ?
That should work. Also, the issue should be fixed by r65591.
--
Glynn Clements gl...@gclements.plus.com
___
grass-dev mailing list
On 2015-07-09 01:01, Glynn Clements wrote:
Moritz Lennert wrote:
I don't know how to debug this...
Can you identify a repeatable test case?
If I could make it happen, I could debug it.
You can get a location names TEST here:
http://tomahawk.ulb.ac.be/moritz/mask_bug_testlocation.tgz
Moritz Lennert wrote:
I don't know how to debug this...
Can you identify a repeatable test case?
If I could make it happen, I could debug it.
--
Glynn Clements gl...@gclements.plus.com
___
grass-dev mailing list
grass-dev@lists.osgeo.org
On Sat, 4 Jul 2015 18:50:44 +0100, Glynn Clements
gl...@gclements.plus.com wrote:
Moritz Lennert wrote:
The error comes from here:
raster/get_row.c:142:G_fatal_error(_(Error reading raster data for
row
%d of %s),
which is part of the 'read_data_compressed' function.
On 2015-07-07 09:45, Moritz Lennert wrote:
On Sat, 4 Jul 2015 18:50:44 +0100, Glynn Clements
gl...@gclements.plus.com wrote:
Moritz Lennert wrote:
The error comes from here:
raster/get_row.c:142: G_fatal_error(_(Error reading raster data
for
row
%d of %s),
which is part of the
Moritz Lennert wrote:
The error comes from here:
raster/get_row.c:142: G_fatal_error(_(Error reading raster data for row
%d of %s),
which is part of the 'read_data_compressed' function.
read(fcb-data_fd, cmp, readamount) returns 0, while readamount is 18.
I'm not familiar enough
On 02/07/15 19:26, Markus Neteler wrote:
On Jul 2, 2015 5:18 PM, Moritz Lennert mlenn...@club.worldonline.be
mailto:mlenn...@club.worldonline.be wrote:
Hello,
When I run a script that loops over a long series of point data sets
and then does a series of raster calculations based on these
On 03-07-15 11:04, Moritz Lennert wrote:
On 02/07/15 19:26, Markus Neteler wrote:
On Jul 2, 2015 5:18 PM, Moritz Lennert mlenn...@club.worldonline.be
mailto:mlenn...@club.worldonline.be wrote:
Hello,
When I run a script that loops over a long series of point data sets
and then does a
On 03/07/15 11:27, Paulo van Breugel wrote:
On 03-07-15 11:04, Moritz Lennert wrote:
On 02/07/15 19:26, Markus Neteler wrote:
On Jul 2, 2015 5:18 PM, Moritz Lennert mlenn...@club.worldonline.be
mailto:mlenn...@club.worldonline.be wrote:
Hello,
When I run a script that loops over a long
Hello,
When I run a script that loops over a long series of point data sets and
then does a series of raster calculations based on these data sets, I
sometimes get the following error:
ERROR: Error reading raster data for row 239 of MASK
Can someone explain what this means and how to debug
On Jul 2, 2015 5:18 PM, Moritz Lennert mlenn...@club.worldonline.be
wrote:
Hello,
When I run a script that loops over a long series of point data sets and
then does a series of raster calculations based on these data sets, I
sometimes get the following error:
ERROR: Error reading raster data
* Moritz Lennert mlenn...@club.worldonline.be [2015-07-02 17:18:49 +0200]:
Hello,
When I run a script that loops over a long series of point data sets and
then does a series of raster calculations based on these data sets, I
sometimes get the following error:
ERROR: Error reading
20 matches
Mail list logo
