I don’t know at this time just how useful these indicators are for trading in general and specifically Futures, the instruments I like to trade. However, given the source John F Ehlers, I would consider the probability pretty good.
In addition to using these indicators in BH, part of my purpose in creating this thread goes beyond them and what I hope to accomplish is to involve others in helping to:
1. determine the usefulness of these indicators and how they should be setup to be useful in trading,
2. determine what other changes could make them more useful, and (with the most important following)
3. test the concept that making code changes to produce various signals can simplify building and making changes to BH strategies.
With the array of BH tools at least most of the signals that are emitted in these indicators there is a BH solver or combination of solvers that could also produce the same signal. However, to do so will no doubt require more work and a more detailed BH strategy. For example, when the Extended Signals option is set in the DecyclerOscillator up to 18 discrete signals can be produced. Testing those signals would require 4 Threshold solvers. To do the equivalent would require at least some combination of at least 9 solvers.
Furthermore, given that there are not any mathematical capabilities in BH there is at least one condition in one of the indicators that would be either difficult or not possible to determine and produce a signal. Whether or not the particular signal is even useful, the point is that there are conditions that may be potential signals and useful for trading which can only be determined and produced in code. This may change in a future BH release but right now I believe it to be true.
Although initially the identified purpose was oriented to the 2 indicators mentioned, the main focus is really item 3 above. Is there any value derived from making programming changes to indicators to produce signals to be used in BH? Assuming for the moment that there is value in coding signals directly into the indicator then several other considerations come to mind. Of course if it is determined the efforts required are greater than the rewards produced then this thread will die of its own accord.
Continuing on the assumption, examples of some of the considerations might be the best practices for:
1. the type of Series passing the values (Bool, Int, Data)
2. the values being passed (specifically for the Int and Data Series)
3. the meanings assigned to these values
4. any naming convention for the Series
5. controlling changes to any of the above
6. documentation for use
I’m certain there are others.
The indicators can be found here (. Note that they are packaged together.
New versions not yet released to the downloads section: