Sometimes it is difficult to remember which functions are not allowed on the Cody platform. Given a function as a string, return true if it is available on Cody and false otherwise.
The test suite will be updated periodically, so hard-coding the answers will eventually fail.
Examples
isavailable('bsxfun') returns true
isavailable('pdist2') returns false
Solution Stats
Problem Comments
6 Comments
Solution Comments
Show comments
Loading...
Problem Recent Solvers16
Suggested Problems
-
Replace NaNs with the number that appears to its left in the row.
3063 Solvers
-
Getting the indices from a vector
11790 Solvers
-
Given a window, how many subsets of a vector sum positive
870 Solvers
-
Magic is simple (for beginners)
11123 Solvers
-
Generate a random matrix A of (1,-1)
401 Solvers
More from this Author43
Problem Tags
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
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.