Color Change Hull Moving Average Alert

This topic has 13 replies, 3 voices, and was last updated 4 years ago by John Henry.

Viewing 14 posts - 1 through 14 (of 14 total)

04/12/2020 at 2:57 AM #125745

John Henry

I have unsuccessfully found an answer to this question…

How to create an alert that triggers each time the color changing hull turns over from red/green, green/red.

Any help would be greatly appreciated.

thanks

John Henry

Participant

Topics: 4

Replies: 8

Been thanked: 0 times

04/12/2020 at 8:53 AM #125751

robertogozzi

Set it when it when:

Hull > Hull[1] and Hull[1] < Hull[2] (bullish)
Hull < Hull[1] and Hull[1] > Hull[2] (bearish)

1 user thanked author for this post.

John Henry

robertogozzi

Moderator

Topics: 69

Replies: 16465

Been thanked: 3641 times

04/12/2020 at 7:15 PM #125823

John Henry

Thank your robertogozzi.
I am new to all this, I’m not sure what that means?
Not even sure what tutorial to look up to figure out what that means lol.
Can you give me some clarification on what you are suggesting I do with the information provided?
thanks

John Henry

Participant

Topics: 4

Replies: 8

Been thanked: 0 times

04/12/2020 at 7:33 PM #125825

robertogozzi

What version are you using?

Do you use a built-in Hull indicator or a custom one?

robertogozzi

Moderator

Topics: 69

Replies: 16465

Been thanked: 3641 times

04/12/2020 at 7:43 PM #125831

John Henry

here is the code of the hull ma I’m using

//HullMA, the Hull Moving Average:
Period = 95
Data = Close
inner = 2*weightedaverage[round(Period/2)](Data)-weightedaverage[Period](Data)
S = weightedaverage[round(sqrt(Period))](inner)
return S

//HullMA, the Hull Moving Average:

Period = 95

Data = Close

inner = 2*weightedaverage[round(Period/2)](Data)-weightedaverage[Period](Data)

S = weightedaverage[round(sqrt(Period))](inner)

return S

John Henry

Participant

Topics: 4

Replies: 8

Been thanked: 0 times

04/12/2020 at 8:19 PM #125834

Vonasi

John Henry Welcome to the forums.

There are some simple rules that everyone using the forums is expected to follow. Your post has broken one or more of these rules.

The forum rules are as follows. I have highlighted in bold the rule/rules that you have not followed:

Post your topic in the correct forum.

ProRealTime Platform Support only platform related issues.
ProOrder only strategy topics.
ProBuilder only indicator topics.
ProScreener only screener topics
General Discussion any other topics.
Welcome New Members for new forum members to introduce themselves.

Only post in the language of the forum that you are posting in. For example English only in the English speaking forums and French only in the French speaking forums.
Always use the ‘Insert PRT Code’ button when putting code in your posts to make it easier for others to read.
Do not double post. Ask your question only once and only in one forum. All double posts will be deleted anyway so posting the same question multiple times will just be wasting your own time and will not get you an answer any quicker. Double posting just creates confusion in the forums.
Be careful when quoting others in your posts. Only use the quote option when you need to highlight a particular bit of text that you are referring to or to highlight that you are replying to a particular member if there are several involved in a conversation. Do not include large amounts of code in your quotes. Just highlight the text you want to quote and then click on ‘Quote’.
Give your topic a meaningful title. Describe your question or your subject in your title. Do not use meaningless titles such as ‘Coding Help Needed’.
Do not include personal information such as email addresses or telephone numbers in your posts. If you would like to contact another forum member directly outside of the forums then contact the forums administrator via ‘Contact Us’ and they will pass your details on to the member that you wish to contact.
Always be polite and courteous to others.
Have fun.

I have edited your post where required. Please ensure that your future posts meet these few simple forum rules. 🙂

Vonasi

Moderator

Topics: 192

Replies: 5088

Been thanked: 1810 times

04/12/2020 at 8:32 PM #125838

John Henry

Vonasi I am new to this platform and this forum
I do not understand what rules I broke and I certainly didn’t break them on purpose
As for “Always use the ‘Insert PRT Code’ button when putting code in your posts to make it easier for others to read.”
I don’t even know what that is.

John Henry

Participant

Topics: 4

Replies: 8

Been thanked: 0 times

04/12/2020 at 8:37 PM #125839

Vonasi

The rules are the things written just above the submit button – you read them before pressing submit being the general idea! 🙂

If you don’t understand any of them then just ask – we don’t bite but we do like a tidy forum.

See the attached image for where to find the ‘Insert PRT Code button’ and many other useful tools.

Vonasi

Moderator

Topics: 192

Replies: 5088

Been thanked: 1810 times

04/12/2020 at 8:56 PM #125841

robertogozzi

Ok, it’s just a matter of replacing HULL with S:

S > S[1] and S[1] < S[2] (bullish)
S < S[1] and S[1] > S[2] (bearish)

S, or S[0], is the current bar, S[1] is the previous bar leftwards, S[2] is the second previous bar leftwards.

robertogozzi

Moderator

Topics: 69

Replies: 16465

Been thanked: 3641 times

04/12/2020 at 9:08 PM #125845

John Henry

gotcha thanks
where would that code be pasted into the original code?

John Henry

Participant

Topics: 4

Replies: 8

Been thanked: 0 times

04/12/2020 at 10:53 PM #125852

robertogozzi

That’s not code.

It’s what you need to set alarms.

When you add an alarm on your HULL moving average you must set it according to signals returned.

It must activate when the conditions are as I described.

You want to set alarms, don’t you?

It must be triggered when the value returned (i.e. S or whatever it is called) is either:

greater than that of the previous bar and that of the previous bar is less than the one of the second previous bar
less than that of the previous bar and that of the previous bar is greater than the one of the second previous bar

That is the alarm is triggered when direction (or colour, as you said) has changed.

robertogozzi

Moderator

Topics: 69

Replies: 16465

Been thanked: 3641 times

04/12/2020 at 11:09 PM #125854

John Henry

You are correct I do want to set these as alarms as I have on other platforms
but I am unclear as to how to apply the criteria you’re recommending.
When I set an alert on the hull and the alert settings are open I’m unclear where this information should go

John Henry

Participant

Topics: 4

Replies: 8

Been thanked: 0 times

04/13/2020 at 12:22 AM #125856

robertogozzi

I am attaching 2 screenshots for the first case (colour changes from Red to Green) alarm:

X1 shows how to set condition 1 (S, that is the current value must be > than S[1] that is the previous one)
X2 shows how to set condition 2 (S[1], that is the previous value mist be < than S[2] that is the second previous one)

you’ll have to add another two opposite conditions for the seconda case (Green to Red), or you may add a separate alarm for that.

Here you’ll find several videos to learn how to use the ProRealTime platform https://www.youtube.com/channel/UC0OEWQSbrDTH2ArVFAzNJkQ or https://www.prorealtime.com/en/video-tutorials.