Beta
Clicker Game Solver [EASY ver.]
Loading description...
Game Solvers
Games
Mathematics
NumPy
Performance
Puzzles
Simulation
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Nice problem, thanks!
Minor suggestions:
It would be would be helpful to have an example, either in the description or the sample tests, where upgrading as soon as possible is not part of the solution.
Display the parameter values for each random test. It helps with debugging, and saves the user having to print them out.
Include what "cpc" stands for.
Explain what n refers to in "The reference solution executes with O(log n) taking less than 1s."
It's not clear why "numpy" is included in the tags. Maybe either explain why or remove it.
I suspect you might have precision issues in your reference solution. For example with inputs:
up=2, goal=2020450000000000000000, I calculate that we should be upgrading126063times, which should result in total clicks of10684790872762699, but your tests expect 1 less at10684790872762698.As the inputs get larger, the discrepency grows too.
You're right: employing
decimal.Decimalinstead offloatfixed the precision issue and confirmed your output (at least for the test case you presented).Reference solution has been updated and tests have been slightly adjusted to take into account the small execution time increment caused by the improved precision.
Thank you very much for pointing that out! Please confirm that the problem is now fixed so i can mark the issue as solved.
I cannot see your comment since I cannot solve the kata. You could come to the Discord (see link on the left menu) and we can discuss there. Otherwise if you want a reference you can click "view solution" under my comment to see what I think should be a correct solution.
Excuse me, I overlooked it. I unflagged my response since it doesn't really represent a relevant spoiler to the solution, at least in my opinion.
I don't think it is resolved, I am now getting many results like this:
You probably need to set
Decimal.getcontext().precto be much higher.Right, I did that and republished just now. Now outputs are no longer "truncated". I'll come back in a short while to make sure outputs are still correct and mark as solved if that's the case.
I noticed our solutions produce different outputs, so I'll check wether that's a mistake in mine or yours and send an update when done.
Thanks again.
Seems fixed
Great. Ty again for the help!
Hi,
If you actually have a O(1) solution, there is no need to make the user wait the result for 9s. Just use big enough inputs, a 2s computation time should be WAY more than enough to prune out any undesired implementation. But make sure the inputs are big enough (better to have less tests with bigger inputs than the opposite)
Done: cut down tests to a third of the former amount, resulting in an execution time of 3.5s (see updated "Performance" paragraph in the description).
The tests' upper bound for the goal parameter has also been reduced, since it didn't really provide harder test cases - only bloated the tests amount.
Thank you for your input!