[GRASS-dev] [Report #2] Kriging with GRASS and R: v.autokrige port to wxPython and more

GRASS GRASS developer
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

there are some important news about the module!

First of all, the interface is almost finished. See a screenshot on the
wiki page [0].
The layout includes a notebook with a page for each R package (automap,
gstat and geoR), with the available options. Another layout could be a
chiocebox wht the three packages on the top of Kriging section, that
redraws the section accourding to the user's choice.
Let me know which one do you prefer, feel free also to suggest something
new.

The R-GRASS integration is on its way: autofitting the variogram on a
map obtained from a DEM sample [1] works in the proof of concept. rpy2
is extremely helpful and does not require much more code than the
original R code. More to come in the next days.

The idea for variogram fitting is to plot the variogram in a new frame
and add some controls like sliders and/or text boxes to fill up with
nugget, sill and range values. This will involve Python graphics, not R,
as the former is more flexible.

Comments, suggestions, critics are welcome!

best regards and happy coding to everyone,

Anne

[0] http://grass.osgeo.org/wiki/V.autokrige_GSoC_2009
[1] http://casoilresource.lawr.ucdavis.edu/drupal/node/442
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoxNdwACgkQzZ3g4YwFFgZ2xgCgmIVL34wnuAD3MIPxLGoKmCE+
yMUAn1Nzf2jzSn9T2jGCaAeKgnD7SV3u
=UaBU
-----END PGP SIGNATURE-----

2

Anne,

Will this be scriptable? I guess it's not a huge deal since it would be using a script that included GRASS and R using automap…

Tom

Anne Ghisla wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

there are some important news about the module!

First of all, the interface is almost finished. See a screenshot on the
wiki page [0].
The layout includes a notebook with a page for each R package (automap,
gstat and geoR), with the available options. Another layout could be a
chiocebox wht the three packages on the top of Kriging section, that
redraws the section accourding to the user's choice.
Let me know which one do you prefer, feel free also to suggest something
new.

The R-GRASS integration is on its way: autofitting the variogram on a
map obtained from a DEM sample [1] works in the proof of concept. rpy2
is extremely helpful and does not require much more code than the
original R code. More to come in the next days.

The idea for variogram fitting is to plot the variogram in a new frame
and add some controls like sliders and/or text boxes to fill up with
nugget, sill and range values. This will involve Python graphics, not R,
as the former is more flexible.

Comments, suggestions, critics are welcome!

best regards and happy coding to everyone,

Anne

[0] http://grass.osgeo.org/wiki/V.autokrige_GSoC_2009
[1] http://casoilresource.lawr.ucdavis.edu/drupal/node/442
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoxNdwACgkQzZ3g4YwFFgZ2xgCgmIVL34wnuAD3MIPxLGoKmCE+
yMUAn1Nzf2jzSn9T2jGCaAeKgnD7SV3u
=UaBU
-----END PGP SIGNATURE-----

_______________________________________________
R-sig-Geo mailing list
R-sig-Geo@stat.math.ethz.ch
https://stat.ethz.ch/mailman/listinfo/r-sig-geo
  
--
Thomas E Adams
National Weather Service
Ohio River Forecast Center
1901 South State Route 134
Wilmington, OH 45177

EMAIL: thomas.adams@noaa.gov

VOICE: 937-383-0528
FAX: 937-383-0033

3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Adams ha scritto:

Anne,

Will this be scriptable? I guess it's not a huge deal since it would be
using a script that included GRASS and R using automap…

Sure it will! I'll have a look at how to add this functionality in the
next weeks.

regards,
Anne

Tom

Anne Ghisla wrote:
Hello all,

there are some important news about the module!

First of all, the interface is almost finished. See a screenshot on the
wiki page [0].
The layout includes a notebook with a page for each R package (automap,
gstat and geoR), with the available options. Another layout could be a
chiocebox wht the three packages on the top of Kriging section, that
redraws the section accourding to the user's choice.
Let me know which one do you prefer, feel free also to suggest something
new.

The R-GRASS integration is on its way: autofitting the variogram on a
map obtained from a DEM sample [1] works in the proof of concept. rpy2
is extremely helpful and does not require much more code than the
original R code. More to come in the next days.

The idea for variogram fitting is to plot the variogram in a new frame
and add some controls like sliders and/or text boxes to fill up with
nugget, sill and range values. This will involve Python graphics, not R,
as the former is more flexible.

Comments, suggestions, critics are welcome!

best regards and happy coding to everyone,

Anne

[0] http://grass.osgeo.org/wiki/V.autokrige_GSoC_2009
[1] http://casoilresource.lawr.ucdavis.edu/drupal/node/442

_______________________________________________
R-sig-Geo mailing list
R-sig-Geo@stat.math.ethz.ch
https://stat.ethz.ch/mailman/listinfo/r-sig-geo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoyEZUACgkQzZ3g4YwFFgbywwCfUqEQ4DFLG7PQGP1I4+aGV+Jq
pQYAniQ2OZ3fCx8huAY1uFyto7/L0KcR
=Q+wU
-----END PGP SIGNATURE-----

4

On Fri, Jun 12, 2009 at 11:28, Anne Ghisla<a.ghisla@gmail.com> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Adams ha scritto:

Anne,

Will this be scriptable? I guess it's not a huge deal since it would be
using a script that included GRASS and R using automap…

Sure it will! I'll have a look at how to add this functionality in the
next weeks.

I think there is a function in SWIG so that your module will have the
same commandline behaviour as other GRASS modules. Martin, you know
better than I do how to ennable it.

--Wolf

--

<:3 )---- Wolf Bergenheim ----( 8:>

5

Anna,

The wxPython interface looks good. I'd stick with the notebook over choicebook because you can easily see the options with a notebook without clicking anything.

We use a flatnotebook control for the GRASS GUI if you'd like to make this visually compatible (not obligatory, though aesthetically consistent). We use the V8 style tab and some nice colors too. You can look at the GUI code for ideas if you want.

If someone does not have one of the programs installed, does the error message suggest the needed URL to get it?

Michael

On Jun 11, 2009, at 9:50 AM, Anne Ghisla wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

there are some important news about the module!

First of all, the interface is almost finished. See a screenshot on the
wiki page [0].
The layout includes a notebook with a page for each R package (automap,
gstat and geoR), with the available options. Another layout could be a
chiocebox wht the three packages on the top of Kriging section, that
redraws the section accourding to the user's choice.
Let me know which one do you prefer, feel free also to suggest something
new.

The R-GRASS integration is on its way: autofitting the variogram on a
map obtained from a DEM sample [1] works in the proof of concept. rpy2
is extremely helpful and does not require much more code than the
original R code. More to come in the next days.

The idea for variogram fitting is to plot the variogram in a new frame
and add some controls like sliders and/or text boxes to fill up with
nugget, sill and range values. This will involve Python graphics, not R,
as the former is more flexible.

Comments, suggestions, critics are welcome!

best regards and happy coding to everyone,

Anne

[0] V.krige GSoC 2009 - GRASS-Wiki
[1] http://casoilresource.lawr.ucdavis.edu/drupal/node/442
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoxNdwACgkQzZ3g4YwFFgZ2xgCgmIVL34wnuAD3MIPxLGoKmCE+
yMUAn1Nzf2jzSn9T2jGCaAeKgnD7SV3u
=UaBU
-----END PGP SIGNATURE-----
_______________________________________________
SoC mailing list
SoC@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/soc

6

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Barton ha scritto:

Anna,

The wxPython interface looks good. I'd stick with the notebook over
choicebook because you can easily see the options with a notebook
without clicking anything.

We use a flatnotebook control for the GRASS GUI if you'd like to make
this visually compatible (not obligatory, though aesthetically
consistent). We use the V8 style tab and some nice colors too. You can
look at the GUI code for ideas if you want.

Yes, I saw that code in Layer Manager, going to integrate in kriring
module soon.

If someone does not have one of the programs installed, does the error
message suggest the needed URL to get it?

I don't know if the popup message is a good place to store all the info
about missing dependencies. I plan to make the error message point to
exhaustive documentation page(s) of the module, but I'm open to any
suggestion.

Michael

Anne

On Jun 11, 2009, at 9:50 AM, Anne Ghisla wrote:

Hello all,

there are some important news about the module!

First of all, the interface is almost finished. See a screenshot on the
wiki page [0].
The layout includes a notebook with a page for each R package (automap,
gstat and geoR), with the available options. Another layout could be a
chiocebox wht the three packages on the top of Kriging section, that
redraws the section accourding to the user's choice.
Let me know which one do you prefer, feel free also to suggest something
new.

The R-GRASS integration is on its way: autofitting the variogram on a
map obtained from a DEM sample [1] works in the proof of concept. rpy2
is extremely helpful and does not require much more code than the
original R code. More to come in the next days.

The idea for variogram fitting is to plot the variogram in a new frame
and add some controls like sliders and/or text boxes to fill up with
nugget, sill and range values. This will involve Python graphics, not R,
as the former is more flexible.

Comments, suggestions, critics are welcome!

best regards and happy coding to everyone,

Anne

[0] http://grass.osgeo.org/wiki/V.autokrige_GSoC_2009
[1] http://casoilresource.lawr.ucdavis.edu/drupal/node/442

_______________________________________________
SoC mailing list
SoC@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/soc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkozZzwACgkQzZ3g4YwFFgayggCgmlMTAFZTCJdRKVuJ6XIjXNJE
MpEAnixpl722NKkTJ3E1HC9AYQ8OHVYN
=mwhx
-----END PGP SIGNATURE-----