What do I have completed this week?

• The progress signal is successfully connected to both progress bar (when running from the console) and AlgorithmDialog (When using the processing toolbox).
• Fixed the bug that makes the algorithm return “None”.
• Fixed the bug that makes QGIS crash (sometimes) after the first time we run the algorithm.
• The multithreading on the AlgorithmDialog seems to work fine.
• More general implementation that allows to test the multithreading with any algorithm.

What am I going to achieve for the next week?

• Solve the issue with the outputs.
• Figure out why the processAlgorithm is not being called.
• Test the algorithms on python console and AlgorithmDialog.
• Bug fixes.

Is there any blocking issue?

• Problem loading the outputs from the algorithm.
• Have some university deadlines that may affect my work time on the project.

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.

What do I have completed this week?

• Using signals from the GeoAlgorithm to print the progress on QGIS python console
• Code refactoring
• Debugging
• Multithread when running the algorithm through the AlgorithmDialog

What am I going to achieve for the next week?

• Finish the multithread on the AlgorithmDialog
• Connect the progress signal to the progress bar
• Fix a bug that makes QGIS crash (sometimes) after the first time we run the algorithm
• Fix a bug that makes the algorithm return “None”

Is there any blocking issue?

Last week I had less time to work on the project due to my university exams and projects. I still have some university projects to finish till the end of the semester that may affect GSoC in the next week.

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.