Closed rdecorsi closed 7 years ago
@Hardcorehobel: could you please test if this bug still exists. If yes and there is no easy way to fix it, we should include a warning in the documentation that you cannot add time as a first value.
I cannot reproduce this bug. Using time as a first request in a multiple-request scenario works for me.
I was not able to test this as I have no Matlab on my Laptop, I just saw that this bug was still open. So I would assume that the problem no longer exists. If you like I can test it next week, or you can close it directly.
This doesn't seem to be a problem anymore.
Requesting time domain representations (output of the pre-processor) as first in a multiple request scenario will generate an error, for example:
A temporary fix is to re-order the requests to avoid time being the first one, e.g.,
mObj.addProcessor({'ild','time'});
. Note that an explicit'time'
request is usually unnecessary, as the pre-processing step is always applied for all other requests and the'time'
signal can be accessed through'mObj.Data.time'
, unless, of course, this representation is requested with a set of different parameters of its own.