Welcome to NexusFi: the best trading community on the planet, with over 200,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 -- discounts are available after registering.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Hello, i would to to ask you if you can share how do you detect support/ resistence levels in NT code. Do you use Swing indicator or any other approach? Can you give me an example?
thank you a lot
Tomas
Can you help answer these questions from other members on NexusFi?
If you create a new thread, please first check whether somebody else has already asked the same or a similar question. Below is one of the many threads, which you will find, if you type "support" and "resistance" into the search field.
:stickyman::stickyman:I am programming an automated trading system with a couple of other people. using R and python languages. Its time to define support and resistance and I am having hard time thinking of something satisfying, I came up with a couple …
Thank you Fat Tails for sharing your know how. I did what you wrote before i post new question very carefully and i was not fully satisfied with content.
Your reply is very common and i ask if somebody has experiance with SR zones in NT code. Do you agree that recognising SR zones in code is different from visual discrecionary?
All concepts of support and resistance rely on self-fulfilling prophecy, it is similar to Keynes' beauty contest: You want to vote for the girl that gets the highest number of votes, not for the girl that you like best.
This means that you basically have to find out what others are doing. If everybody uses yesterday's high or low, then you should use yesterday's high or low. The only difference between the code and the discretionary approach that I see is
-> It is easier to include S/R zones that originate from price action prior to the starting time of the chart via code.
-> It is easier to aggregate S/R zones via code than visually.
Coding also requires that the S/R zone is defined in an explicit and reproducible manner.
