-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lab 6: 6a, 6b, 7 #22
Comments
Hello Bert, Thanks for the feedback. For exercise 6, you're right. We stated at the bottom in comments section, the tester can increase n up to what number s/he like and re-execute main function, if s/he is willing to wait for the results. We thought there will be no point of repeating the reporting in the comments section for n = 2, 3, ... up to 100. The algorithm was not fooled with multiple n values. Hopefully that answers your question on why not executing on a bigger n. for ex.8 (you wrote 7 probably what you meant is 8), yes that is totally correct. We were testing on many messages and then we fixed one in the main. Apparently at the end we forgot to update the reporting in the comments section, before we commit to github. If msg is set to 15122 in main, the report will be the one shown in the comments section. |
After this update: |
Thanks for following up on this.. |
6a
Why not
like in main65. Incomplete report.
6a(=4)
6b
The same remark as in 6a.
6b(=4)
I expect
7(=4)
The text was updated successfully, but these errors were encountered: