Does r=uint64(308436464205151562) make sense? It seems like the argument to uint64 is a double precision number, so you have already lost the precision you are trying to gain by using uint64.
r=uint64(308436464205151562) outputs for uint64(r) 308436464205151562. However, r=308436464205151562 outputs for uint64(r) 308436464205151552. A very small loss in precision, but still a loss. The Challenge set has some numbers that use all the paint if full precision math was used. If residual paint was required as an output then full precision is needed. For solutions using p=p-2*r-1 the errors in r and p may cause issues.
Very novel input parameter adjustment to allow direct solution.
That's Muller's method which is more computationally realiable than Bhaskaracharya's.
Nice bisecting search method and anonymous function for clean appearance.
Check if sorted
First non-zero element in each column
Visualization of experimental data across a surface
Infinite precision division
Create an index-powered vector
Kaggle: Planetoid Game of Life - Total Score 0.10
USC Fall 2012 ACM: Rover Maze
Geometry: Find Circle given 3 Non-Colinear Points
New Cody Time-Out Time
PACMAT 06 - Optimized Ghosts, Equal Speed, Inf Lives; Interactive Download
Find the treasures in MATLAB Central and discover how the community can help you!
Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: .
You can also select a web site from the following list:
Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.
Contact your local office