[GRASS-user] GRASS Session Record

GRASS GRASS user
1

   It would be very helpful to capture all GRASS commands and output in a
text file for each session. I believe this can be done by invoking grass
with the 'tee' command. Is there another, preferred way to do this?

Rich

2

Rich,

On Fri, Jun 8, 2012 at 6:33 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:

It would be very helpful to capture all GRASS commands and output in a
text file for each session. I believe this can be done by invoking grass
with the ‘tee’ command. Is there another, preferred way to do this?

There is a .bash_history file stored in the PERMANENT mapset, it stores all the command logs you used in the sessions

ciao madi

–
Dr. Margherita Di Leo

3

On Fri, 8 Jun 2012, Margherita Di Leo wrote:

There is a .bash_history file stored in the PERMANENT mapset, it stores
all the command logs you used in the sessions

madi,

   There's also one in the project's mapset, but it has only the commands,
not the output of those commands sent to stdout. I'll see how successful
pipiging output through the tee command works for this.

Thanks,

Rich

--
Richard B. Shepard, Ph.D. | Integrity - Credibility - Innovation
Applied Ecosystem Services, Inc. | Helping Ensure Our Clients' Futures
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863

4

Rich Shepard wrote:

   It would be very helpful to capture all GRASS commands and output in a
text file for each session. I believe this can be done by invoking grass
with the 'tee' command. Is there another, preferred way to do this?

Use a terminal emulator with a "log to file" capabaility. Or use the
"script" command.

The main problem with "tee" is that it won't work with commands which
require a terminal.

--
Glynn Clements <glynn@gclements.plus.com>

5

On Fri, 8 Jun 2012, Glynn Clements wrote:

Use a terminal emulator with a "log to file" capabaility. Or use the
"script" command.

Glynn,

   OK. I'll see if urxvt supports logging.

Thanks,

Rich

6

Hi,

2012/6/8 Rich Shepard <rshepard@appl-ecosys.com>:

It would be very helpful to capture all GRASS commands and output in a
text file for each session. I believe this can be done by invoking grass
with the 'tee' command. Is there another, preferred way to do this?

slightly related --- GUI-oriented way how to create commands protocol
in wxGUI has been asked by Helena Mitasova during GRASS community
sprint in Prague [1], currently available for testing in G65 & G70.
See short video tutorial at [2].

Martin

[1] http://grass.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2012
[2] http://grass.osgeo.org/wiki/WxPython-based_GUI_for_GRASS#Layer_Manager:_Commands_protocol

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

7

2012/6/8 Martin Landa <landa.martin@gmail.com>:

slightly related --- GUI-oriented way how to create commands protocol
in wxGUI has been asked by Helena Mitasova during GRASS community
sprint in Prague [1], currently available for testing in G65 & G70.
See short video tutorial at [2].

now (r52016) also in relbr64.

Martin

--
Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

8

Glynn wrote:

Use a terminal emulator with a "log to file" capabaility. Or use the
"script" command.

fyi, hints for using the `script` command can be found here:

http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#record-session

Hamish

9

On Fri, Jun 8, 2012 at 8:31 PM, Martin Landa <landa.martin@gmail.com> wrote:

slightly related --- GUI-oriented way how to create commands protocol
in wxGUI has been asked by Helena Mitasova during GRASS community
sprint in Prague [1],

One wish: ignore the # character for comments, when copy-pasting
from enriched protocols:

# display elevation model:
[Errno 2] No such file or directory
d.rast elevation

thanks
Markus