You mix two things: functions not allowed on Cody for safety reasons (evalin, assignin...) and toolbox functions not available (imfindcircles, ocr ...).
I am curious to know how you can make the difference. :.)
I realize there is a mix. That is part of the reason I created the problem.
Yes, but if you update the test suite with other Cody restricted functions (str2func, evalc) ?
With this mix a player can't submit a permanent solution. It's bothers me.
But maybe I am boring...
Interesting problem anyway.
Point well taken. I will not update the test suite until I verify that a permanent solution exists.
Maybe you should evaluate the existance of functions dinamically using try and catch as I did. The only problem is that functions such as eval or feval are available at cody although your test suite declares that they aren't. The system just doesn't allow us to use some functions, but they are there. So are they available or not? I would say that they are*.
* There are even ways to bypass this restriction.
'fwbmjo!bttjhojo!fwbm'-1? Did you think I would read the file and search for strings like 'eval'?
Not you but Cody maybe ...
Who knows the last digit of pi?
Angle between two vectors
Check if vertices form a rectangle
Convert matrix to 3D array of triangular matrices
Convert ColorSpec string to RGB triplet
The Python Challenge, Level 1: Decode strings
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