[GRASS-dev] adding 2 more modules to G7 SVNimagery

GRASS GRASS developer
1

Hello,

I would like to complete the i.evapo.* series of modules from
grass-addons/imagery/gipe with these two last ones.
i.evapo.potrad: potential radiation (Bastiaanssen, 1995)
i.evapo.senay: Actual evapotranspiration (Senay, 2007)

They have been upgraded to SVN code in the grass-addons directories
and now waiting for your syntax check and approval for migration to
Grass7.

Yann

--
Yann Chemin
www.csu.edu.au

2

Hi Yann,

On 1/23/11, Yann Chemin <yann.chemin@gmail.com> wrote:

Hello,

I would like to complete the i.evapo.* series of modules from
grass-addons/imagery/gipe with these two last ones.
i.evapo.potrad: potential radiation (Bastiaanssen, 1995)
i.evapo.senay: Actual evapotranspiration (Senay, 2007)

would it be possible to make one single i.evapo module
and manage the methods via method=xx parameter?

Markus

3

Yes theoretically same for i.eb.* modules. Practically, it will be
some work and maybe creating maintenance trouble.

When I was thinking about i.eb.toolbox two issues were there first:
1-Coding blocks from each module to be kept separated somehow for
maintenance/bug fixing reasons
2-possibility to have a module tab dedicated to each type of tool,
with the possibility of input parameters to appear in two or more
tabs.

Rest is sweat and debugging and unforeseen problems

I would appreciate comments from experienced coders about integrating
many tools in one.

Yann

Yann Chemin
www.csu.edu.au

On 23/01/2011, at 21:05, Markus Neteler <neteler@osgeo.org> wrote:

Hi Yann,

On 1/23/11, Yann Chemin <yann.chemin@gmail.com> wrote:

Hello,

I would like to complete the i.evapo.* series of modules from
grass-addons/imagery/gipe with these two last ones.
i.evapo.potrad: potential radiation (Bastiaanssen, 1995)
i.evapo.senay: Actual evapotranspiration (Senay, 2007)

would it be possible to make one single i.evapo module
and manage the methods via method=xx parameter?

Markus

4

Hello Yann,
while adding new i.eb.* modules it would be great if you can check
this ticket: http://trac.osgeo.org/grass/ticket/899
Maybe it is obsolete now?

Best regards
Soeren

2011/1/23 Yann Chemin <yann.chemin@gmail.com>:

Yes theoretically same for i.eb.* modules. Practically, it will be
some work and maybe creating maintenance trouble.

When I was thinking about i.eb.toolbox two issues were there first:
1-Coding blocks from each module to be kept separated somehow for
maintenance/bug fixing reasons
2-possibility to have a module tab dedicated to each type of tool,
with the possibility of input parameters to appear in two or more
tabs.

Rest is sweat and debugging and unforeseen problems

I would appreciate comments from experienced coders about integrating
many tools in one.

Yann

Yann Chemin
www.csu.edu.au

On 23/01/2011, at 21:05, Markus Neteler <neteler@osgeo.org> wrote:

Hi Yann,

On 1/23/11, Yann Chemin <yann.chemin@gmail.com> wrote:

Hello,

I would like to complete the i.evapo.* series of modules from
grass-addons/imagery/gipe with these two last ones.
i.evapo.potrad: potential radiation (Bastiaanssen, 1995)
i.evapo.senay: Actual evapotranspiration (Senay, 2007)

would it be possible to make one single i.evapo module
and manage the methods via method=xx parameter?

Markus

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

5

Thank you Soeren
Most of this request is the process I am going through with few
students/colleagues now for the i.evapo.* modules, the most
significant users orientated output being located in
grass-promo/tutorials/grass_landsat5_ETa and friends as this is the
most used level.
A deeper level is i.eb.* where one can model thermodynamic parts of
the sensible heat flux. As seen in i.eb.h_* there Monin-Obhukov length
is defined by sensible heat flux, but defines the diabetic corrections
(psi_*), so most of the time an iteration process is adopted to solve
the system. i.eb.* are designed to give most controls in solving this
through scripting without dwelling in those standard equations.

In R (RemoteSensing) and in a python lib, all this is available as API
for manipulations as high-level scripting permit it.

Yann Chemin
www.csu.edu.au

On 24/01/2011, at 7:45, Soeren Gebbert <soerengebbert@googlemail.com> wrote:

Hello Yann,
while adding new i.eb.* modules it would be great if you can check
this ticket: http://trac.osgeo.org/grass/ticket/899
Maybe it is obsolete now?

Best regards
Soeren

2011/1/23 Yann Chemin <yann.chemin@gmail.com>:

Yes theoretically same for i.eb.* modules. Practically, it will be
some work and maybe creating maintenance trouble.

When I was thinking about i.eb.toolbox two issues were there first:
1-Coding blocks from each module to be kept separated somehow for
maintenance/bug fixing reasons
2-possibility to have a module tab dedicated to each type of tool,
with the possibility of input parameters to appear in two or more
tabs.

Rest is sweat and debugging and unforeseen problems

I would appreciate comments from experienced coders about integrating
many tools in one.

Yann

Yann Chemin
www.csu.edu.au

On 23/01/2011, at 21:05, Markus Neteler <neteler@osgeo.org> wrote:

Hi Yann,

On 1/23/11, Yann Chemin <yann.chemin@gmail.com> wrote:

Hello,

I would like to complete the i.evapo.* series of modules from
grass-addons/imagery/gipe with these two last ones.
i.evapo.potrad: potential radiation (Bastiaanssen, 1995)
i.evapo.senay: Actual evapotranspiration (Senay, 2007)

would it be possible to make one single i.evapo module
and manage the methods via method=xx parameter?

Markus

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

6

Looking at the various i.evapo.* modules, it will be a cumbersome task
to fuse them into one code, and a even more confusing input
arrangement for the user.

What are other options within Grass 7 experimental?

On 24 January 2011 08:24, Yann Chemin <yann.chemin@gmail.com> wrote:

Thank you Soeren
Most of this request is the process I am going through with few
students/colleagues now for the i.evapo.* modules, the most
significant users orientated output being located in
grass-promo/tutorials/grass_landsat5_ETa and friends as this is the
most used level.
A deeper level is i.eb.* where one can model thermodynamic parts of
the sensible heat flux. As seen in i.eb.h_* there Monin-Obhukov length
is defined by sensible heat flux, but defines the diabetic corrections
(psi_*), so most of the time an iteration process is adopted to solve
the system. i.eb.* are designed to give most controls in solving this
through scripting without dwelling in those standard equations.

In R (RemoteSensing) and in a python lib, all this is available as API
for manipulations as high-level scripting permit it.

Yann Chemin
www.csu.edu.au

On 24/01/2011, at 7:45, Soeren Gebbert <soerengebbert@googlemail.com> wrote:

Hello Yann,
while adding new i.eb.* modules it would be great if you can check
this ticket: http://trac.osgeo.org/grass/ticket/899
Maybe it is obsolete now?

Best regards
Soeren

2011/1/23 Yann Chemin <yann.chemin@gmail.com>:

Yes theoretically same for i.eb.* modules. Practically, it will be
some work and maybe creating maintenance trouble.

When I was thinking about i.eb.toolbox two issues were there first:
1-Coding blocks from each module to be kept separated somehow for
maintenance/bug fixing reasons
2-possibility to have a module tab dedicated to each type of tool,
with the possibility of input parameters to appear in two or more
tabs.

Rest is sweat and debugging and unforeseen problems

I would appreciate comments from experienced coders about integrating
many tools in one.

Yann

Yann Chemin
www.csu.edu.au

On 23/01/2011, at 21:05, Markus Neteler <neteler@osgeo.org> wrote:

Hi Yann,

On 1/23/11, Yann Chemin <yann.chemin@gmail.com> wrote:

Hello,

I would like to complete the i.evapo.* series of modules from
grass-addons/imagery/gipe with these two last ones.
i.evapo.potrad: potential radiation (Bastiaanssen, 1995)
i.evapo.senay: Actual evapotranspiration (Senay, 2007)

would it be possible to make one single i.evapo module
and manage the methods via method=xx parameter?

Markus

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

--
Yann Chemin