Flowgorithm Help

[dual290x]

Is there any one with Flowgorithm experience that could take a look at my chart to see what I am doing wrong? I have an assignment due tomorrow and I can not figure out how to get around an issue. Thanks to anyone who replies.

[Techicolors]

sure, post the chart 

[straight_stewie]

8 minutes ago, dual290x said:

Is there any one with Flowgorithm experience that could take a look at my chart to see what I am doing wrong? I have an assignment due tomorrow and I can not figure out how to get around an issue. Thanks to anyone who replies.

Lots of us know how to read flowcharts.  Go ahead and post an image(s) of it for us.

[dual290x]

 

3 minutes ago, Technicolors said:

sure, post the chart 

 

https://drive.google.com/open?id=1vBlqZ5L9OHtt1ykAzPDn1P23ZY72ElJT

Thanks.

 

5 minutes ago, CUDA_Cores said:

♎︎□︎♏︎⬧︎ ⧫︎♒︎♓︎⬧︎ ♒︎♏︎●︎◻︎✍︎

Ummm.... maybe?

[straight_stewie]

1 minute ago, dual290x said:

Thanks.

The link is permission locked.

[dual290x]

3 minutes ago, straight_stewie said:

The link is permission locked.

Sorry guys. Try this one. https://drive.google.com/drive/folders/1vBlqZ5L9OHtt1ykAzPDn1P23ZY72ElJT?usp=sharing

I also added a doc with the prompt for what the assignment is.

[straight_stewie]

4 minutes ago, dual290x said:

orry guys. Try this one. https://drive.google.com/drive/folders/1vBlqZ5L9OHtt1ykAzPDn1P23ZY72ElJT?usp=sharing

still permission locked. 

[dual290x]

 

12 minutes ago, straight_stewie said:

still permission locked. 

Sorry, I changed the permissions. Not use to dealing with google drive. Thanks for your patience.

[straight_stewie]

1 hour ago, dual290x said:

Sorry, I changed the permissions. Not use to dealing with google drive. Thanks for your patience.

Ok. I have it up and running. What exactly is the issue that you're having? (I have a pretty good guess, but this is homework and you're gonna have to do more work).

[dual290x]

17 minutes ago, straight_stewie said:

Ok. I have it up and running. What exactly is the issue that you're having? (I have a pretty good guess, but this is homework and you're gonna have to do more work).

Okay. So, (generally speaking) I do not have an issue with the largest number (max). However, I always have an issue with the smallest number (min). If I input (for example) 92, then 15,  I receive 92 as max and 15 as min. However, if I reverse the two numbers (15 then 92) I get 92 as max and 0 as min. If I input three numbers in order of 20, 15, and 25. I will receive 25 as the highest, and 15 as the lowest. Or 20, 26, 30. then 30 is max and 0 is min.

 

Sorry for the link issues.

[straight_stewie]

1 minute ago, dual290x said:

Okay. So, (generally speaking) I do not have an issue with the largest number (max). However, I always have an issue with the smallest number (min). If I input (for example) 92, then 15,  I receive 92 as max and 15 as min. However, if I reverse the two numbers (15 then 92) I get 92 as max and 0 as min. If I input three numbers in order of 20, 15, and 25. I will receive 25 as the highest, and 15 as the lowest. Or 20, 26, 30. then 30 is max and 0 is min.

Ok. So let's think more academically about what it is you are actually doing, and then we will get to what it is you should be doing. Let's write out, in plain english, what your algorithm currently is.
 

1. Declare three integers; number, max, and min.
2. Declare three booleans: start, finish, and end.
3. Set max and min to 0.
4. Set start to false
5. If not start
   1. Ask the user for a number
   2. Store the result in number
   3. If the number is greater than 0
      1. If the number is greater than max
         1. Set max to number
      2. Else
         1. Set min to number
   4. Else
      1. Set Start to true
   5. GoTo step five
6. Else
   1. Output min, max
   2. Exit

Now, we have something to step through, so step through it with your cases and see where it fails.
Alternatively, you can turn the speed of execution down in Flowgarithm, and watch as it executes each step to see where it fails. This is the process of debugging. 

So here's my question for you: Where is your algorithm going wrong?

[dual290x]

4 minutes ago, straight_stewie said:

Ok. So let's think more academically about what it is you are actually doing, and then we will get to what it is you should be doing. Let's write out, in plain english, what your algorithm currently is.
 

1. Declare three integers; number, max, and min.
2. Declare three booleans: start, finish, and end.
3. Set max and min to 0.
4. Set start to false
5. If not start
   1. Ask the user for a number
   2. Store the result in number
   3. If the number is greater than 0
      1. If the number is greater than max
         1. Set max to number
      2. Else
         1. Set min to number
   4. Else
      1. Set Start to true
   5. GoTo step five
6. Else
   1. Output min, max
   2. Exit

Now, we have something to step through, so step through it with your cases and see where it fails.
Alternatively, you can turn the speed of execution down in Flowgarithm, and watch as it executes each step to see where it fails. This is the process of debugging. 

So here's my question for you: Where is your algorithm going wrong?

For one, any number is greater than 0. So any number larger than the first (say first number is 16  then second is 20) will become the max. Which takes 16 and dumps it. Therefor I am still stuck with my min = 0.

[straight_stewie]

Just now, dual290x said:

For one, any number is greater than 0. So any number larger than the first (say first number is 16  then second is 20) will become the max. Which takes 16 and dumps it. Therefor I am still stuck with my min = 0.

Well, what part of your algorithm is wrong that leaves your min stuck at zero?

[dual290x]

2 minutes ago, straight_stewie said:

Well, what part of your algorithm is wrong that leaves your min stuck at zero?

number > max | makes it so any number larger than the last will be true (hence it would never go to min).

[straight_stewie]

1 minute ago, dual290x said:

number > max | makes it so any number larger than the last will be true (hence it would never go to min).

Exactly, so what should happen instead?

[dual290x]

I am way over thinking this. >.<

[straight_stewie]

You're trying to stick two comparisons that must always execute independently of each other into one decision.

[dual290x]

19 minutes ago, straight_stewie said:

You're trying to stick two comparisons that must always execute independently of each other into one decision.

I am over thinking it. However, I did come up with this.

 

replaced | number > max | with min == max -- (first time is true making [x] number max. Then second round it would be false making it go | false | -- number > max -- true -- max = number (or false -- min = number).

[straight_stewie]

3 minutes ago, dual290x said:

I am over thinking it. However, I did come up with this.

Still overthinking it. Think about it this way: Does a number being the minimum number entered mean that that number relates to the maximum number entered? If so why, if not why not?

In more concrete terms, just because a number is the new maximum number, does that mean it is not the new minimum number? Just because a number is the new minimum, does that mean that it is not the new maximum? Can you find one case where a number is both min and max?

[dual290x]

1 minute ago, straight_stewie said:

Still overthinking it. Think about it this way: Does a number being the minimum number entered mean that that number relates to the maximum number entered? If so why, if not why not?

In more concrete terms, just because a number is the new maximum number, does that mean it is not the new minimum number? Just because a number is the new minimum, does that mean that it is not the new maximum? Can you find one case where a number is both min and max?

0 or the same number over and over again.

[straight_stewie]

Just now, dual290x said:

0 or the same number over and over again.

So if there is a case where a number is both min and max, then don't you need to check that case against both min and max?

[dual290x]

2 minutes ago, straight_stewie said:

So if there is a case where a number is both min and max, then don't you need to check that case against both min and max?

I think I understand what you are saying, but I am not understanding what checking the min and max (for same number  [== to]) has to do with it. Are you saying it should show (say inputs were 2, 2, 2, 2, 2) max is 2 and min is 0?

[straight_stewie]

1 minute ago, dual290x said:

I think I understand what you are saying, but I am not understanding what checking the min and max (for same number  [== to]) has to do with it. Are you saying it should show (say inputs were 2, 2, 2, 2, 2) max is 2 and min is 0?

I'm saying that you're problem is that you don't always check if number is less than min or greater than max.

It is not:

1. If number greater than max
   1. max = number
2. Else
   1. Min = number

Rather, it is:

1. If number greater than max
   1. max = number
2. If number less than min
   1. min = number

[dual290x]

so something to the effect of || (false) | number >max or number < min | (true) ||?

[straight_stewie]

35 minutes ago, dual290x said:

so something to the effect of || (false) | number >max or number < min | (true) ||?

 

46 minutes ago, straight_stewie said:

• If number greater than max
  1. max = number
• If number less than min
  1. min = number

But I repeat myself.