Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I have been teaching myself c# and slowly making progress trying to code up my current trading system.
Then found Bloodhound. It seems to do most of what I need to do and much more. However I have gotten stuck. My strategy is based on divergence and to date I have used the Ninza DivergenceEngine$. However this does not appear to work with Bloodhound.
Is anyone aware of a clean divergence indicator that does work with Bloodhound?
Thanks in advance.
Can you help answer these questions from other members on NexusFi?
Hey, I think you might have some settings wrong; the DEngine$ works fine in BH for me. Remember that you have to nest the indicator you will base divergences on in the DivergenceEngine$ within BH:
Once you do that, set the comparison to compare to 0:
and you should have it:
Hope this is useful.
I'm happy to send the template, but I'm still on BH 1.x so not sure if it will work for you. Besides, you should be able to recreate this easily.
Thank you for responding. You are right and it is fairly straight forward to use the DE$ long/short flags in Blood Hound. My trading qualifies the trade based on the actual indicator values at the divergence points and not just a L/S flag.
I spend some quality time with Shark Indicators this morning and think I have landed on a reasonable solution. My current plan is to write a pass-through wrapper for the DE$. I will either pass the "y" values through as well as various values so I can use these in the Comparison Solver (my preference), of if too hard I will just keep decision logic inside the wrapper - filtering out signals that do not meet my x & y criteria.
You just gotta love the flexibility of the tools we have these days!
Warmest,
Lex
PS a shout out to Keith from Shark Indicators for extending himself above and beyond reasonable expectations.
Hey, glad you got it sorted. Sorry for my uber-basic reply; I thought you were stuck on something simple, but clearly not.
Just out of curiosity, when you say "My trading qualifies the trade based on the actual indicator values at the divergence points and not just a L/S flag." are you talking about the underlying indicator used to spot divergences, like the MACD, or the DE$? I ask because I enquired awhile ago about setting up alerts for divergence candidates before confirmation but they (Ninza) said no dice. Just wondered if you were getting data from the DE$ itself or another indicator.
If you'd prefer not to divulge anything, no worries, but any insights would be appreciated.
I'm also working on an algorithm to see divergences from the values of the indicator, not price. That is my issue with D3 Spotter and many others in that they tell you there was a divergence after price has reached the peak/valley. Working from the indicator values does have the risk to alert too early, which is why I've been working on level detection that can be fed to a strategy for awhile. Let me know how it goes with divergence detection. It's a hard thing to solve as (IMO) it can't be solved consistently with knowledge of likely reversal zones, but when combined...
