I notice after 200 lines of output the output stops completely.
Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
output window
Collapse
X
-
output window
I have created my own custom script in NT 6.5Originally posted by NinjaTrader_Austin View Postrjngh2005, there is a limit, but the old output should be deleted and replaced by the new output. It should definitely not stop printing output. Sometimes the auto-scrolling will stop, and the new output isn't visible. What sort of script did you use to test this?
It basically has two timeframes 15 minute and 5 minute
and I am printing the output on every new candle of the 5 minute..
Comment
-
rjngh, thanks for the update. If you restart your computer does the issue still persist? Does this also occur in NinjaTrader 7?
EDIT: I just created a simple script to test this out with NT6.5 (haven't used it in a long time) and it printed 15000 some lines of output.
This code produced 15565 lines of output on a 1 minute ES 09-11 chart.Code:OnBarUpdate() { Print("current bar number: " + CurrentBar.ToString()); }Last edited by NinjaTrader_Austin; 06-24-2011, 09:29 AM.AustinNinjaTrader Customer Service
Comment
-
I tried a simple script to find where it breaks
Then I tried to introduce a little complexity
That worked too
next I tried this script which failed
Script is attachedAttached Files
Comment
-
rjngh2005, I just ran the most recent strategy you posted and there were no trades generated, no text to the output window, and no error messages in the logs. This means the entry conditions are too restrictive, and are not being met, so no trades are being placed.
Please take a look at the sample multi timeframe strategy that comes with every NinjaTrader installation (Tools -> Edit NinjaScript -> Strategy -> SampleMultiTimeFrame) for guidance on how to create multi-timeframe strategies.AustinNinjaTrader Customer Service
Comment
-
The strategy is a simple strategy of EMA(5), EMA(13)Originally posted by NinjaTrader_Austin View Postrjngh2005, I just ran the most recent strategy you posted and there were no trades generated, no text to the output window, and no error messages in the logs. This means the entry conditions are too restrictive, and are not being met, so no trades are being placed.
Please take a look at the sample multi timeframe strategy that comes with every NinjaTrader installation (Tools -> Edit NinjaScript -> Strategy -> SampleMultiTimeFrame) for guidance on how to create multi-timeframe strategies.
why are there no trades generated when the chart clearly indicates that EMA(5) , EMA(13) is crossing over.
Comment
-
Bertrand,Originally posted by NinjaTrader_Bertrand View PostYou will need to debug the script then to see where it exactly breaks, the one you posted would run in real-time going forward only since 'Historical' is used, so there will be no historical / backtest trades.
I am using Market Replay to test the script.
Could you explain if this will work ?
Your associate tried my script and it failed...
why is this failing ?
Comment
-
rjngh2005,
Market Replay is sufficient for testing realtime behavior. Unfortunately though we will not be able to debug this for you. I suggest you start by adding a bunch of Print()s into your code and track each of its conditions to try and understand what your strategy is doing. If it never trades it either means your orders are just being rejected/ignored or your entry conditions were never satisfied. You can use TraceOrders = true to analyze if your orders were ever submitted or not, but you will need to slowly debug with Print()s to figure out what is going on with your entry conditions.Josh P.NinjaTrader Customer Service
Comment
-
My logic is perfect in the code.Originally posted by NinjaTrader_Josh View Postrjngh2005,
Market Replay is sufficient for testing realtime behavior. Unfortunately though we will not be able to debug this for you. I suggest you start by adding a bunch of Print()s into your code and track each of its conditions to try and understand what your strategy is doing. If it never trades it either means your orders are just being rejected/ignored or your entry conditions were never satisfied. You can use TraceOrders = true to analyze if your orders were ever submitted or not, but you will need to slowly debug with Print()s to figure out what is going on with your entry conditions.
I have tested this a number of times.
The script starts working as expected however after 70 or 80 bars it quits
The problem is with Ninja not being able to handle computations
Comment
Latest Posts
Collapse
| Topics | Statistics | Last Post | ||
|---|---|---|---|---|
|
Started by Geovanny Suaza, 02-11-2026, 06:32 PM
|
0 responses
647 views
0 likes
|
Last Post
|
||
|
Started by Geovanny Suaza, 02-11-2026, 05:51 PM
|
0 responses
369 views
1 like
|
Last Post
|
||
|
Started by Mindset, 02-09-2026, 11:44 AM
|
0 responses
108 views
0 likes
|
Last Post
by Mindset
02-09-2026, 11:44 AM
|
||
|
Started by Geovanny Suaza, 02-02-2026, 12:30 PM
|
0 responses
572 views
1 like
|
Last Post
|
||
|
Started by RFrosty, 01-28-2026, 06:49 PM
|
0 responses
573 views
1 like
|
Last Post
by RFrosty
01-28-2026, 06:49 PM
|

Comment