[GRASS-dev] [GRASS GIS] #2074: r3.mapcalc neighborhood modifier hash table and tile errors

[GRASS GIS]

#2074: r3.mapcalc neighborhood modifier hash table and tile errors
-------------------------+--------------------------------------------------
 Reporter:  wenzeslaus   |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  normal       |   Milestone:  7.0.0                    
Component:  Raster3D     |     Version:  svn-trunk                
 Keywords:  r3.mapcalc   |    Platform:  All                      
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by neteler):

 Replying to [comment:13 wenzeslaus]:
 > Replying to [comment:12 glynn]:
 > > Replying to [comment:11 wenzeslaus]:
 > >
 > > > I though that `putenv("WORKERS=1")` solved it and I don't have to
 set anything, is that right?
 > >
 > > Actually it probably needs to be `putenv("WORKERS=0")`. WORKERS=1 will
 create 1 additional thread, but will also execute code in the main thread.
 >
 > This makes sense although it is not consistent with other usages of
 `WORKERS`:

 ...

 Just a (user) comment:

 In general the notion of WORKERS=0 is a bit strange from a user's point of
 view.
 I know that it is C notion but not quite human readable. Most users will
 put WORKERS=1 and then, suprise, find two parallel threads (?)...

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2074#comment:14>
GRASS GIS <http://grass.osgeo.org>