Alert Time Data Series Object not saving?

[brucerobinson]

Hello Bruce,

I added an alert to one of the 6b 5 minute charts set to 2:45, and another set on the RTY 1 minute at 2:43. This is during a 'slow market' shortly before the day's close, so not many ticks are coming through.




As you can see in the screenshot, the alerts fired but a fairly significant amount of time after the time it was set to, particularly 6b. This makes sense as the 6b has very limited trading during this time.

I believe this explains the 'lag' on some of the alerts. This seems to be a limitation of NinjaTrader needing to receive a tick to fire the alert once the time is reached.

You may want to consider using NinjaScript to create such alerts as they can be linked to the system clock and would not have this limitation. I was unable to find such a indicator on our user app share, so it looks like this would have to be custom coded.




Please let me know if you have any further questions.


Hello Ryan and thanks.
I understand what you have done and why it is so.
However it isn't of use to me because it has no relevance to my use. insofar as a) I don't have this problem of lack of ticks coming through, b) I am not interested in using alerts where this is the case so will never encounter this situation, c) is not the cause of the alerts not working as described.

It is a problem I don't have, and not an answer to the problem I experience nor solution. 5 minutes prior to the Opens and Closes of the markets I have given you of FDAX, CL, GC, ES there is no lack of ticks. The problem of being variously multiples of the bar period early or late is nothing to do with lack of ticks.

The question remains, why are the Alerts exhibiting the behaviour they are, which is not as they should - it has nothing to do with this nor is this of any relevance or benefit.

Kind regards,

[brucerobinson]

Hello Bruce,




So I understand, the main issue is with the instances of the alert firing prematurely?

eg. this post from the forum:

Hello,
Update -

DAX Open Alert triggered - RHS Condition Time value 03:25, triggered 03:20:02
GC Open Alert triggered - RHS Condition Time value 08:15, triggered 08:10:01
CL Open Alert triggered - RHS Condition Time value 08:55, triggered 08:50:00
ES Open Alert triggered - RHS Condition Time value 09:25, triggered 09:25:00
DAX Close Alert triggered - RHS Condition Time value 11:25, triggered 11:20:00

Seems ES is the only one that exhibits expected behaviour.
Kind regards,




In this scenarior, the ES is the only one not exhibiting expected behavior. Since each of these time alerts is assumed to be running on a 5 minute bar, all of the others fire after the first tick is received on a 5 minute bar, which occurs ~ 5 minutes prior to the time value set since bars are time stamped at the end of bar. So the 3:25 time value bar starts at 3:20:00.




Using this, the ES should have fired around 9:20. Is ES still the only instrument experiencing this behavior?


Sincerely,
Ryan S
NinjaTrader Platform Customer Service

[brucerobinson]

Hello Ryan and thanks.


"So I understand, the main issue is with the instances of the alert firing prematurely?"
I would say the main issue is 47 Posts, numerous emails and this is still barely getting anywhere.

That, and incorrect documentation aside - I numbered 3 issues. see an earlier Post.
It is now transparent how this is 'expected' to work (not how a User would and not documented how it does, but I guess we should look for the positives)

"issue is with the instances of the alert firing prematurely?"
I have posted numerous example where several instruments, ES and others, fire late.
See my Posts 44 & 45 for GC & CL examples.yesterday just before you sent me the above email

What is the point in me taking time to send you this if you don't read?

"
In this scenarior, the ES is the only one not exhibiting expected behavior. Since each of these time alerts is assumed to be running on a 5 minute bar, all of the others fire after the first tick is received on a 5 minute bar, which occurs ~ 5 minutes prior to the time value set since bars are time stamped at the end of bar. So the 3:25 time value bar starts at 3:20:00."
And in my very next post I gave examples of a whole bunch not doing so, some not triggering until the subsequent bar (which is in fact what the most recent GC & CL show happening)

"Using this, the ES should have fired around 9:20."
Agreed
" Is ES still the only instrument experiencing this behavior?"
In despair at the progress of this, yesterday I decided to simply change the alerts so they were sufficiently ahead that even if a bar late they'd still be ahead of the Markets Open/Close e.g. 15mins using 5 minute bars.
In doing so, I changed the Names of the Alerts (from ,Gold Open in 5 mins, to Gold Open).
Doing so 'strips out' the Condition LHS Time setting. It doesn't appear so, but on re-opening.
Which is the Subject Heading of this thread. Change the Name and it breaks the Alert. I'm sure it is Expected Behaviour in Ninja's view. Never heard such ridiculousness in all my puff. Change a name and it removes the Condition. It isn't Documented. It is dismal.
Which is my numbered point 2 If I recall correctly, and what you asked me about re: aborted attempts to use Alerts a year ago, when new Releases did similar..
Hence, they didn't fire today - but I have no reason to expect they've miraculously changed behaviour.

Kind regards,

[brucerobinson]

having rebuilt the CL alerts, CL has just triggered correctly