[GRASS-dev] wingrass daily buidls + addons temporary down

Hi all,

winGRASS daily builds and addons (http://wingrass.fsv.cvut.cz) will be
temporary down due to moving building environment from mingw to
mingw-w64. Please stay tuned.

Martin

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Great! Thank you for your continued efforts.

Doug

···

On Fri, Dec 11, 2015 at 11:20 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi all,

winGRASS daily builds and addons (http://wingrass.fsv.cvut.cz) will be
temporary down due to moving building environment from mingw to
mingw-w64. Please stay tuned.

Martin


Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa


grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.gov

The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats. As a federal employee, my email may be subject to FOIA request.

Hi,

2015-12-11 17:20 GMT+01:00 Martin Landa <landa.martin@gmail.com>:

winGRASS daily builds and addons (http://wingrass.fsv.cvut.cz) will be
temporary down due to moving building environment from mingw to
mingw-w64. Please stay tuned.

since today you can start testing 64bit daily builds via standalone
installer (*) [1,2] or through OSGeo4W [3] (`grass-daily`) package. I
also drop dependency on MSYS. So no MSYS installed together with
GRASS.

There are still several open issues:

* GRASS binaries are a bit bigger (39MB vs 49MB compressed). This
difference is caused by bigger exe GRASS files (not sure why, will
investigate later **)
* 64bit Windows installer is 20MB compressed smaller that 32bit (it's
cause by different Python packages in OSGeo4W)
* GRASS Addons are still down (will work on them in the next days)

But it's ready for testing! Enjoy and please report issues;-) Ma

(*) If you have GRASS already installed, please uninstall first from
control panel and then install GRASS 64bit (you need to uninstall
separately otherwise 64bit GRASS will be installed in 'Program Files
(x86)` rather then 'Program Files`).
(**) GRASS packages are now build using mingw32-w64 toolchain using MSYS2 [4]

[1] http://wingrass.fsv.cvut.cz/x86_64/grass71/
[2] http://wingrass.fsv.cvut.cz/x86_64/grass70/
[3] http://download.osgeo.org/osgeo4w/osgeo4w-setup-x86_64.exe
[4] https://trac.osgeo.org/grass/wiki/CompileOnWindows#InstalltheMSYS2directorystructure

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

since today you can start testing 64bit daily builds via standalone
installer (*) [1,2] or through OSGeo4W [3] (`grass-daily`) package. I
also drop dependency on MSYS. So no MSYS installed together with
GRASS.

thanks a lot for your effort to bring winGRASS to 64bit!!! :slight_smile:

already downloading...

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241668.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

But it's ready for testing!

System Info
GRASS version: 7.1.svn
GRASS SVN revision: 67160
Build date: 2015-12-16
Build platform: x86_64-w64-mingw32
GDAL: 1.11.3
PROJ.4: 4.9.2
GEOS: 3.5.0
SQLite: 3.7.17
Python: 2.7.5
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

tested with NC sample dataset:

(Wed Dec 16 22:36:18 2015)
r.slope.aspect elevation=elevation@PERMANENT slope=slope aspect=aspect
pcurvature=profcurv tcurvature=tangcurv dx=partderdx dy=partderdy
dxx=partderdxx dyy=partderdyy dxy=partdervdxy
Aspect raster map <aspect> complete
Slope raster map <slope> complete
Profile curve raster map <profcurv> complete
Tangential curve raster map <tangcurv> complete
E-W slope raster map <partderdx> complete
N-S slope raster map <partderdy> complete
Dxx raster map <partderdxx> complete
Dyy raster map <partderdyy> complete
Dxy raster map <partdervdxy> complete
(Wed Dec 16 22:36:26 2015) Command finished (8 sec)

(Wed Dec 16 22:38:52 2015)
r.watershed elevation=elevation@PERMANENT threshold=100
accumulation=accumulation tci=tci drainage=draindir basin=basinraster
stream=streamsegments half_basin=halfbasins length_slope=slopelengths
slope_steepness=slopesteepness
SECTION 1a (of 6): Initiating Memory.
SECTION 1b (of 6): Determining Offmap Flow.
SECTION 2: A* Search.
SECTION 3a: Accumulating Surface Flow with MFD.
SECTION 3b: Adjusting drainage directions.
SECTION 4: RUSLE LS and/or S factor determination.
SECTION 5: Watershed determination.
SECTION 6: Closing Maps.
(Wed Dec 16 22:39:31 2015) Command finished (38 sec)

(Wed Dec 16 22:41:04 2015)
r.stream.extract elevation=elevation@PERMANENT threshold=100
d8cut=10000000000000000000000000000000000000 stream_raster=runique
stream_vector=vuniqe direction=flowdir
Loading elevation raster map...
Initializing A* search...
A* Search...
Calculating flow accumulation...
Extracting streams...
Thinning stream segments...
Writing output raster maps...
Writing vector map <vuniqe>...
Writing attribute data...
Building topology for vector map <vuniqe@w64>...
Registering primitives...
15091 primitives registered
117778 vertices registered
Building areas...
0 areas built
0 isles built
Attaching islands...
Attaching centroids...
Number of nodes: 7600
Number of primitives: 15091
Number of points: 7603
Number of lines: 7488
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0
(Wed Dec 16 22:41:37 2015) Command finished (32 sec)

(Wed Dec 16 22:43:03 2015)
r.neighbors -c input=elevation@PERMANENT output=elevation_average_17 size=17
(Wed Dec 16 22:43:13 2015) Command finished (9 sec)

r.horizon elevation=elevation step=30 bufferzone=200 basename=horangle
maxdistance=5000
WARNING: Please update the usage of <r.horizon>: option <basename> has been
renamed to <output>
Calculating map 1 of 12 (angle 0.00, raster map <horangle_000>)
Calculating map 2 of 12 (angle 30.00, raster map <horangle_030>)
Calculating map 3 of 12 (angle 60.00, raster map <horangle_060>)
Calculating map 4 of 12 (angle 90.00, raster map <horangle_090>)
Calculating map 5 of 12 (angle 120.00, raster map <horangle_120>)
Calculating map 6 of 12 (angle 150.00, raster map <horangle_150>)
Calculating map 7 of 12 (angle 180.00, raster map <horangle_180>)
Calculating map 8 of 12 (angle 210.00, raster map <horangle_210>)
Calculating map 9 of 12 (angle 240.00, raster map <horangle_240>)
Calculating map 10 of 12 (angle 270.00, raster map <horangle_270>)
Calculating map 11 of 12 (angle 300.00, raster map <horangle_300>)
Calculating map 12 of 12 (angle 330.00, raster map <horangle_330>)
(Wed Dec 16 22:51:28 2015) Command finished (3 min 31 sec)

r.sun elevation=elevation horizon_basename=horangle horizon_step=30
aspect=aspect slope=slope glob_rad=global_rad day=180 time=14
Mode 1: instantaneous solar incidence angle & irradiance using a set local
time
Using Linke constant: 3.000000
Using albedo constant: 0.200000
Using slope map <slope>
Using aspect map <aspect>
(Wed Dec 16 22:54:20 2015) Command finished (11 sec)

(Wed Dec 16 23:02:04 2015)
r.sun elevation=elev_ned_30m linke_value=2.5 albedo_value=0.2 day=172
beam_rad=b172 diff_rad=d172 refl_rad=r172 insol_time=it172
Mode 2: integrated daily irradiation for a given day of the year
Using Linke constant: 2.500000
Using albedo constant: 0.200000
Using slope constant: 0.000000
Using aspect constant: 270.000000
(Wed Dec 16 23:54:16 2015) Command finished (52 min 11 sec)

(Wed Dec 16 23:55:27 2015)
r.topidx input=elevation@PERMANENT output=topidx
Reading elevation map...
Calculating...
Number of sinks or boundaries: 18679
Writing topographic index map...
(Wed Dec 16 23:55:32 2015) Command finished (4 sec)

after some quick tests of some ratser modules: it's quite responsive and
fast ...

thanks

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241683.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Hi,

2015-12-16 21:56 GMT+01:00 Martin Landa <landa.martin@gmail.com>:

* GRASS Addons are still down (will work on them in the next days)

GRASS Addons now again back (you need to install the most fresh daily
build). Thanks for testing. Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Hi,

2015-12-16 23:52 GMT+01:00 Helmut Kudrnovsky <hellik@web.de>:

after some quick tests of some ratser modules: it's quite responsive and
fast ...

it would be interesting to compare with 32bit (new) and also old
(grass 7.0.2-1)... Ma

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Martin Landa wrote

Hi,

2015-12-16 23:52 GMT+01:00 Helmut Kudrnovsky &lt;

hellik@

&gt;:

after some quick tests of some ratser modules: it's quite responsive and
fast ...

it would be interesting to compare with 32bit (new) and also old
(grass 7.0.2-1)... Ma

here it is, some quick test:

g.region -p -a raster=dem align=dem
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: hermannskogel
ellipsoid: bessel
north: 377082.51207363
south: 330542.51207363
west: 299699.26720377
east: 406699.26720377
nsres: 10
ewres: 10
rows: 4654
cols: 10700
cells: 49797800

----------------

GRASS version: 7.0.2
GRASS SVN Revision: 66861
Build Date: 2015-11-19
Build Platform: i686-pc-mingw32
GDAL/OGR: 1.11.3
PROJ.4: 4.8.0
GEOS: 3.5.0
SQLite: 3.7.17
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

r.slope.aspect elevation=dem slope=wingrass_702_32_bit_slope
aspect=wingrass_702_32_bit_aspect pcurvature=wingrass_702_32_bit_profcurv
tcurvature=wingrass_702_32_bit_tangcurv dx=wingrass_702_32_bit_dx
dy=wingrass_702_32_bit_dy dxx=wingrass_702_32_bit_dxx
dyy=wingrass_702_32_bit_dyy dxy=wingrass_702_32_bit_dxy
Aspect raster map <wingrass_702_32_bit_aspect> complete
Slope raster map <wingrass_702_32_bit_slope> complete
Profile curve raster map <wingrass_702_32_bit_profcurv> complete
Tangential curve raster map <wingrass_702_32_bit_tangcurv> complete
E-W slope raster map <wingrass_702_32_bit_dx> complete
N-S slope raster map <wingrass_702_32_bit_dy> complete
Dxx raster map <wingrass_702_32_bit_dxx> complete
Dyy raster map <wingrass_702_32_bit_dyy> complete
Dxy raster map <wingrass_702_32_bit_dxy> complete
(Thu Dec 17 14:22:45 2015) Command finished (11 min 47 sec)

----------------

GRASS version: 7.1.svn
GRASS SVN revision: 67197
Build date: 2015-12-17
Build platform: i386-w64-mingw32
GDAL: 1.11.3
PROJ.4: 4.9.2
GEOS: 3.5.0
SQLite: 3.7.17
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

r.slope.aspect elevation=dem slope=wingrass_71svn_32_bit_slope
aspect=wingrass_71svn_32_bit_aspect
pcurvature=wingrass_71svn_32_bit_profcurv
tcurvature=wingrass_71svn_32_bit_tancurv dx=wingrass_71svn_32_bit_dx
dy=wingrass_71svn_32_bit_dy dxx=wingrass_71svn_32_bit_dxx
dyy=wingrass_71svn_32_bit_dyy dxy=wingrass_71svn_32_bit_dxy
Aspect raster map <wingrass_71svn_32_bit_aspect> complete
Slope raster map <wingrass_71svn_32_bit_slope> complete
Profile curve raster map <wingrass_71svn_32_bit_profcurv> complete
Tangential curve raster map <wingrass_71svn_32_bit_tancurv> complete
E-W slope raster map <wingrass_71svn_32_bit_dx> complete
N-S slope raster map <wingrass_71svn_32_bit_dy> complete
Dxx raster map <wingrass_71svn_32_bit_dxx> complete
Dyy raster map <wingrass_71svn_32_bit_dyy> complete
Dxy raster map <wingrass_71svn_32_bit_dxy> complete
(Thu Dec 17 14:33:26 2015) Command finished (7 min 17 sec)

----------------

System Info
GRASS version: 7.1.svn
GRASS SVN revision: 67197
Build date: 2015-12-17
Build platform: x86_64-w64-mingw32
GDAL: 1.11.3
PROJ.4: 4.9.2
GEOS: 3.5.0
SQLite: 3.7.17
Python: 2.7.5
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

r.slope.aspect elevation=dem slope=wingrass_71svn_64_bit_slope
aspect=wingrass_71svn_64_bit_aspect
pcurvature=wingrass_71svn_64_bit_profcurv
tcurvature=wingrass_71svn_64_bit_tangcurv dx=wingrass_71svn_64_bit_dx
dy=wingrass_71svn_64_bit_dy dxx=wingrass_71svn_64_bit_dxx
dyy=wingrass_71svn_64_bit_dyy dxy=wingrass_71svn_64_bit_dxy
Aspect raster map <wingrass_71svn_64_bit_aspect> complete
Slope raster map <wingrass_71svn_64_bit_slope> complete
Profile curve raster map <wingrass_71svn_64_bit_profcurv> complete
Tangential curve raster map <wingrass_71svn_64_bit_tangcurv> complete
E-W slope raster map <wingrass_71svn_64_bit_dx> complete
N-S slope raster map <wingrass_71svn_64_bit_dy> complete
Dxx raster map <wingrass_71svn_64_bit_dxx> complete
Dyy raster map <wingrass_71svn_64_bit_dyy> complete
Dxy raster map <wingrass_71svn_64_bit_dxy> complete
(Thu Dec 17 14:54:58 2015) Command finished (5 min 58 sec)
----------------

no systematic test here, but it seems there is some speed gain from:

7.0.2 32 bit (old mingw tool chain) -> 7.1.svn 32 bit (new mingw2 tool
chain) -> 7.1.svn 64 bit (new mingw2 tool chain)

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241772.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Dec 17, 2015 at 8:51 AM, Helmut Kudrnovsky <hellik@web.de> wrote:

>:

after some quick tests of some ratser modules: it’s quite responsive and
fast …

it would be interesting to compare with 32bit (new) and also old
(grass 7.0.2-1)… Ma

here it is, some quick test:

Almost twice as fast this is really good! Thanks Martin, the 64bit version is useful in general as well.

Helmut, do you want to try to run all tests to see if they work and if there is some visible seed improvement as well?

Quoting from my previous email about tests on Windows [1]: Install the latest build of trunk for Windows. Get the latest source code: If you don’t have Subversion on Windows, checkout the latest version on Linux (or make distclean && svn up), zip it and unzip it on Windows. Run GRASS GIS, use cmd line, cd into the source code dir and run all tests [2]:

python -m grass.gunittest.main --location nc_basic_spm_grass7 --location-type nc

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-February/074037.html
[2] http://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html

Hi,

2015-12-17 14:51 GMT+01:00 Helmut Kudrnovsky <hellik@web.de>:

7.0.2 32 bit (old mingw tool chain) -> 7.1.svn 32 bit (new mingw2 tool
chain) -> 7.1.svn 64 bit (new mingw2 tool chain)

please try to compare 7.0.2 vs 7.0.3svn (32bit and 64bit) [1,2]. Thanks, Martin

[1] http://wingrass.fsv.cvut.cz/x86/grass70/
[2] http://wingrass.fsv.cvut.cz/x86_64/grass70/

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa

Hi Helmut,

On Wed, 16. Dec 2015 at 13:07:17 -0800, Helmut Kudrnovsky wrote:

>since today you can start testing 64bit daily builds via standalone
>installer (*) [1,2] or through OSGeo4W [3] (`grass-daily`) package. I
>also drop dependency on MSYS. So no MSYS installed together with
>GRASS.

thanks a lot for your effort to bring winGRASS to 64bit!!! :slight_smile:

winGRASS is just the standalone installer? Otherwise 64bit GRASS has been
sitting in OSGeo4W for more than two years - although there weren't any updates
after 6.4.3 :wink:

Jürgen

--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50
Software Engineer D-26506 Norden http://www.norbit.de

Hi Jürgen,

Jürgen E. Fischer wrote

Hi Helmut,

On Wed, 16. Dec 2015 at 13:07:17 -0800, Helmut Kudrnovsky wrote:

>since today you can start testing 64bit daily builds via standalone
>installer (*) [1,2] or through OSGeo4W [3] (`grass-daily`) package. I
>also drop dependency on MSYS. So no MSYS installed together with
>GRASS.

thanks a lot for your effort to bring winGRASS to 64bit!!! :slight_smile:

winGRASS is just the standalone installer? Otherwise 64bit GRASS has been
sitting in OSGeo4W for more than two years - although there weren't any
updates
after 6.4.3 :wink:

Jürgen

as it was late in the night, just forgotten to add 7 ... :wink:

no doubt, also thank you for the initial effort ... :slight_smile:

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241805.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Martin Landa wrote

Hi,

2015-12-17 14:51 GMT+01:00 Helmut Kudrnovsky &lt;

hellik@

&gt;:

7.0.2 32 bit (old mingw tool chain) -> 7.1.svn 32 bit (new mingw2 tool
chain) -> 7.1.svn 64 bit (new mingw2 tool chain)

please try to compare 7.0.2 vs 7.0.3svn (32bit and 64bit) [1,2]. Thanks,
Martin

[1] http://wingrass.fsv.cvut.cz/x86/grass70/
[2] http://wingrass.fsv.cvut.cz/x86_64/grass70/

--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
_______________________________________________
grass-dev mailing list

grass-dev@.osgeo

http://lists.osgeo.org/mailman/listinfo/grass-dev

done, still no profiled comparing, just a quick and simple test:

g.region -p -a raster=dem align=dem
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: hermannskogel
ellipsoid: bessel
north: 377082.51207363
south: 330542.51207363
west: 299699.26720377
east: 406699.26720377
nsres: 10
ewres: 10
rows: 4654
cols: 10700
cells: 49797800
(Thu Dec 17 18:08:29 2015) Command finished (0 sec)

--------------------

System Info
GRASS version: 7.0.3svn
GRASS SVN Revision: 67196
Build Date: 2015-12-17
Build Platform: i386-w64-mingw32
GDAL/OGR: 1.11.3
PROJ.4: 4.9.2
GEOS: 3.5.0
SQLite: 3.7.17
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1

r.slope.aspect elevation=dem_npht_null_filled@myricaria
slope=wingrass703svn_32bit_slope aspect=wingrass703svn_32bit_aspect
pcurvature=wingrass703svn_32bit_profcurv
tcurvature=wingrass703svn_32bit_tancurv dx=wingrass702svn_32bit_dx
dy=wingrass702svn_32bit_dy dxx=wingrass702svn_32bit_dxx
dyy=wingrass702svn_32bit_dyy dxy=wingrass702svn_32bit_dxy
Aspect raster map <wingrass703svn_32bit_aspect> complete
Slope raster map <wingrass703svn_32bit_slope> complete
Profile curve raster map <wingrass703svn_32bit_profcurv> complete
Tangential curve raster map <wingrass703svn_32bit_tancurv> complete
E-W slope raster map <wingrass703svn_32bit_dx> complete
N-S slope raster map <wingrass703svn_32bit_dy> complete
Dxx raster map <wingrass703svn_32bit_dxx> complete
Dyy raster map <wingrass703svn_32bit_dyy> complete
Dxy raster map <wingrass703svn_32bit_dxy> complete
(Thu Dec 17 18:21:29 2015) Command finished (10 min 20 sec)

--------------------

System Info
GRASS version: 7.0.3svn
GRASS SVN Revision: 67196
Build Date: 2015-12-17
Build Platform: x86_64-w64-mingw32
GDAL/OGR: 1.11.3
PROJ.4: 4.9.2
GEOS: 3.5.0
SQLite: 3.7.17
Python: 2.7.5
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1

r.slope.aspect elevation=dem_npht_null_filled@myricaria
slope=wingrass703svn_64bit_slope aspect=wingrass703svn_64bit_aspect
pcurvature=wingrass703svn_64bit_profcurv
tcurvature=wingrass703svn_64bit_tancurv dx=wingrass703svn_64bit_dx
dy=wingrass703svn_64bit_dy dxx=wingrass703svn_64bit_dxx
dyy=wingrass703svn_64bit_dyy dxy=wingrass703svn_64bit_dxy
Aspect raster map <wingrass703svn_64bit_aspect> complete
Slope raster map <wingrass703svn_64bit_slope> complete
Profile curve raster map <wingrass703svn_64bit_profcurv> complete
Tangential curve raster map <wingrass703svn_64bit_tancurv> complete
E-W slope raster map <wingrass703svn_64bit_dx> complete
N-S slope raster map <wingrass703svn_64bit_dy> complete
Dxx raster map <wingrass703svn_64bit_dxx> complete
Dyy raster map <wingrass703svn_64bit_dyy> complete
Dxy raster map <wingrass703svn_64bit_dxy> complete
(Thu Dec 17 18:39:39 2015) Command finished (8 min 23 sec)

--------------------

there seems still to be some speed gain from 32bit to 64bit

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241806.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

wenzeslaus wrote

On Thu, Dec 17, 2015 at 8:51 AM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

> &gt;:
>> after some quick tests of some ratser modules: it's quite responsive

and

>> fast ...
>
> it would be interesting to compare with 32bit (new) and also old
> (grass 7.0.2-1)... Ma

here it is, some quick test:

Almost twice as fast this is really good! Thanks Martin, the 64bit version
is useful in general as well.

Helmut, do you want to try to run all tests to see if they work and if
there is some visible seed improvement as well?

Quoting from my previous email about tests on Windows [1]: Install the
latest build of trunk for Windows. Get the latest source code: If you
don't
have Subversion on Windows, checkout the latest version on Linux (or make
distclean && svn up), zip it and unzip it on Windows. Run GRASS GIS, use
cmd line, cd into the source code dir and run all tests [2]:

    python -m grass.gunittest.main --location nc_basic_spm_grass7
--location-type nc

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-February/074037.html
[2]
http://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html

tests are running, will post the results later. some are failing as it seems
some maps have different names as expected in the tests.

I suggest to link in [1] to the needed nc sample data set version for which
the tests should be run.

[1]
https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241813.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

wenzeslaus wrote

    python -m grass.gunittest.main --location nc_basic_spm_grass7
--location-type nc

how do I know if the test has finished?

after:

C:\OSGeo4W\src\grass7>python -m grass.gunittest.main --location
nc_spm_08_grass7
--location-type nc
test_assertions from .\lib\python\gunittest failed (6 tests failed)
test_assertions_vect from .\lib\python\gunittest failed (6 tests failed)
test_doctests from .\lib\python\gunittest failed (1 test failed)
test_doctests from .\lib\python\pygrass failed (3 tests failed)
test_doctests from .\lib\python\pygrass\modules failed (1 test failed)
test_doctests from .\lib\python\pygrass\modules\interface failed (1 test
failed)

test_modules from .\lib\python\pygrass\modules\interface failed (17 tests
failed
)
test_category from .\lib\python\pygrass\raster failed (1 test failed)
test_doctests from .\lib\python\pygrass\raster failed (5 tests failed)
test_numpy from .\lib\python\pygrass\raster failed (1 test failed)
test_raster_region from .\lib\python\pygrass\raster failed

the command line seems to be locked, not sure, if the tests are still
running?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241816.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Dec 17, 2015 at 2:01 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

wenzeslaus wrote
> python -m grass.gunittest.main --location nc_basic_spm_grass7
> --location-type nc

how do I know if the test has finished?

after:

C:\OSGeo4W\src\grass7>python -m grass.gunittest.main --location
nc_spm_08_grass7
--location-type nc
test_assertions from .\lib\python\gunittest failed (6 tests failed)
...

test_numpy from .\lib\python\pygrass\raster failed (1 test failed)

test_raster_region from .\lib\python\pygrass\raster failed

the command line seems to be locked, not sure, if the tests are still
running?

You can have a look to process manager what is still running there. There
might be some problems [1] when RPC interface is used in temporal or
pygrass but I'm not sure if it is the case now.

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-February/074037.html

wenzeslaus wrote

On Thu, Dec 17, 2015 at 2:01 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

wenzeslaus wrote
> python -m grass.gunittest.main --location nc_basic_spm_grass7
> --location-type nc

how do I know if the test has finished?

after:

C:\OSGeo4W\src\grass7>python -m grass.gunittest.main --location
nc_spm_08_grass7
--location-type nc
test_assertions from .\lib\python\gunittest failed (6 tests failed)
...

test_numpy from .\lib\python\pygrass\raster failed (1 test failed)

test_raster_region from .\lib\python\pygrass\raster failed

the command line seems to be locked, not sure, if the tests are still
running?

You can have a look to process manager what is still running there. There
might be some problems [1] when RPC interface is used in temporal or
pygrass but I'm not sure if it is the case now.

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-February/074037.html

in testfiles.html the last entries are:

[...]
./lib/python/pygrass/raster test_raster succeeded 6 6 0 100%
./lib/python/pygrass/raster test_raster_img succeeded 9 9 0 100%
./lib/python/pygrass/raster test_raster_region FAILED unknown unknown 0
unknown

no further entries.

I have to stop for now and post the results.

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241819.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

wenzeslaus wrote

On Thu, Dec 17, 2015 at 2:01 PM, Helmut Kudrnovsky &lt;

hellik@

&gt; wrote:

wenzeslaus wrote
> python -m grass.gunittest.main --location nc_basic_spm_grass7
> --location-type nc

how do I know if the test has finished?

after:

C:\OSGeo4W\src\grass7>python -m grass.gunittest.main --location
nc_spm_08_grass7
--location-type nc
test_assertions from .\lib\python\gunittest failed (6 tests failed)
...

test_numpy from .\lib\python\pygrass\raster failed (1 test failed)

test_raster_region from .\lib\python\pygrass\raster failed

the command line seems to be locked, not sure, if the tests are still
running?

You can have a look to process manager what is still running there. There
might be some problems [1] when RPC interface is used in temporal or
pygrass but I'm not sure if it is the case now.

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-February/074037.html

testreport_ggunittest_winGRASS71svn_64bit.zip
<http://osgeo-org.1560.x6.nabble.com/file/n5241821/testreport_ggunittest_winGRASS71svn_64bit.zip&gt;

attached the results. it seems there are no entries for the temporal tests.

HTH

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241821.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On Thu, Dec 17, 2015 at 2:15 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

wenzeslaus wrote
> On Thu, Dec 17, 2015 at 2:01 PM, Helmut Kudrnovsky &lt;

> hellik@

> &gt; wrote:
>
>> wenzeslaus wrote
>> > python -m grass.gunittest.main --location nc_basic_spm_grass7
>> > --location-type nc
>>
>> how do I know if the test has finished?
>>
>> after:
>>
>> C:\OSGeo4W\src\grass7>python -m grass.gunittest.main --location
>> nc_spm_08_grass7
>> --location-type nc
>> test_assertions from .\lib\python\gunittest failed (6 tests failed)
>> ...
>>
> test_numpy from .\lib\python\pygrass\raster failed (1 test failed)
>> test_raster_region from .\lib\python\pygrass\raster failed
>>
>> the command line seems to be locked, not sure, if the tests are still
>> running?
>>
>
> You can have a look to process manager what is still running there. There
> might be some problems [1] when RPC interface is used in temporal or
> pygrass but I'm not sure if it is the case now.
>
> [1]
https://lists.osgeo.org/pipermail/grass-dev/2015-February/074037.html

in testfiles.html the last entries are:

[...]
./lib/python/pygrass/raster test_raster succeeded 6 6
     0 100%
./lib/python/pygrass/raster test_raster_img succeeded 9 9
     0 100%
./lib/python/pygrass/raster test_raster_region FAILED unknown
unknown 0
unknown

no further entries.

This file is written as it runs individual tests. The same as in command
line.

I have to stop for now and post the results.

According to that email linked above, Ctrl+C worked for me and interrupted
just the subprocess, so I got the subsequent tests as well.

-----
best regards
Helmut
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/wingrass-daily-buidls-addons-temporary-down-tp5240948p5241819.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

On Thu, Dec 17, 2015 at 1:49 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

wenzeslaus wrote

python -m grass.gunittest.main --location nc_basic_spm_grass7
–location-type nc

tests are running, will post the results later. some are failing as it seems
some maps have different names as expected in the tests.

It requires the basic nc spm.

I suggest to link in [1] to the needed nc sample data set version for which
the tests should be run.

Done in r67208.
https://trac.osgeo.org/grass/changeset/67208

[1]
https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html