juantheron
Active Member
- Joined
- Feb 9, 2012
- Messages
- 259
- Gender
- Male
- HSC
- N/A
The problem with this exact type of problem is that you have to consider every single divisor of whatever number you are solving for, thereby making it a brute force problem.For anyone who might want to try this using 2016's factors, here are its factors:
1, 2, 3, 4, 6, 7, 8, 9, 12, 14, 16, 18, 21, 24, 28, 32, 36, 42, 48, 56, 63, 72, 84, 96, 112, 126, 144, 168, 224, 252, 288, 336, 504, 672, 1008, 2016 .
And 2016 has too many factors to do by hand without it getting very tedious.The problem with this exact type of problem is that you have to consider every single divisor of whatever number you are solving for, thereby making it a brute force problem.
And 2016 has too many factors to do by hand without it getting very tedious. (There could be a more elegant way though.)The problem with this exact type of problem is that you have to consider every single divisor of whatever number you are solving for, thereby making it a brute force problem.
If there is, it is beyond all of stack exchange...And 2016 has too many factors to do by hand without it getting very tedious. (There could be a more elegant way though.)
-for x>64, all solutions must have y=1 or x.
Yep x-1. Will edit, thanks.