On Mon, Oct 19, 2015 at 11:35 AM, Paolo Cavallini <[email protected]> wrote: > Il 19/10/2015 11:30, Markus Neteler ha scritto: > >> The problem is to "guess" how much memory resources are available >> which change continuously (i.e. RAM is naturally static but its >> allocation not). > > sure - perhaps taking the total memory as an upper bound could mitigate > at least the most serious cases.
In case it would be RAM + SWAP. But to my limited knowledge it is not possible to easily know the available memory on at least Windows (what I remember from past discussions here). >> Just check the "history" file of the mapset. Some previously issued >> command will have set the computational region. >> A candidate might be a g.region vector=vmap with an additional >> (unneeded) res=value call (maybe from "Processing"?). > > right - interestingly enough, the history does not seem to be visible in > the current version of the grass qgis plugin - going to explore this. thanks - it would be great to have it also there. ciao Markus _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
