Return Custom Indicator value within a window of time?
Welcome to futures io.
(If you already have an account, login at the top of the page)
futures io is the largest futures trading community on the planet, with over 90,000 members. At futures io, our goal has always been and always will be to create a friendly, positive, forward-thinking community where members can openly share and discuss everything the world of trading has to offer. The community is one of the friendliest you will find on any subject, with members going out of their way to help others. Some of the primary differences between futures io and other trading sites revolve around the standards of our community. Those standards include a code of conduct for our members, as well as extremely high standards that govern which partners we do business with, and which products or services we recommend to our members.
At futures io, our focus is on quality education. No hype, gimmicks, or secret sauce. The truth is: trading is hard. To succeed, you need to surround yourself with the right support system, educational content, and trading mentors – all of which you can find on futures io, utilizing our social trading environment.
With futures io, you can find honest trading reviews on brokers, trading rooms, indicator packages, trading strategies, and much more. Our trading review process is highly moderated to ensure that only genuine users are allowed, so you don’t need to worry about fake reviews.
We are fundamentally different than most other trading sites:
We are here to help. Just let us know what you need.
We work extremely hard to keep things positive in our community.
We do not tolerate rude behavior, trolling, or vendors advertising in posts.
We firmly believe in and encourage sharing. The holy grail is within you, we can help you find it.
We expect our members to participate and become a part of the community. Help yourself by helping others.
You'll need to register in order to view the content of the threads and start contributing to our community. It's free and simple.
Return Custom Indicator value within a window of time?
HI: First post, thanks for the assistance ;√)
The following simple "for" loop, looks back X number of days and indicates if the Volume
has exceeded the moving avg of volume by at least 4 Std Deveations.
{VOLUME> SDV CHECK WITHIN X# OF DAYS}
FOR WXD2 = 0 TO WXDST BEGIN
If VOLUME (WXD2) > SDVOL2
THEN VOLDCOUNT = WXD2;
End ;
WXD2 = WITHIN X DAYS, WXDST = IMPUT OF NUMBER OF DAYS YOU WANT TO LOOKBACK.
That works just fine. I am encountering a problem when the indicator is custom and I want the same lookback ability as the reserved word Volume provides, i.e., Volume(#). Where number is my lookback days counter. Below I am using the same loop, but the trigger is now the number of long tails in the previous X number of days.
The EasyLanguage compile error that I am receiving is: "Cannot implicitly convert Numerical to True False" I have tried to assign TSCOUNT to a new variable like "Value1" as suggested in the error code directory but still get the same error code.
{CHECK TSCOUNT > 9 WITHIN X# OF DAYS}
FOR WXD1 = 0 TO WXDST BEGIN
IF TSCOUNT(WXD1) > 9
THEN TCDCOUNT = WXD1:
End ;
Grateful for any help or sugestions. More than glad to share any code relating to this issue.
Quick Summary is created and edited by users like you... Add FAQ's, Links and other Relevant Information by clicking the edit button in the lower right hand corner of this message.
it's hard to say without knowing the full code. It could simply be that a variable is declared as boolean and now you try to store a numerical value with it. Besides that referencing previous bar values should be done with square brackets and not round brackets. At least the current Tradestation versions won't compile
where Volume is a reserved word. Which platform are you using?
Regards,
ABCTG
The following user says Thank You to ABCTG for this post:
Thanks, the problem was the omission of the square brackets. I assumed because I was using a variable to determine the days back that it should be () not []. Don't know why I made that assumption, but changing them eliminated the problem.
