gvsig-geoprocess / org.gvsig.geoprocess / trunk / org.gvsig.geoprocess / org.gvsig.geoprocess.app / org.gvsig.geoprocess.app.mainplugin / src / main / resources / help / en / general / history.html @ 338
History | View | Annotate | Download (2.73 KB)
| 1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|---|---|
| 2 |
|
| 3 |
<!--Converted with LaTeX2HTML 2002-2-1 (1.71)
|
| 4 |
original version by: Nikos Drakos, CBLU, University of Leeds
|
| 5 |
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
|
| 6 |
* with significant contributions from:
|
| 7 |
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
|
| 8 |
<HTML>
|
| 9 |
<HEAD>
|
| 10 |
<TITLE>The SEXTANTE history manager</TITLE> |
| 11 |
<META NAME="description" CONTENT="The SEXTANTE history manager"> |
| 12 |
<META NAME="keywords" CONTENT="IntroductionToSEXTANTE"> |
| 13 |
<META NAME="resource-type" CONTENT="document"> |
| 14 |
<META NAME="distribution" CONTENT="global"> |
| 15 |
|
| 16 |
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> |
| 17 |
<META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1"> |
| 18 |
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| 19 |
|
| 20 |
<LINK REL="STYLESHEET" HREF="IntroductionToSEXTANTE.css"> |
| 21 |
|
| 22 |
</HEAD>
|
| 23 |
|
| 24 |
<BODY > |
| 25 |
<!--Table of Child-Links-->
|
| 26 |
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A> |
| 27 |
|
| 28 |
<UL CLASS="ChildLinks"> |
| 29 |
<LI><A NAME="tex2html220" |
| 30 |
HREF="node8.html#SECTION00810000000000000000">Introduction</A> |
| 31 |
</UL>
|
| 32 |
<!--End of Table of Child-Links-->
|
| 33 |
<HR>
|
| 34 |
|
| 35 |
<H1><A NAME="SECTION00800000000000000000"> |
| 36 |
The SEXTANTE history manager</A>
|
| 37 |
</H1>
|
| 38 |
|
| 39 |
<P>
|
| 40 |
|
| 41 |
<H1><A NAME="SECTION00810000000000000000"> |
| 42 |
Introduction</A>
|
| 43 |
</H1>
|
| 44 |
|
| 45 |
<P>
|
| 46 |
Every time you execute a SEXTANTE algorithm, information about the process is stored in the SEXTANTE history manager. Along with the parameters used, the date and time of the execution are also saved. |
| 47 |
|
| 48 |
<P>
|
| 49 |
This way, it is easy to track the and control all the work that has been developed using SEXTANTE, and easily reproduce it. |
| 50 |
|
| 51 |
<P>
|
| 52 |
The SEXTANTE history manager is a set of registries grouped according to their date of execution, making it easier to find information about an algorithm executed at any particular moment. |
| 53 |
|
| 54 |
<P>
|
| 55 |
<DIV ALIGN="CENTER"> |
| 56 |
<IMG
|
| 57 |
WIDTH="479" HEIGHT="380" ALIGN="BOTTOM" BORDER="0" |
| 58 |
SRC="./history.png" |
| 59 |
ALT="Image history"> |
| 60 |
|
| 61 |
</DIV>
|
| 62 |
|
| 63 |
<P>
|
| 64 |
Process information is kept as a command-line expression, even if the algorithm was launched from the toolbox. This makes it also useful for those learning how to use the command-lin interface, since they can call an algorithm using the toolbox and then check the history manager to see how that same algorithm could be called from the command line. |
| 65 |
|
| 66 |
<P>
|
| 67 |
Apart from browsing the entries in the registry, processes can be re-executed, simply double-clicking on the corresponding entry. |
| 68 |
|
| 69 |
<P>
|
| 70 |
You can also right click on a process (the command-line sentence must start with ``runalg'') and select <SPAN CLASS="textit">Open algorithm dialog</SPAN>. This will show the dialog used to execute the algorithm, already filled with the parameter values corresponding to the selected command. |
| 71 |
|
| 72 |
<P>
|
| 73 |
<BR><HR> |
| 74 |
<ADDRESS>
|
| 75 |
Victor Olaya |
| 76 |
2010-02-18 |
| 77 |
</ADDRESS>
|
| 78 |
</BODY>
|
| 79 |
</HTML>
|