topic Re: guess number in LabVIEW

guess number

anny321dum — Fri, 06 Oct 2017 16:09:05 GMT

I have developed a vi where user will guess the number and if the guess is correct it will report as win and if wrong the user will try again using state machine architecture. But the problem is for any number I guess, it report success. I am trying hard to understand why that is happening. Also I want user to give only 5 chances how can I do that. Can anyone please help me.

Thank you in advance for your help

Re: guess number

arteitle — Fri, 06 Oct 2017 16:39:09 GMT

Try using "highlight execution" to see what's happening to the random and guess numbers in the "enter guess" and "give a hint" cases.

Re: guess number

jamiva — Fri, 06 Oct 2017 16:41:23 GMT

Another hint. Look what the tunnel output is if unwired.

Re: guess number

altenbach — Fri, 06 Oct 2017 16:47:44 GMT

In "check guess", you are resetting both oranges wires to zero, meaning they will be equal (and equal zero) from then on.

(You also need to do something about your greedy loops. A simple program like that does not need to use 100% of a CPU core, spinning the loops as fast as the computer allows.)

Re: guess number

anny321dum — Fri, 06 Oct 2017 17:31:05 GMT

Thank you very much for your reply. I still can't figure out what to put there at orange wires.

Re: guess number

altenbach — Fri, 06 Oct 2017 17:32:32 GMT

@anny321dum wrote:

Thank you very much for your reply. I still can't figure out what to put there at orange wires

Whatever the current value was coming from the right side. Just wire across!

(did you understand my note about timing?)

Re: guess number

anny321dum — Fri, 06 Oct 2017 17:38:19 GMT

Thank you again. No I did not. Sorry!

Re: guess number

arteitle — Fri, 06 Oct 2017 18:14:35 GMT

A while loop will execute over and over as fast as your computer's processor is able, consuming much computing power and slowing everything else down. In cases like this where the loop is just waiting for input, it's a good idea to add a brief pause in the loop (say, 100 ms) to relieve the CPU of that needless work.

Re: guess number

altenbach — Fri, 06 Oct 2017 21:45:19 GMT

Yes, your inner and outer loops are spinning as fast as the computer allows Millions of times per second. If you would place a 50ms wait in the loop, it would spin millions of times less without a perceptible difference seen by the user. Your PC will run cooler, you battery will last longer, and all your other running process don't have to fight for breadcrumbs of CPU time.

Also have a look at your architecture. You don't need the loop inside "enter uess" (sic) at all, you can use the state enum to either go back to the "enter uess" or forward to "Check guess", depending on the boolean state. No inner loop needed at all.

Also note that the text "enter number between ..." needs to appear when the program starts. Right now it won't unless the confirm button is pressed, at which time it gets overwritten a nanosecond later.

You also need to ensure that other messages don't get overwritten by new messages before the user has a chance to read them.

Your sequencing seems wrong too. for example the in the "give a hint" case, you need to go back to "enter uess", not to "check guess". Right?

Your numbers needs to be an integer once rounded, else it is very unlikely to ever guess right, because there are a near infinite number of DBLs between 1 and 10.

Re: guess number

altenbach — Fri, 06 Oct 2017 21:48:02 GMT

Here's a quick draft to give you some ideas. If you want to limit the number of guesses, this can be done by keeping count in another shift register and switch states accordingly.

(There are probably bugs, so check for correct operation)

Re: guess number

anny321dum — Sun, 08 Oct 2017 14:28:51 GMT

Thank you, I understand what was causing trouble.

I am trying to give 4 attempts, but it is taking more than 5 attempts.

Re: guess number

altenbach — Sun, 08 Oct 2017 16:21:03 GMT

Well, an image cannot tell us what's wrong. We cannot run it, we cannot see what's in the other cases, etc.

Your comparison is >5, so that IS "more than 5 attempts". Right?
Where does the count increment? Where does it initialize? Did you probe the value during run?
A 1000ms wait seems excessive. Why did you pick it?
Does the rest of the functionality work as expected?
Code is easier to debug if you keep the wiring clean. No need for all these wire bends and overlaps.
Why don't you display the number of guesses in the text indicator?