[GRASS-dev] creating temporary mapsets in a parallelized python script

Anna Petrášová kratochanna at gmail.com
Mon Apr 11 14:09:59 PDT 2016


On Mon, Apr 11, 2016 at 4:46 PM, Helmut Kudrnovsky <hellik at web.de> wrote:
> Anna Petrášová wrote
>> On Mon, Apr 11, 2016 at 4:04 PM, Helmut Kudrnovsky <
>
>> hellik@
>
>> > wrote:
>>> Hi,
>>>
>>> in a parallelized python script it is needed to do the parallelized jobs
>>> in
>>> different mapsets as region settings are changed during calculations.
>>
>> are you sure you need separate mapsets? You can also just use this:
>>
>> env = os.environ.copy()
>> env['GRASS_REGION'] = grass.region_env(raster='elevation')
>>
>> gscript.run_command('r.viewshed', ..., env=env)
>>
>> Anna
>>
>>>
>>> Any hints how to create temporary mapsets? Already existing pygrass /
>>> pyscript functions?
>>>
>
> the idea of the script is to run (1) by python's multiprocessing for more
> than 600 points.
>
> IIRC (1) changes region during calculations, so several calculations may
> interfere in regions settings.
>
>

I see, then it's easier to fix the script and use grass.use_temp_region

> (1)
> https://trac.osgeo.org/grass/browser/grass-addons/grass7/raster/r.basin/r.basin.py
>
>
>
> -----
> best regards
> Helmut
> --
> View this message in context: http://osgeo-org.1560.x6.nabble.com/creating-temporary-mapsets-in-a-parallelized-python-script-tp5260753p5260758.html
> Sent from the Grass - Dev mailing list archive at Nabble.com.
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev


More information about the grass-dev mailing list