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
Chartseries adds (by default) a second volume chart, equivalent to "addVo ()"
The volume chart scale is represented in a friendly way (x thousand, x one hundred thousand, etc.)
When we add the Volume average to this graph, it is plotted without friendly scaling (x unit) and is outside the plot area.
Expected behavior
he expected behavior is to represent "SMA (Vo (VALE3.SA), n = 20)" on the same scale as the variable that created the second graph, in this case "Vo ()".
Minimal, reproducible example
# incorrect behavior of function Vo() in second graphfim<- Sys.Date()
inicio<- Sys.Date() -730
getSymbols("VALE3.SA", from=inicio, to=fim)
chartSeries(VALE3.SA, theme="white", TA='addEMA(n=21); addVo(); addTA(SMA(Vo(VALE3.SA), n=20), on=2)', subset='last 6 months')
# correct behavior, add function in second graph, but not Vo() function
chartSeries(VALE3.SA, theme="white", TA='addEMA(n=21,col="red"); addOBV(); addTA(EMA(OBV(Cl(VALE3.SA), Vo(VALE3.SA)), n=10), on =2)', subset='last 6 months')
Session Info
[Insertyour sessionInfo() output]
The text was updated successfully, but these errors were encountered:
I agree that this is a bug in chartSeries() and/or addTA(), but I'm not sure it's worth the effort to try and fix. Especially when chart_Series() works.
Description
Chartseries adds (by default) a second volume chart, equivalent to "addVo ()"
The volume chart scale is represented in a friendly way (x thousand, x one hundred thousand, etc.)
When we add the Volume average to this graph, it is plotted without friendly scaling (x unit) and is outside the plot area.
Expected behavior
he expected behavior is to represent "SMA (Vo (VALE3.SA), n = 20)" on the same scale as the variable that created the second graph, in this case "Vo ()".
Minimal, reproducible example
Session Info
The text was updated successfully, but these errors were encountered: