What do I have completed this week?

• Solved the issue with the outputs.
• Did some tests with QGIS algorithms which seems to be working fine.
• Refactored all QGIS algorithms in order to remove the progress bar parameter and use the signal instead.
• I have changed the Buffer used by QGIS algorithms: the Buffer is now a subclass of QObject. This new implementation allows the buffer to have a parent (the algorithm) and get access to the algorithm’s signal.
• SagaUtils refactored in the same way I did with the Buffer.
• SAGA algorithms refactored in order to use the signals instead of the progress parameter (Not finished yet)

What am I going to achieve for the next week?

• Solve the issue with SAGA algorithms.
• Code refactoring in order to improve the previous implementation on the AlgorithmDialog.
• Refactor Grass/Grass7.
• Bug fixes.

Is there any blocking issue?

There is an issue with SAGA algorithms that makes the Toolbar crash.

What do I have completed this week?

• Solved the issue with the outputs.
• Did some tests with QGIS algorithms which seems to be working fine.
• Refactored all QGIS algorithms in order to remove the progress bar parameter and use the signal instead.
• I have changed the Buffer used by QGIS algorithms: the Buffer is now a subclass of QObject. This new implementation allows the buffer to have a parent (the algorithm) and get access to the algorithm’s signal.
• SagaUtils refactored in the same way I did with the Buffer.
• SAGA algorithms refactored in order to use the signals instead of the progress parameter (Not finished yet)

What am I going to achieve for the next week?

• Solve the issue with SAGA algorithms.
• Code refactoring in order to improve the previous implementation on the AlgorithmDialog.
• Refactor Grass/Grass7.
• Bug fixes.

Is there any blocking issue?

There is an issue with SAGA algorithms that makes the Toolbar crash.

What do I have completed this week?

• A new implementation was designed to take into account several algorithms running. (using bounded signals)

• Deep analysis of the processing in order to fit this new design into the current implementation of the Processing toolbox

• Thread/Signal debugging

• Fix the problem that makes QGIS crash when starting the new thread

What am I going to achieve for the next week?

Continue working on the new design of the multithreading support.

Is there any blocking issue?

There is no blocking issue for now.

What do I have completed this week?

• New implementation of the AlgorithmExecutor subclassing QObject.
• Mechanism to deal with crashing Algorithms: when there is an exception during the algorithm execution, a signal is emitted in order to allow the main thread to make the other thread quit.
• Use signal to connect the algorithm progress signal to the setPercentage slot in the ProgressBar

In the runAlgorithm method of the Processing class I changed the code associated with the runalg in order to support multithreading. Each time that an algorithm is running through the QGIS python console, a new thread and a new instance of the algorithm executor are created. The signals of the AlgorithmExecutor are connected to the thread signal in order to quit the thread and run the algorithm when the thread starts. While the algorithm is running, the main thread waits for the algorithm to finish and then proceed to show the output (first approach)

What am I going to achieve for the next week?

Create a non-blocking version of the processing in order to the interface not wait for the algorithm to finish.

Is there any blocking issue?

QGIS seems to crash randomly when starting the new thread and, when it doesn’t crash, the output of the algorithm is None, which may indicate that the algorithm is crashing in the new thread.

The complete report about the crashing can be found here.