-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add Ichimoku forward candles #675
Comments
many thanks! |
Lol. I know, everyone wants everything immediately or sooner, right? Unfortunately, I do have a day job that requires most of my time and can really only spend a few hours a week on this project. Also, there are quite a few competing priorities in this backlog and some other things I'm goofing around on. In other words, I can't say exactly when I'll get to this one, but since it's a community request, I do tend to prioritize those higher than most other things. As per my usual response: contributors are welcome! I'd love to have more help from the community, especially from those who are avid users of the library. Help wanted! |
I've been looking at some of the popular charting sites to see how they predict future dates and it seems as though they have some metadata from each symbol that drives how future dates are selected. For example, an hourly TSLA chart would end at 4pm one day and start at 9:30 or 10 am the next day; whereas BTC-USD would continue after 4pm to 5pm, etc since it's on a 24-hour open market. Our library is not that smart about each symbol, so the only option for us to do this would be to somehow reverse engineer the incremental bar size and then randomly assign future dates OR require the user to specify the exact bar size and market open parameters to use. I'm not loving either of these options as I'm sure I'll be getting complaints about it being wrong. |
I’m still thinking about this one. I haven’t yet found a way to implement it. Help wanted, even if it’s just an idea for a solid implementation approach! |
Hi Dave, it is a must-have for my strategy to execute. Can we please solve it? I really appreciate what you are doing for us. |
I’d love to, but can’t quite figure out a simple way to make future candle dates align with what’s expected or accurate. Any ideas? |
I could manually produce similar results with the following formulas. The first one is easy, 2nd one requires a bit of going back in time and getting High/Low amongst 52 candles. Senkou Span A (Leading Span A): (Conversion Line + Base Line)/2)) This is the midpoint between the Conversion Line and the Base Line. The Leading Span A forms one of the two cloud boundaries. It is referred to as "Leading" because it is plotted 26 periods in the future and forms the faster cloud boundary. Senkou Span B (Leading Span B): (52-period high + 52-period low)/2)) On the daily chart, this line is the midpoint of the 52-day high-low range, which is a little less than 3 months. The default calculation setting is 52 periods, but can be adjusted. This value is plotted 26 periods in the future and forms the slower cloud boundary. |
The bigger vexing problem is not determining the values and actual number of future bars, but rather the actual accurate dates for them. You can imagine all the time scenarios with different markets that’d need to be considered. Crypto and Forex are typically 7 days a week, for example, equities 5 + cutoff times for hourly, etc. |
Until we get to implement the right thing, I’m locking this thread to avoid splitting our discussion, for now, please respond and comment to poll #1060. |
i can't see any result for future candles
Originally posted by @Salardx in #251 (comment)
FOR NOW, please respond and comment to poll #1060 with your thoughts and ideas.
What it does now
What it should do
The text was updated successfully, but these errors were encountered: