Hi Pietro,
When running the tiled_function function you wrote [1] I am getting the error below.
{{{
tiled_function(raster_inputs=ref, raster_output=“out_mah1”, func=mahalanobis_distances)
}}}
ERROR: No null file for <out_mah1>
Any idea what is wrong?
Best wishes,
Paulo
[1] http://lists.osgeo.org/pipermail/grass-dev/2015-February/074049.html
Paulo van Breugel wrote:
When running the tiled_function function you wrote [1] I am getting the
error below.{{{
tiled_function(raster_inputs=ref, raster_output="out_mah1",
func=mahalanobis_distances)
}}}ERROR: No null file for <out_mah1>
Any idea what is wrong?
That error message is from lib/raster, and indicates that the null
file couldn't be created (Rast_open_new() should probably generate an
error or warning if this happens; the fact that it doesn't suggests
that it isn't a common occurrence).
Were there any other warnings prior to that? Check the permissions on
the mapset directory, the cell_misc subdirectory, and the
cell_misc/out_mah1 subdirectory (if it exists).
Alternatively, it might indicate an issue in the PyGrass library; that
code is relatively new.
--
Glynn Clements <glynn@gclements.plus.com>
On Mon, Mar 16, 2015 at 3:30 PM, Glynn Clements <glynn@gclements.plus.com>
wrote:
Paulo van Breugel wrote:
> When running the tiled_function function you wrote [1] I am getting the
> error below.
>
> {{{
> tiled_function(raster_inputs=ref, raster_output="out_mah1",
> func=mahalanobis_distances)
> }}}
>
> ERROR: No null file for <out_mah1>
>
> Any idea what is wrong?That error message is from lib/raster, and indicates that the null
file couldn't be created (Rast_open_new() should probably generate an
error or warning if this happens; the fact that it doesn't suggests
that it isn't a common occurrence).Were there any other warnings prior to that? Check the permissions on
the mapset directory, the cell_misc subdirectory, and the
cell_misc/out_mah1 subdirectory (if it exists).
No prior warnings, as far as I could see. Permissions on those folders are
OK. No cell_misc/out_mah1, but that makes sense I guess as that is the
raster file that should be created by the tiled_function.
Alternatively, it might indicate an issue in the PyGrass library; that
code is relatively new.
OK, hopefully the PyGrass gurus can have a look at it.
--
Glynn Clements <glynn@gclements.plus.com>
Hi Paulo,
On Mon, Mar 16, 2015 at 9:23 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
Paulo van Breugel wrote:
Alternatively, it might indicate an issue in the PyGrass library; that
code is relatively new.OK, hopefully the PyGrass gurus can have a look at it.
Ofcourse I will look into it, but since I need two/three weeks, may be
could a good idea to open a ticket on track, just to not forget this
problem.
Thank you for reporting this.
Pietro
Great, I’ll do that
On Mon, Mar 16, 2015 at 9:56 PM, Pietro <peter.zamb@gmail.com> wrote:
Hi Paulo,
On Mon, Mar 16, 2015 at 9:23 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:Paulo van Breugel wrote:
Alternatively, it might indicate an issue in the PyGrass library; that
code is relatively new.OK, hopefully the PyGrass gurus can have a look at it.
Ofcourse I will look into it, but since I need two/three weeks, may be
could a good idea to open a ticket on track, just to not forget this
problem.
Thank you for reporting this.Pietro
Hi Pietro
I would just like to check if you had a change to look at the problem described in http://trac.osgeo.org/grass/ticket/2629?
Cheers
Paulo
On 16-03-15 22:01, Paulo van Breugel wrote:
Great, I’ll do that
On Mon, Mar 16, 2015 at 9:56 PM, Pietro <peter.zamb@gmail.com> wrote:
Hi Paulo,
On Mon, Mar 16, 2015 at 9:23 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:Paulo van Breugel wrote:
Alternatively, it might indicate an issue in the PyGrass library; that
code is relatively new.OK, hopefully the PyGrass gurus can have a look at it.
Ofcourse I will look into it, but since I need two/three weeks, may be
could a good idea to open a ticket on track, just to not forget this
problem.
Thank you for reporting this.Pietro