Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

[Maris Nartiss]

2021-02-17 18:28 GMT+02:00, Anna Petrášová :
>
> we need a co-mentor and ideally it wouldn't be me, since I
> may be a mentor elsewhere.

I don't have experience with OpenMP (yet), but if nobody more skilled
steps up, I could be a co-mentor. I already filled the contact form
and added myself (with a ? mark) in the wiki.

> Thanks again!
> Anna

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

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

[Huidae Cho]

Thanks. I'm not familiar with the process. The deadline for mentoring
organization applications is approaching. Have we already applied with all
those project ideas in the wiki (one application per organization I guess,
not per project idea)?

Best,
Huidae

On Wed, Feb 17, 2021 at 11:49 PM Anna Petrášová 
wrote:

>
>
> On Wed, Feb 17, 2021 at 11:51 AM Huidae Cho  wrote:
>
>> Anna,
>>
>> Thanks! I just updated the wiki and filled out the form. Will I receive
>> further communications from OSGeo (e.g., rejected, accepted, how to
>> proceed...)?
>>
>
>  I believe they will inform us about the OSGeo application status on OSGeo
> discuss and soc mailing lists. Here is the timeline:
> https://developers.google.com/open-source/gsoc/timeline
>
> Best,
> Anna
>
>>
>> Regards,
>> Huidae
>>
>> On Wed, Feb 17, 2021 at 11:29 AM Anna Petrášová 
>> wrote:
>>
>>>
>>>
>>> On Tue, Feb 16, 2021 at 2:37 PM Huidae Cho  wrote:
>>>
 Anna,

 It sounds like an interesting topic and I'm open to mentoring him even
 though I have limited experience with OpenMP. If anyone else has more
 experience with it and is interested in mentoring, that will be even 
 better.

>>>
>>> Thanks Huidae, I think you are more than qualified for being a mentor
>>> for this topic. Please put your name on the wiki page and fill out the
>>> form. If others would be interested in helping out (e.g. testing, reviews),
>>> that would be great, we need a co-mentor and ideally it wouldn't be me,
>>> since I may be a mentor elsewhere.
>>>
>>> Thanks again!
>>> Anna
>>>

 Best,
 Huidae

 On Tue, Feb 16, 2021 at 10:14 AM Anna Petrášová 
 wrote:

> Hi devs,
>
> would you consider being a GSoC mentor for this topic [1]? I suggested
> this topic in hope this could be impactful for GRASS and fairly accessible
> for students with CS background.
>
> We need somebody with C experience, ideally also OpenMP experience. I
> have only limited experience, and I would probably be mentoring a 
> different
> project, so I can't be the main mentor here.
>
> There is already a student who would be interested in that, so we need
> to make sure there is somebody who can mentor him.
>
> This is all theoretical so far, OSGeo is not even accepted yet. If you
> are interested, please also fill this form [2].
>
> Thank you for considering this,
>
> Anna
>
> [1]
> https://trac.osgeo.org/grass/wiki/GSoC/2021#Parallelizationofexistingmodules
> [2] https://forms.gle/9Na1vzGX3ESxqgpj9
>


 --
 Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
 GRASS GIS Developer
 https://idea.isnew.info

>>>
>>
>> --
>> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
>> GRASS GIS Developer
>> https://idea.isnew.info
>>
>

-- 
Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
GRASS GIS Developer
https://idea.isnew.info
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

[Anna Petrášová]

On Wed, Feb 17, 2021 at 11:51 AM Huidae Cho  wrote:

> Anna,
>
> Thanks! I just updated the wiki and filled out the form. Will I receive
> further communications from OSGeo (e.g., rejected, accepted, how to
> proceed...)?
>

 I believe they will inform us about the OSGeo application status on OSGeo
discuss and soc mailing lists. Here is the timeline:
https://developers.google.com/open-source/gsoc/timeline

Best,
Anna

>
> Regards,
> Huidae
>
> On Wed, Feb 17, 2021 at 11:29 AM Anna Petrášová 
> wrote:
>
>>
>>
>> On Tue, Feb 16, 2021 at 2:37 PM Huidae Cho  wrote:
>>
>>> Anna,
>>>
>>> It sounds like an interesting topic and I'm open to mentoring him even
>>> though I have limited experience with OpenMP. If anyone else has more
>>> experience with it and is interested in mentoring, that will be even better.
>>>
>>
>> Thanks Huidae, I think you are more than qualified for being a mentor for
>> this topic. Please put your name on the wiki page and fill out the form. If
>> others would be interested in helping out (e.g. testing, reviews), that
>> would be great, we need a co-mentor and ideally it wouldn't be me, since I
>> may be a mentor elsewhere.
>>
>> Thanks again!
>> Anna
>>
>>>
>>> Best,
>>> Huidae
>>>
>>> On Tue, Feb 16, 2021 at 10:14 AM Anna Petrášová 
>>> wrote:
>>>
 Hi devs,

 would you consider being a GSoC mentor for this topic [1]? I suggested
 this topic in hope this could be impactful for GRASS and fairly accessible
 for students with CS background.

 We need somebody with C experience, ideally also OpenMP experience. I
 have only limited experience, and I would probably be mentoring a different
 project, so I can't be the main mentor here.

 There is already a student who would be interested in that, so we need
 to make sure there is somebody who can mentor him.

 This is all theoretical so far, OSGeo is not even accepted yet. If you
 are interested, please also fill this form [2].

 Thank you for considering this,

 Anna

 [1]
 https://trac.osgeo.org/grass/wiki/GSoC/2021#Parallelizationofexistingmodules
 [2] https://forms.gle/9Na1vzGX3ESxqgpj9

>>>
>>>
>>> --
>>> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
>>> GRASS GIS Developer
>>> https://idea.isnew.info
>>>
>>
>
> --
> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
> GRASS GIS Developer
> https://idea.isnew.info
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-user] Code sprint is now (OGC-OSGeo-ASF 2021)

[Moritz Lennert]

Am 17. Februar 2021 17:40:03 MEZ schrieb Luca Delucchi :
>Hi all,
>
>On Wed, 17 Feb 2021 at 17:29, Vaclav Petras  wrote:
>>
>> Code sprint is now!
>>
>
>I'm trying to connect sometime, specially during Italian evening time
>
>>
>> Post you plan here:
>>
>> https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/issues/2
>>
>
>could make sense to start a v.in.ogc.features to import features from
>OGC API Feature service using owslib library?

+1

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

[GRASS-dev] Moving to Black for Python formatting

[Vaclav Petras]

Dear all,

At this moment, we don't use an automatic formatter for Python code and we
have only limited enforcement of basic formatting rules. This is changing
as we are moving towards PEP8 formatting compliance and automatic Flake8
checks.

We need an automatic formatter and enforcement in the CI. There seems to be
a clear candidate for that and that is Black (The uncompromising code
formatter) which was already suggested in 2019:

https://lists.osgeo.org/pipermail/grass-dev/2019-May/092654.html

See details about how that applies to GRASS here:

https://github.com/OSGeo/grass/issues/543

Here is a first PR (ready to be merged) which makes changes to content of
scripts and adds a automatic check:

https://github.com/OSGeo/grass/pull/1347

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

Re: [GRASS-dev] Source code layout reorganization for G8

[Vaclav Petras]

tools -> utils
https://github.com/OSGeo/grass/pull/1348

include/*.h -> include/grass/*.h
https://github.com/OSGeo/grass/pull/1350

lib/python -> python/grass
https://github.com/OSGeo/grass/pull/1356
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] grass-dev Digest, Vol 180, Issue 22

[Michael Barton]

Denis,

Thanks for the detailed response. From the sound of it, and from some other 
responses, the multi-res arguments should probably be removed or commented out 
until they actually work and are documented.

Also, I'm not sure what is the best to call the ratio of the geomorphon polygon 
and a maximum search circle. Perhaps relative extent or relative coverage. But 
it is not "extend". That is the wrong English word for this.

I'll make an issue so that this can be easier to deal with.

Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://shesc.asu.edu, https://complexity.asu.edu, 
http://www.public.asu.edu/~cmbarton

On Feb 16, 2021, at 7:36 AM, 
grass-dev-requ...@lists.osgeo.org 
wrote:

Date: Tue, 16 Feb 2021 02:56:48 +
From: Denis Ovsienko mailto:de...@ovsienko.info>>
To: grass-dev@lists.osgeo.org
Subject: Re: [GRASS-dev] r.geomorphon multiresolution mode
Message-ID: <20210216025648.6b98d46d@basepc>
Content-Type: text/plain; charset=US-ASCII

On Mon, 15 Feb 2021 22:23:09 +
Michael Barton mailto:michael.bar...@asu.edu>> wrote:

Can anyone explain how multiresolution model works in r.geomorphon?
It does not seem to respond to any setting changes and seems to
always produce blank maps (testing with NC demo set). There is
nothing about multiresolution mode in the manual for 7.8 or 7.9

Hello Michael.

I had applied a few rounds of cleanups and improvements to this
plugin, one of which was directly related to multires (see commit
867ff057b). Other than that, I didn't study multires closely, but
managed to notice earlier that start_distance and step_distance (which
are derived from the command-line arguments) are never used in the main
multires branch, which also overrides the value of num_of_steps with a
hard-coded value of 5, but I had more pressing problems to solve in the
non-multires branch of main() at the time.

Having looked through the multires branch again just now, it does not
look right that after the call to calc_pattern() the code does not have
a call to determine_form(), the output of which ought to go into
multiple_output[i].forms_buffer before Rast_put_row() stores it. That
would explain why you have blank outputs. That said, I still do not
understand the intended difference between the multiple output rasters.

Also, I think there is a typo in the manual and arguments. I think
that what is meant is the word "extent" (a noun for area) rather than
"extend" (a verb to make larger). I can make an issue for this typo
if helpful.

If you take the 8 cardinal points of a geomorphon without the
elevations, the plane figure will be an octagon (a degenerate one when
more than two cardinal points end up in the centre). In any case, it
will always be a so called simple polygon, let's call its area S1.

If you take a fixed search radius, draw a circle and intersect it with
the 8 cardinal directions (in other word, if you consider the regular
convex case of the above figure), its maximum possible area (let's call
it S2) will be a function of the search radius.

So what is currently known as the "extend" output of r.geomorphon is
S1/S2, hence its value belongs to the [0.0, 1.0] interval. I agree this
might be not the right term, although I am not sure what would be the
most appropriate geometric term in English. For what it is worth, the
function that computes S1 is currently called "extends()", and both the
G_parser props and the HTML document currently give an incorrect
description of what the "extend" output produces, so that would be best
made consistent in the same go.

There are some other long-standing imperfections in both the C code and
the HTML documentation of r.geomorphon, if you have time now to work on
these, I could suggest a few points. That said, it would be nice not to
re-jig r.geomorphon in substantial ways right now, because it is
serving as a foundation for Geomorphon Profiler, and I am busy
finishing another layer of software on top of these two, so a student
can finally get their thesis done.

--
   Denis Ovsienko

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

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

[Huidae Cho]

Anna,

Thanks! I just updated the wiki and filled out the form. Will I receive
further communications from OSGeo (e.g., rejected, accepted, how to
proceed...)?

Regards,
Huidae

On Wed, Feb 17, 2021 at 11:29 AM Anna Petrášová 
wrote:

>
>
> On Tue, Feb 16, 2021 at 2:37 PM Huidae Cho  wrote:
>
>> Anna,
>>
>> It sounds like an interesting topic and I'm open to mentoring him even
>> though I have limited experience with OpenMP. If anyone else has more
>> experience with it and is interested in mentoring, that will be even better.
>>
>
> Thanks Huidae, I think you are more than qualified for being a mentor for
> this topic. Please put your name on the wiki page and fill out the form. If
> others would be interested in helping out (e.g. testing, reviews), that
> would be great, we need a co-mentor and ideally it wouldn't be me, since I
> may be a mentor elsewhere.
>
> Thanks again!
> Anna
>
>>
>> Best,
>> Huidae
>>
>> On Tue, Feb 16, 2021 at 10:14 AM Anna Petrášová 
>> wrote:
>>
>>> Hi devs,
>>>
>>> would you consider being a GSoC mentor for this topic [1]? I suggested
>>> this topic in hope this could be impactful for GRASS and fairly accessible
>>> for students with CS background.
>>>
>>> We need somebody with C experience, ideally also OpenMP experience. I
>>> have only limited experience, and I would probably be mentoring a different
>>> project, so I can't be the main mentor here.
>>>
>>> There is already a student who would be interested in that, so we need
>>> to make sure there is somebody who can mentor him.
>>>
>>> This is all theoretical so far, OSGeo is not even accepted yet. If you
>>> are interested, please also fill this form [2].
>>>
>>> Thank you for considering this,
>>>
>>> Anna
>>>
>>> [1]
>>> https://trac.osgeo.org/grass/wiki/GSoC/2021#Parallelizationofexistingmodules
>>> [2] https://forms.gle/9Na1vzGX3ESxqgpj9
>>>
>>
>>
>> --
>> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
>> GRASS GIS Developer
>> https://idea.isnew.info
>>
>

-- 
Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
GRASS GIS Developer
https://idea.isnew.info
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Code sprint is now (OGC-OSGeo-ASF 2021)

[Luca Delucchi]

Hi all,

On Wed, 17 Feb 2021 at 17:29, Vaclav Petras  wrote:
>
> Code sprint is now!
>

I'm trying to connect sometime, specially during Italian evening time

>
> Post you plan here:
>
> https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/issues/2
>

could make sense to start a v.in.ogc.features to import features from
OGC API Feature service using owslib library?

>
> Vaclav

-- 
ciao
Luca

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

[GRASS-dev] Code sprint is now (OGC-OSGeo-ASF 2021)

[Vaclav Petras]

Code sprint is now!

Agenda and all:

https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/

GRASS GIS page (edit using a PR):

https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/blob/master/group/OSGeoGRASS.adoc

List of OSGeo participants (add yourself):

https://wiki.osgeo.org/wiki/Joint_OGC_OSGeo_ASF_Sprint_2021

Post you plan here:

https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021/issues/2

Working on stuff in the main repo? Add it here:

https://github.com/OSGeo/grass/projects/5

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

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

[Anna Petrášová]

On Tue, Feb 16, 2021 at 2:37 PM Huidae Cho  wrote:

> Anna,
>
> It sounds like an interesting topic and I'm open to mentoring him even
> though I have limited experience with OpenMP. If anyone else has more
> experience with it and is interested in mentoring, that will be even better.
>

Thanks Huidae, I think you are more than qualified for being a mentor for
this topic. Please put your name on the wiki page and fill out the form. If
others would be interested in helping out (e.g. testing, reviews), that
would be great, we need a co-mentor and ideally it wouldn't be me, since I
may be a mentor elsewhere.

Thanks again!
Anna

>
> Best,
> Huidae
>
> On Tue, Feb 16, 2021 at 10:14 AM Anna Petrášová 
> wrote:
>
>> Hi devs,
>>
>> would you consider being a GSoC mentor for this topic [1]? I suggested
>> this topic in hope this could be impactful for GRASS and fairly accessible
>> for students with CS background.
>>
>> We need somebody with C experience, ideally also OpenMP experience. I
>> have only limited experience, and I would probably be mentoring a different
>> project, so I can't be the main mentor here.
>>
>> There is already a student who would be interested in that, so we need to
>> make sure there is somebody who can mentor him.
>>
>> This is all theoretical so far, OSGeo is not even accepted yet. If you
>> are interested, please also fill this form [2].
>>
>> Thank you for considering this,
>>
>> Anna
>>
>> [1]
>> https://trac.osgeo.org/grass/wiki/GSoC/2021#Parallelizationofexistingmodules
>> [2] https://forms.gle/9Na1vzGX3ESxqgpj9
>>
>
>
> --
> Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大
> GRASS GIS Developer
> https://idea.isnew.info
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1839: Install.make should honor $DESTDIR

[GRASS GIS]

#1839: Install.make should honor $DESTDIR
---+-
  Reporter:  vince |  Owner:  grass-dev@…
  Type:  defect| Status:  closed
  Priority:  normal|  Milestone:  7.0.7
 Component:  Installation  |Version:  svn-trunk
Resolution:  wontfix   |   Keywords:  DESTDIR
   CPU:  OSX/Intel |   Platform:  MacOSX
---+-

Comment (by nila):

 DESTDIR support added with commit
 
​[https://github.com/OSGeo/grass/commit/daa8cd7f96060685901e7fa990a9d4ba96da9398
 daa8cd7] to master.

-- 
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] #764: Can the install process accept a DESTDIR additional variable?

[GRASS GIS]

#764: Can the install process accept a DESTDIR additional variable?
---+-
  Reporter:  vince |  Owner:  grass-dev@…
  Type:  enhancement   | Status:  closed
  Priority:  minor |  Milestone:  8.0.0
 Component:  Installation  |Version:  git-releasebranch78
Resolution:  fixed |   Keywords:  install DESTDIR
   CPU:  All   |   Platform:  All
---+-
Changes (by nila):

 * status:  new => closed
 * resolution:   => fixed


-- 
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] #764: Can the install process accept a DESTDIR additional variable?

[GRASS GIS]

#764: Can the install process accept a DESTDIR additional variable?
---+-
  Reporter:  vince |  Owner:  grass-dev@…
  Type:  enhancement   | Status:  new
  Priority:  minor |  Milestone:  8.0.0
 Component:  Installation  |Version:  git-releasebranch78
Resolution:|   Keywords:  install DESTDIR
   CPU:  All   |   Platform:  All
---+-

Comment (by nila):

 DESTDIR support added with commit
 [https://github.com/OSGeo/grass/commit/daa8cd7f96060685901e7fa990a9d4ba96da9398
 daa8cd7] to master.

-- 
Ticket URL: 
GRASS GIS 

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