[GRASS-dev] r.series: extentions as plugins

Hi,

would it make sense to add support for extentions as plugins in
r.series? We plan to add some function fitting which might not be
of interest to all - on the other hand a plugin style for extensions
could simplify the addition of custom functionality.

I darkly remember that this was discussed some time ago but
cannot find the reference(s).

Markus

On Tuesday 19 May 2009, Markus Neteler wrote:

Hi,

would it make sense to add support for extentions as plugins in
r.series? We plan to add some function fitting which might not be
of interest to all - on the other hand a plugin style for extensions
could simplify the addition of custom functionality.

I darkly remember that this was discussed some time ago but
cannot find the reference(s).

Markus

Yes please. I think that any functionality that is added will be of some use
to someone. However, generic hooks built-in to r.series would be a very
convenient. Perhaps this fits into the discussion of time-series modeling
that came up on the list a while back?

any details?

Cheers,
Dylan

--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341

On May 19, 2009, at 6:08 PM, Markus Neteler wrote:

Hi,

would it make sense to add support for extentions as plugins in
r.series? We plan to add some function fitting which might not be
of interest to all - on the other hand a plugin style for extensions
could simplify the addition of custom functionality.

Markus,

it would be hugely appreciated if you could add any planned capabilities
to the core r.series rather than plugins -
  function fitting would be certainly of great interest.
We were able to get lots of very interesting, useful and unique results
when applying the module to time series of lidar data and we have been thinking
about adding more options too. We got around the variable time step issue
using inserted null rasters (this should probably be included on the man page)
but providing the time steps as an option may be a better approach in case
there are big differences - you may have this issue with function fitting as well
unless you have constant time step. Maybe we should keep in touch
about r.series to coordinate the development.

Helena

I darkly remember that this was discussed some time ago but
cannot find the reference(s).

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

On Thu, May 21, 2009 at 11:26 PM, Helena Mitasova
<hmitaso@unity.ncsu.edu> wrote:

On May 19, 2009, at 6:08 PM, Markus Neteler wrote:

would it make sense to add support for extentions as plugins in
r.series? We plan to add some function fitting which might not be
of interest to all - on the other hand a plugin style for extensions
could simplify the addition of custom functionality.

Markus,

it would be hugely appreciated if you could add any planned capabilities
to the core r.series rather than plugins -
function fitting would be certainly of great interest.

Helena,

the point wasn't to keep the plugin(s) for me but to facilitate the
development of extensions. That every group interested in an extensions
hack the core r.series code might destabilize everything.
Having it separated out as plugin separates core from user functionality.

We were able to get lots of very interesting, useful and unique results
when applying the module to time series of lidar data and we have been
thinking
about adding more options too. We got around the variable time step issue
using inserted null rasters (this should probably be included on the man
page)

(yes, please add or send me a text snippet)

but providing the time steps as an option may be a better approach in case
there are big differences - you may have this issue with function fitting as
well unless you have constant time step. Maybe we should keep in touch
about r.series to coordinate the development.

Perfect.

Markus