[GRASS-dev] redirect graphic output of r.spread

GRASS GIS GRASS GIS developer
1

Hi!

Any idea on how to (and IF it’s possible to) redirect the graphic output of r.spread module to a gif or mov or avi file instead of to (or beside to) the monitor?

Many thanks in advance

–

Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.

2

Margherita wrote:

Any idea on how to (and IF it's possible to) redirect the graphic
output of r.spread module to a gif or mov or avi file instead of
to (or beside to) the monitor?

not directly, but you might see the "screencast" section in:
http://grasswiki.osgeo.org/wiki/Movies

Hamish

ps- I just added a completely synthetic example to the wiki page, not as good as the sample download but you can run it directly from the NC sample dataset.
http://grasswiki.osgeo.org/wiki/How_to_create_parameters_to_run_r.ros#Example

3

Hi,

···

On Wed, Sep 18, 2013 at 1:07 AM, Hamish <hamish_b@yahoo.com> wrote:

Margherita wrote:

Any idea on how to (and IF it’s possible to) redirect the graphic
output of r.spread module to a gif or mov or avi file instead of
to (or beside to) the monitor?

not directly, but you might see the “screencast” section in:
http://grasswiki.osgeo.org/wiki/Movies

Thanks for the link. But I don’t understand how to put this in practice. I mean, as far as I understand, you’re suggesting to run r.spread in a loop, each step producing a final map as image and then compose together as a video, right? I had also thought something of the kind, but I was looking for a way to save the detailed fire evolution as it is generated by r.spread, hence a way to redirect the output directly to a video, or at least save several static images while r.spread is running, and then to compose them as a movie. Is that feasible?

Thanks

–

Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo@jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.

4

Margherita wrote:

Any idea on how to (and IF it's possible to) redirect the graphic
output of r.spread module to a gif or mov or avi file instead of
to (or beside to) the monitor?

Hamish:

not directly, but you might see the "screencast" section in:
http://grasswiki.osgeo.org/wiki/Movies

Thanks for the link. But I don't understand how to put this in practice.
I mean, as far as I understand, you're suggesting to run r.spread in a loop,
each step producing a final map as image and then compose together as a video,
right?

nope, the "screencast" is to record the changes on the screen as
they happen, like putting a movie camera pointed at the screen. (including the
cursor if it happens to be in-shot)

As-written I don't think there's a way to have r.spread write out static images
per-iteration to encode later into a video from individual frames.

regards,

Hamish

5

On Wed, Sep 18, 2013 at 3:29 PM, Hamish <hamish_b@yahoo.com> wrote:

Margherita wrote:
>>> Any idea on how to (and IF it's possible to) redirect the graphic
>>> output of r.spread module to a gif or mov or avi file instead of
>>> to (or beside to) the monitor?

Hamish:
>> not directly, but you might see the "screencast" section in:
>> http://grasswiki.osgeo.org/wiki/Movies
>
> Thanks for the link. But I don't understand how to put this in practice.
> I mean, as far as I understand, you're suggesting to run r.spread in a
loop,
> each step producing a final map as image and then compose together as a
video,
> right?

nope, the "screencast" is to record the changes on the screen as
they happen, like putting a movie camera pointed at the screen. (including
the
cursor if it happens to be in-shot)

As-written I don't think there's a way to have r.spread write out static
images
per-iteration to encode later into a video from individual frames.

So, if I understand correctly this is a bug in r.spread. For GRASS 6 it

may seem as feature request but for GRASS 7 it is a bug. Expected output is
a series of maps which you can put into a temporal dataset, export as
images or analyze individually. Visualization is another issue but for
GRASS 7, -d switch will newer be enabled.

I'm not familiar with r.spread much, only from manual, so correct me if I'm
wrong.

Maybe it is not so complicated to rewrite it, is somebody familiar with the
code to say something about it?

Vaclav

regards,

Hamish

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