Do you sometimes need to be sure an array has only bounded, positive values? At least one customer asked about this recently and noted that it could be quite involved. Depending on the duration for which you need to ensure this, there is more than one way to attack this.
Here are the two main scenarios I can think of.
I would be tempted to attack these scenarios in different ways. This week, I'll cover the first scenario.
If I were only going to check once in a while, I might write some code using some simple MATLAB functions and check details methodically.
The first method would try to test every assumption I can think of, perhaps like this:
ispositive = ( ~isnumeric(x) ... | ~all(isfinite(x(:))) ... | ~isreal(x) ... | ~(any(x(:) <= 0))); if ~ispositive doSomething(perhaps, throw, anError); end
There are some possible gotchas with this. There is a long of list of is* functions. Which ones do we need to consider? For example, old-style graphics handles are stored as doubles so they could confuse the results.
I can embed these checks into an assertion at places in my code where I want to be sure the data is correct. To not have to recreate the logic everytime, I can construct a function handle (anonymous in this case) and use it when I make each assertion.
fhispositive = @(x) ( ~isnumeric(x) ... | ~all(isfinite(x(:))) ... | ~isreal(x) ... | ~(any(x(:) <= 0))); assert(fhispositive(x), ... 'myapp:checkData:notPos', ... 'Data not all positive.');
I am now free to reuse the function handle with assert in strategic places throughout the code, not just at the one place where I typed the original code.
Note: you can do this as well by creating a separate function (in a separate file or a subfunction) to do the checking. Additionally, assert is only one possible behavior for the case where the data don't comply with the assumptions. You could instead set the data to a default value, for example.
In a MATLAB release R2007b, you'll find the function validateattributes (as well as validatestring). Using validateattributes, you can more compactly check data properties. You will get an error if the data doesn't match the requirements.
Here's a list of interesting functions to consider helping you with such checks including the is* functions mentioned above.
Stay tuned for a demo of a solution to the second scenario where you always want to ensure that the data is in a valid state. In the meantime, I'd love to hear if you have requirements or constraints where controlling the values in an array are important. Let me know here.