Add a meaningful progress bar for calculations

[inasafe]

Add a meaningful progress bar for calculations

[uniomni]

I agree. In the previous incarnation we had four distinct steps that could be reported:
1: Download Hazard
2: Download Exposure
3: Compute Impact
4: Upload Result

In the QGis incarnation, we could do something like

1: Prepare Hazard layer (load, possibly reproject, clip, resample)
2: Prepare Exposure layer (load, possibly reproject, clip, resample)
3: Compute Impact
(4: Upload - if we are actually pushing to another server which is not the case in version 0.10)

[uniomni]

This is still valid and would help understand issue #96

[timlinux]

I've implemented message status updates through the process. It isnt implemented as a progress bar, just as updated messages in the status bar. If you specifically want a status bar please reopen this ticket and I will 'make it so'.

Regards

Tim

[uniomni]

I love the way you have done it - with the status bar. Couple of comments:
1: It looks like the progress bar is dead, so perhaps remove it?
2: What are the steps? Isn't there one after calculating impact?
3: After the calculation is done, the status bar says 'ready' (or 'siap') again and there is some waiting before the impact summary report is shown. This is also reported in issue #96. It would be good to get the report ASAP even if the layer takes a while to load. I understand this may not be possible without threading, but worth checking.

[timlinux]

Hi

On Tue, Mar 27, 2012 at 9:50 AM, Ole Nielsen
[email protected]
wrote:

I love the way you have done it - with the status bar. Couple of comments:
1: It looks like the progress bar is dead, so perhaps remove it?
2: What or the steps? Isn't there one between calculating impact and ready?
3: After the status bar says 'ready' (or 'siap') there is still some waiting before the impact summary report is shown. This is also reported in issue #96

1. Ok stand by - I wasnt happy with my first implementation and am
   tweaking it...
2. Its going to be replaced in my above tweaks. On the ticket you
   asked for the following steps: Preparing hazard (runs so fast on my
   system you may not see it), preparing exposure, calculating impact,
   uploading (not relevant yet). Feel free to adjust that list - the
   implementation allows for that to be done easily.
3. Ok I iwll look at that.

Regards

Tim

---

Reply to this email directly or view it on GitHub:
#33 (comment)

Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)

Visit http://linfiniti.com to find out about:
 * QGIS programming services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services

Skype: timlinux Irc: timlinux on #qgis at freenode.net

[uniomni]

OK cool.
A good example to test this on is Shakemap Padang 2009 with the OSM data.
There are about 65000 buildings involved, so there is time to see the
progress.

Cheers
Ole

On Tue, Mar 27, 2012 at 2:54 PM, Tim Sutton <
[email protected]

wrote:

Hi

On Tue, Mar 27, 2012 at 9:50 AM, Ole Nielsen
[email protected]
wrote:

I love the way you have done it - with the status bar. Couple of
comments:
1: It looks like the progress bar is dead, so perhaps remove it?
2: What or the steps? Isn't there one between calculating impact and
ready?
3: After the status bar says 'ready' (or 'siap') there is still some
waiting before the impact summary report is shown. This is also reported in
issue #96

1. Ok stand by - I wasnt happy with my first implementation and am
   tweaking it...
2. Its going to be replaced in my above tweaks. On the ticket you
   asked for the following steps: Preparing hazard (runs so fast on my
   system you may not see it), preparing exposure, calculating impact,
   uploading (not relevant yet). Feel free to adjust that list - the
   implementation allows for that to be done easily.
3. Ok I iwll look at that.

Regards

Tim

---

Reply to this email directly or view it on GitHub:
#33 (comment)

Tim Sutton - QGIS Project Steering Committee Member (Release Manager)

Visit http://linfiniti.com to find out about:

• QGIS programming services
• Mapserver and PostGIS based hosting plans

• FOSS Consulting Services
  Skype: timlinux Irc: timlinux on #qgis at freenode.net

---

Reply to this email directly or view it on GitHub:
#33 (comment)

[timlinux]

Ok try what is in master now! Works quite nicely I think and provides the user with a little more info as to what is happening. I'll address #96 on its own ticket.

[uniomni]

I can't see any commit since I left work. Are you sure you pushed?
O

On Tue, Mar 27, 2012 at 4:32 PM, Tim Sutton <
[email protected]

wrote:

Ok try what is in master now! Works quite nicely I think and provides the
user with a little more info as to what is happening. I'll address #96 on
its own ticket.

---

Reply to this email directly or view it on GitHub:
#33 (comment)

[uniomni]

I can't see any commit since I left work. Are you sure you pushed?

[timlinux]

Sorry it is pushed now...

Regards

Tim

On Tue, Mar 27, 2012 at 2:20 PM, Ole Nielsen
[email protected]
wrote:

I can't see any commit since I left work. Are you sure you pushed?

---

Reply to this email directly or view it on GitHub:
#33 (comment)

Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)

Visit http://linfiniti.com to find out about:
 * QGIS programming services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services

Skype: timlinux Irc: timlinux on #qgis at freenode.net

[vanpuk]

In the progress panel it goes back to 'ready' at the end of the process. When dealing with OSM data in Padang (65,000) building it actually holds there for a long time. Which for someone that does not know the software will think that it has finished processing.
Cheers

[timlinux]

The progress bar was replaced with the new messaging system in 1.2. The messaging system needs further improvement independently of this ticket but for now I will close this ticket as it is no longer relevant to the GUI as currently implemented.

[timlinux]

Still needs to be updated so that:

• new messages appear at the top
• message groups are collapsable.

I will close this issue as the functionality should be covered in #577

See also #577