Outdated version of the documentation. Find the latest one here.

.

Gestão do histórico

O histórico do processamento

Cada vez que executa um algoritmo, a informação do processo é armazenado no gestor histórico. Juntamente com os parâmetros usados, a data e o tempo de execução são também guardados.

This way, it is easy to track and control all the work that has been developed using the processing framework, and easily reproduce it.

The history manager is a set of registry entries grouped according to their date of execution, making it easier to find information about an algorithm executed at any particular moment.

Figure Processing 30:

../../../_images/history2.png

Histórico win

A informação do processo é mantida como uma expressão de linha de comandos, mesmo se o algoritmo seja lançado a partir da barra de ferramentas. Isto permite ser útil para aqueles que querem aprender como se usa a interface da linha de comandos, uma vez que podem chamar o algortimo usando a barra de ferramentas e verificar o gestor histórico para ver como o mesmo algoritmo pode ser chamado a partir da linha de comandos.

Apart from browsing the entries in the registry, you can also re-execute processes by simply double-clicking on the corresponding entry.

Along with recording algorithm executions, the processing framework communicates with the user by means of the other groups of the registry, namely Errors, Warnings and Information. In case something is not working properly, having a look at the Errors might help you to see what is happening. If you get in contact with a developer to report a bug or error, the information in that group will be very useful for her or him to find out what is going wrong.

Third-party algorithms are usually executed by calling their command-line interfaces, which communicate with the user via the console. Although that console is not shown, a full dump of it is stored in the Information group each time you run one of those algorithms. If, for instance, you are having problems executing a SAGA algorithm, look for an entry named ‘SAGA execution console output’ to check all the messages generated by SAGA and try to find out where the problem is.

Some algorithms, even if they can produce a result with the given input data, might add comments or additional information to the Warning block if they detect potential problems with the data, in order to warn you. Make sure you check those messages if you are having unexpected results.