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.
Nice bisecting search method and anonymous function for clean appearance.
Times 2 - START HERE
Find all elements less than 0 or greater than 10 and replace them with NaN
Back to basics 9 - Indexed References
Infinite precision division
Unique: Faster for options 'rows' and 'stable' for large array of uint8
PONG 003: 3-Ball Rectangle, Interactive Download
Battleship_010 : (TM) Classic Game - Methodical Bot (100 move max)
GJam 2013 Veterans: Baby Height Prediction
Hamming Weight - Fast
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