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

2018-04-25 Thread Martin Landa 
Hi,

2018-04-25 23:16 GMT+02:00 Helmut Kudrnovsky :
> As daily winGRASS builds seems to be broken for some times now, it may be
> needed to find a way to test the RCs.

apparently something wrong with server again, what a pain. Will
investigate more. Thanks for pointer. Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

2018-04-25 Thread Helmut Kudrnovsky 
Markus Neteler wrote
> Hi devs,
> 
> according to our roadmap [1] it is time to prepare 7.4.1RC1:
> 
> Time schedule:
> 
> Proposal of release: ~14 Mar
> Soft freeze of release branch: ~23 Mar
> RC1: ~23 Apr   <<-- we are here
> RC2: ~7 May
> Final release: ~14 May
> 
> We have no blockers any more [2].
> 
> If there are no objections, I'll prepare RC1 in the next few days.

+1

As daily winGRASS builds seems to be broken for some times now, it may be
needed to find a way to test the RCs.




-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [release planning] 7.4.1

2018-04-25 Thread Markus Neteler 
Hi devs,

according to our roadmap [1] it is time to prepare 7.4.1RC1:

Time schedule:

Proposal of release: ~14 Mar
Soft freeze of release branch: ~23 Mar
RC1: ~23 Apr   <<-- we are here
RC2: ~7 May
Final release: ~14 May

We have no blockers any more [2].

If there are no objections, I'll prepare RC1 in the next few days.

Markus

[1] https://trac.osgeo.org/grass/milestone/7.4.1
[2] 
https://trac.osgeo.org/grass/query?status=new=assigned=reopened=7.4.1=7.4.0=type=priority


-- 

Markus Neteler, PhD
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC introduction Roberta Fagandini

2018-04-25 Thread Roberta Fagandini 
2018-04-25 16:03 GMT+02:00 Moritz Lennert :

> Hi Roberta,


Hi Moritz,


>
> On 24/04/18 13:55, Roberta Fagandini wrote:
>
>> 2018-04-24 13:15 GMT+02:00 Moritz Lennert > >:
>>
>>
>> Hi Roberta,
>>
>>
>> Hi Moritz!
>>
>>
>> On 24/04/18 13:01, Roberta Fagandini wrote:
>>
>> Hi all!
>> I'm Roberta Fagandini, Ph.D. student at Politecnico of Milano.
>> My proposal "GRASS GIS module for Sentinel-2 cloud and shadow
>> detection" has been accepted therefore I've been selected for
>> the GSoC 2018.
>> I'm glad to start contributing to OSGeo and especially to GRASS
>> GIS with the help of my mentors Roberto Marzocchi and Moritz
>> Lennert.
>>
>> My project consists in the realization of a GRASS GIS module for
>> the detection of clouds and their shadows in Sentinel-2 images
>> without using time series.
>> Below you can find the link to my proposal:
>>
>> https://docs.google.com/document/d/1mQyouqbHGHugn5DjEDZI3hc1
>> eU_bT_b0qLJPPwkt_hk/edit?usp=sharing
>> > 1eU_bT_b0qLJPPwkt_hk/edit?usp=sharing>
>>
>> I would be grateful if you could have a look at the proposal and
>> provide any suggestions.
>> Every feedback is welcome and it will be useful to improve my
>> project.
>>
>> I'm waiting for the writing access to the OSGeo wiki, therefore,
>> I will share my wiky page as soon as possible.
>>
>> Thanks for this great opportunity!
>>
>>
>> It is great to have you with us ! I'm looking forward to working
>> with you on this project.
>>
>>
>> First of all I want to thank you for being my mentor!
>>
>> The first thing I would love to see is your existing python script
>> to get a better understanding of the exact approach you are planning
>> on implementing.
>>
>>
>> Depending on what tool you prefer, you can either set up a github
>> repository for the project, or you could also use the sandbox in the
>> GRASS svn [1]. You could then share your code there.
>>
>>
>> A the moment I have only some bash script. I'm testing different
>> procedures for shadows detection, which is the task that is creating more
>> troubles at the moment.  Anyway, I already had the intention of setting up
>> a github repository for the project therefore, I hope to share it as soon
>> as possible.
>>
>>
>
> Please also set up a wiki page about your project. See [0] for examples
> from last year.
>

Sure, tomorrow I'm going to set up the wiki page!


>
> Looking at your bash scripts, I think the first thing to do during this
> bonding period is, as you planned yourself, to get familiar with the
> writing of GRASS modules in Python. You can have a look at existing scripts
> [1, 2] to get feeling for this works and how to structure addon code in
> order to make it directly installable with g.extension.
>
> You can find the actual function definitions and documentation of the
> GRASS Python scripting library at [3]. The functions in that library should
> be more than enough to translate your scripts into a (or several) modules.
>
> Be aware that GRASS modules create their own GUI. So, unless you need some
> interactive features in your modules, you will not have to program your own
> GUI.
>

Thank you for your precious suggestions! I'll start studying how to write a
GRASS module in Python in the next days and at the same time I will keep on
testing the procedures so as to show you some results and fix some open
points.


>
> Something else you should probably do during this bonding time is to
> elaborate a schema of your algorithm, so that it is easier to understand
> what it does at each step.
>

Yes, this could be very useful also for me in order to better organize and
put in order everything!


>
> Best wishes,
> Moritz
>

Thanks again!
Best regards,
Roberta


>
>
> [0] https://trac.osgeo.org/grass/wiki/GSoC
> [1] https://trac.osgeo.org/grass/browser/grass/trunk/scripts
> [2] https://trac.osgeo.org/grass/browser/grass-addons/grass7
> [3] https://grass.osgeo.org/grass75/manuals/libpython/script_intro.html
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC introduction Roberta Fagandini

2018-04-25 Thread Moritz Lennert 

Hi Roberta,

On 24/04/18 13:55, Roberta Fagandini wrote:
2018-04-24 13:15 GMT+02:00 Moritz Lennert >:


Hi Roberta,


Hi Moritz!


On 24/04/18 13:01, Roberta Fagandini wrote:

Hi all!
I'm Roberta Fagandini, Ph.D. student at Politecnico of Milano.
My proposal "GRASS GIS module for Sentinel-2 cloud and shadow
detection" has been accepted therefore I've been selected for
the GSoC 2018.
I'm glad to start contributing to OSGeo and especially to GRASS
GIS with the help of my mentors Roberto Marzocchi and Moritz
Lennert.

My project consists in the realization of a GRASS GIS module for
the detection of clouds and their shadows in Sentinel-2 images
without using time series.
Below you can find the link to my proposal:


https://docs.google.com/document/d/1mQyouqbHGHugn5DjEDZI3hc1eU_bT_b0qLJPPwkt_hk/edit?usp=sharing



I would be grateful if you could have a look at the proposal and
provide any suggestions.
Every feedback is welcome and it will be useful to improve my
project.

I'm waiting for the writing access to the OSGeo wiki, therefore,
I will share my wiky page as soon as possible.

Thanks for this great opportunity!


It is great to have you with us ! I'm looking forward to working
with you on this project.


First of all I want to thank you for being my mentor!

The first thing I would love to see is your existing python script
to get a better understanding of the exact approach you are planning
on implementing.


Depending on what tool you prefer, you can either set up a github
repository for the project, or you could also use the sandbox in the
GRASS svn [1]. You could then share your code there.


A the moment I have only some bash script. I'm testing different 
procedures for shadows detection, which is the task that is creating 
more troubles at the moment.  Anyway, I already had the intention of 
setting up a github repository for the project therefore, I hope to 
share it as soon as possible.





Please also set up a wiki page about your project. See [0] for examples 
from last year.


Looking at your bash scripts, I think the first thing to do during this 
bonding period is, as you planned yourself, to get familiar with the 
writing of GRASS modules in Python. You can have a look at existing 
scripts [1, 2] to get feeling for this works and how to structure addon 
code in order to make it directly installable with g.extension.


You can find the actual function definitions and documentation of the 
GRASS Python scripting library at [3]. The functions in that library 
should be more than enough to translate your scripts into a (or several) 
modules.


Be aware that GRASS modules create their own GUI. So, unless you need 
some interactive features in your modules, you will not have to program 
your own GUI.


Something else you should probably do during this bonding time is to 
elaborate a schema of your algorithm, so that it is easier to understand 
what it does at each step.


Best wishes,
Moritz


[0] https://trac.osgeo.org/grass/wiki/GSoC
[1] https://trac.osgeo.org/grass/browser/grass/trunk/scripts
[2] https://trac.osgeo.org/grass/browser/grass-addons/grass7
[3] https://grass.osgeo.org/grass75/manuals/libpython/script_intro.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3348: wxGTK3: Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton

2018-04-25 Thread GRASS GIS 
#3348: wxGTK3: Gtk-CRITICAL **: gtk_box_gadget_distribute: assertion 'size >= 0'
failed in GtkSpinButton
--+-
  Reporter:  neteler  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.4
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  wxGUI
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mlennert):

 I'm also getting a lot of these messages, but the amount depends on the
 size I allow for the GUI window of d.vect or d.rast. Using a tabbed window
 manager, I get many of such messages when I add the GUI windows next to
 many existing windows. However, when I provide a +/- full screen for the
 GUI window, I get only very few such messages.

 I can confirm that the width widgets in the Line tab cause a lot of these
 messages. The same goes for the label_size widget in the Labels tab.

 When launching the d.rast GUI window in tabbed window mode, I get a lot of
 these messages:


 {{{
 gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkNotebook
 }}}

 I get quite a lot of these messages also when I launch d.vect --ui, but
 with tabs on top, not on the left.

 In short: it seems that this really depends on window layout, which it
 shouldn't. Whatever the window layout, we shouldn't see our terminals
 flooded with such messages. Is there any way of making this more robust ?

-- 
Ticket URL: 
GRASS GIS 

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