progress bar_elapsed/expected duration

[battler.]

Hi all,

Has anybody ever tackled this problem and come up with a solution for a progress bar which displays elapsed and estimated time.

In order to do this the VI should realise:

- N iterations

- i iteration (current)

- what is the average time per iteration (as a running average)

Has anyone done this?

What about the .NET implementation of a progress bar.  Does anyone know how to use it?

Thanks.

[Guruthilak]

i guess there is one somewhere in this forum created by Daren.

Try his nugget posts.. may be this

Message Edited by Guruthilak on 02-01-2010 03:44 PM

[Giedrius.S]

Hi.

Could this be something helpful?

It does not calculate the average time per iteration. In this example I use time delay variable instead.

Code for LV 9.0.

[Giedrius.S]

Sorry for two posts in a row.

I have modified my VI a bit for it to match your needs better while including this point also:

---

@battler. wrote:

In order to do this the VI should realise:

- what is the average time per iteration (as a running average)

---

I am very novice to LV, so if this won't be what you really need, maybe it will leastwise give you some ideas putting you in the right direction.

Giedrius

[battler.]

Hi there.  Thanks for the effort.

I think it's a good start but needs refinement.

I have attached an image of the block diagram for others to look at:

Please post your suggestions.

[Guruthilak]

could be better if you fix those coercion dots.... 🙂

[battler.]

I think that's the least of our worries with this VI.

What about the sequence structures with separate timers..

[battler.]

Would the time source not have to be external to this VI?

[Giedrius.S]

---

Guruthilak wrote:
could be better if you fix those coercion dots.... 🙂

---

That is true. I should also move the part of the code for the elapsed time measurement and the stop button outside of the sequence structure to the body of the loop. While I am a novice, I still need to learn to code more correctly.

But in this case all of that should not be a problem for the author of the question. The point is if the provided algorithm to implement the task given by the author is ok or is it not 🙂

The algorithm in each iteration measures the time used to implement the task and calculates the average of time used per iteration. If you will change the time delay (or if some iteration will require more or less time) the average and therefore the "expected time of execution" will converge to the appropriate direction. In parallel, the "execution time left" is also adjusted to correspond to the differencs occured. We also have the progress bar and elapsed time indicated too.

Excludind the "ugliness" of the code, maybe there is some lapse left. I'll leave this for you guys to find out. 

[Giedrius.S]

I have made some minor changes.

The code works fine to me:

But maybe something more specific is required.