Re: [GRASS-dev] [GRASS GIS] #3434: GUI: Make metadata accessible in Data tab

[GRASS GIS]

#3434: GUI: Make metadata accessible in Data tab
--+
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  Data tab, metadata
   CPU:  Unspecified  |   Platform:  All
--+

Comment (by annakrat):

 This is already implemented in trunk, please feel free to test it.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Does multi-threading apply to r.series.lwr?

[Markus Metz]

On Fri, Nov 3, 2017 at 7:08 PM, Nikos Alexandris 
wrote:
>
> Before processing tens of thousands of Landsat8 TIRS bands, a script
> tests the workflow described below, for 74 scenes, that correspond to one
> WRS2 tile.
>
>
> The script takes as inputs:
>
>  path to directory with Landsat scenes
>  regex pattern to match a set of Landsat scene identifiers
>  land cover map
>  path to the GRASS GIS data base
>  name for the GRASS GIS Location
>  name for the GRASS GIS Mapset to host maps to build a time
series
>  an odd integer, parameter for a split-window algorithm (SW)
>
>
> Part 1 of the workflow derives Land Surface Temperature maps by:
>
> 1. Creating the target Location
> 2. Linking pseudo GRASS raster maps to Landsat8 GeoTIFF files
> 3. Exporting a TGIS-compliant list of maps and timestamps
> 4. Importing a land cover map required for the SW algorithm
> 5. Estimating Land Surface Temperature (LST) maps for given scenes
(i.landsat8.swlst)
> 6. Creating a dedicated Mapset for LST maps
> 7. Copying LST maps in the "LST" Mapset
> 8. Removing initial LST maps from individual scene Mapsets
>
>
> With a somewhat strong CPU, producing one LST map (7771 rows by 7651
> columns = 59455921 cells), takes ~34 minutes.
>
> For 74 Landsat8 input scenes, first trials took about 42 hours, running
> grass-7.3.svn inside a docker container, albeit assigned one CPU.
>
>
> Part 2 concerns building Time Series by:
>
> 1. Creating and LST Spatio-Temporal Raster Dara Set (STRDS)
> 2. Registering LST maps in TGIS' data base
> 3. Smoothing the LST STRDS via Local Weighted Regression (r.series.lwr)
> 4. Timestamping Local-Weight-Regression derived maps
> 5. Creating an STRDS for LWR maps
> 6. Registering LWR maps in TGIS' data base
>
>
> Part 2 took about 130 minutes including all steps. Obviously, step 3 is
> practically the consumer.
>
>
> Overall it took about 44 hours to build an LWR Smoothed LST STRDS.
>
> After proofing the concept, good use of the cluster concerns steps 2, 5,
> 7 and 8 (of Part 1). Processes that can/should run in parallel, in an
> (admittedly heterogeneous) cluster that consists of 912 cores.
>
> Final concern is if multi-threading applies to r.series.lwr (step 3 of
> Part 2).

You could
1. create different temporal chunks of the time series, each chunk will be
processed by r.series.lwr, all chunks can be processed in parallel.
2. create different spatial chunks of the time series (tiling the
computational region), each chunk will be processed by r.series.lwr, all
chunks can be processed in parallel.

HTH,

Markus M
>
> Thank you, Nikos
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Does multi-threading apply to r.series.lwr?

[Nikos Alexandris]

Before processing tens of thousands of Landsat8 TIRS bands, a script
tests the workflow described below, for 74 scenes, that correspond to one
WRS2 tile.


The script takes as inputs:

 path to directory with Landsat scenes
 regex pattern to match a set of Landsat scene identifiers
 land cover map
 path to the GRASS GIS data base
 name for the GRASS GIS Location
 name for the GRASS GIS Mapset to host maps to build a time series
 an odd integer, parameter for a split-window algorithm (SW)


Part 1 of the workflow derives Land Surface Temperature maps by:

1. Creating the target Location
2. Linking pseudo GRASS raster maps to Landsat8 GeoTIFF files
3. Exporting a TGIS-compliant list of maps and timestamps
4. Importing a land cover map required for the SW algorithm
5. Estimating Land Surface Temperature (LST) maps for given scenes 
(i.landsat8.swlst)
6. Creating a dedicated Mapset for LST maps
7. Copying LST maps in the "LST" Mapset
8. Removing initial LST maps from individual scene Mapsets


With a somewhat strong CPU, producing one LST map (7771 rows by 7651
columns = 59455921 cells), takes ~34 minutes.

For 74 Landsat8 input scenes, first trials took about 42 hours, running
grass-7.3.svn inside a docker container, albeit assigned one CPU.


Part 2 concerns building Time Series by:

1. Creating and LST Spatio-Temporal Raster Dara Set (STRDS)
2. Registering LST maps in TGIS' data base
3. Smoothing the LST STRDS via Local Weighted Regression (r.series.lwr)
4. Timestamping Local-Weight-Regression derived maps
5. Creating an STRDS for LWR maps
6. Registering LWR maps in TGIS' data base


Part 2 took about 130 minutes including all steps. Obviously, step 3 is
practically the consumer.


Overall it took about 44 hours to build an LWR Smoothed LST STRDS.

After proofing the concept, good use of the cluster concerns steps 2, 5,
7 and 8 (of Part 1). Processes that can/should run in parallel, in an
(admittedly heterogeneous) cluster that consists of 912 cores.

Final concern is if multi-threading applies to r.series.lwr (step 3 of
Part 2).

Thank you, Nikos


signature.asc
Description: PGP signature
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] 7.4.0

[Markus Neteler]

On Thu, Nov 2, 2017 at 4:18 PM, Luca Delucchi  wrote:
> On 2 October 2017 at 23:35, Markus Neteler  wrote:
>
>>
>> ###
>> v.clip: NC dataset
>> https://grass.osgeo.org/grass72/manuals/addons/v.clip.html
>>
>> A clip test could be made by counting points falling into a polygon,
>> similar to the example in the manual page.
>>
>
> added tests in r71627.

thanks!

v.clip addon moved to trunk in r71634 for further testing.

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] 7.4.0

[Markus Neteler]

On Thu, Nov 2, 2017 at 4:56 PM, Luca Delucchi  wrote:
> On 2 October 2017 at 23:35, Markus Neteler  wrote:
>
>>
>> ###
>> r.geomorphon:
>> --> in the directory is an initial "test_rgeomorphon_NC.sh"
>>
> added in r71628.

great, thanks!

Copied to trunk in r71632 (in addition, I fixed some C++ style comments).

> I don't know if you want to remove the .sh file

I did not transfer it.

Please test r.geomorphon in trunk (alias 7.3.svn).

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3427: Ask for improvement of i.segment.stats : Allow parallel work for different rasters

[GRASS GIS]

#3427: Ask for improvement of i.segment.stats : Allow parallel work for 
different
rasters
--+-
  Reporter:  tgrippa  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:
 Component:  Addons   |Version:  unspecified
Resolution:  fixed|   Keywords:  segment
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by tgrippa):

 Tested on Linux Mint 18.1 (MATE 64bits) and GRASS 7.3.svn (r71315). Works
 perfectly. Thanks for the improvement.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3434: GUI: Make metadata accessible in Data tab

[GRASS GIS]

#3434: GUI: Make metadata accessible in Data tab
--+
  Reporter:  sbl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.4.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  Data tab, metadata
   CPU:  Unspecified  |   Platform:  All
--+
Changes (by martinl):

 * keywords:  Data tab => Data tab, metadata
 * milestone:   => 7.4.0


--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3434: GUI: Make metadata accessible in Data tab

[GRASS GIS]

#3434: GUI: Make metadata accessible in Data tab
-+-
 Reporter:  sbl  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:
Component:  wxGUI|Version:  svn-trunk
 Keywords:  Data tab |CPU:  Unspecified
 Platform:  All  |
-+-
 It would be nice if metadata (v.info, r.info) of the listed maps could be
 made available in the data tab in the wxGUI, e.g. in the context menu.
 Can save some clicks and can help to quickly understand what the data is
 about...

--
Ticket URL: 
GRASS GIS 

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