Hint: when the Problem Statement uses phrases like "reasonably accurate" and "sufficiently accurate", it is a clue that your Test Suite should not require 'equality' to any 'exact values', but rather should include a small tolerance to allow for unavoidable floating-point imprecision.
It was very hard to understand what do you mean.
I'm glad you managed to find a solution. I tried to provide a few extra clues, such as in the Solution Template and in the comment from 02 June. Players will benefit from looking up the Documentation on functions such as "assert", "isequal", etc., along with information on "Floating-Point Numbers" at https://au.mathworks.com/help/matlab/matlab_prog/floating-point-numbers.html . There are also many other resources online, such as www.floating-point-gui.de . For some people this should be a simple problem to implement their existing knowledge; for other people, it should be a learning process. —DIV
Since assert is not working anymore, it is necessary to use the dummy variable and the function error.
Make a run-length companion vector
Return a list sorted by number of consecutive occurrences
Tick. Tock. Tick. Tock. Tick. Tock. Tick. Tock. Tick. Tock.
Comparison of floating-point numbers (doubles)
Guess the number I'm thinking of
Code breaker, Part I: Operation Phoenix
Seemingly impossible problem
Code breaker, Part III: Operation Xiangliu
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