You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As in title -- when using the apply.paramset.signal.analysis function, which calls on the post.signal.returns function, we're seeing the changes in the level, rather than returns.
Expected behavior
Be able to switch to analysing the behaviour post-signal in returns space.
Minimal, reproducible example
add a parameter called cum.return (default false so the function retains previous behaviour), but if true hits the following code block:
for(jin1:length(idx)){
signal.ret[j,] = tryCatch({
na.omit(diff( log(getPrice(mktdata[idx[j] + (days.increment*days.in.period) ,])) ))
}, error=function(e){
cat('')
stop('Not enough forward data to evaluate post signal returns.')
})}
signal.ret=t(apply(signal.ret+1,1,cumprod))-1
The text was updated successfully, but these errors were encountered:
Description
As in title -- when using the apply.paramset.signal.analysis function, which calls on the post.signal.returns function, we're seeing the changes in the level, rather than returns.
Expected behavior
Be able to switch to analysing the behaviour post-signal in returns space.
Minimal, reproducible example
add a parameter called cum.return (default false so the function retains previous behaviour), but if true hits the following code block:
The text was updated successfully, but these errors were encountered: