Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
Simulator reports
Collapse
X
-
Ray,
after hours of work I found what is causing the issue and to some degree it can be repeated over and over. I am suspect that the windows crash aka blue screen / stop error has a part in the chain of events as something triggered what took place. I say to some respect it can be repeated because I don't know what is causing the windows crash.
Steps I took this evening.
1. I reset the database in NT
2. I waited until MBT Maintenance was completed (which resets trade information to zero)
3. I selected the tab "positions" in the MBT NAV.
3. I placed a buy, counted to 5 and then placed a sell order for each pair MBT has available for trading.
4. I compared the P/L results as between NT and MBT for each pair and for the total.
I found that in all cases but one, the P/L was the same in both NT and MBT. The pair that did not match was EURGBP. I found the total account P/L was off by this same amount.
5. I disconnected MBT from NT
6. I reset the database
7. I restarted NT
8. I connected MBT
9. I began to explore NT's various reports (Orders, Executions, Positions etc.).
Even-though I reset the NT database, there was information on the orders and executions tabs.
I noted all transaction times were the same to the second. That the time matched the moment I connected NT to MBT. I also noticed the P/L values incorrect for most pairs
To recap
1. Something took place to wipe out/damage the NT database or an error in the database caused the windows crash.
2. That upon restarting NT and connecting to MBT, MBT information was fed back into NT all at the same time, giving me identical timestamps.
3. That something about this process corrupts or causes changes to the P/L.
Attached are comparison shots from MBT Positions and NT Positions. The post to follow this one will have account values.
Don
Comment
-
Don,
You likely forgot...
This is expected since as you reset, the database, NT will get all of the executions but the rate data needed to properly calculate the PnL can only be recorded at the actual time of execution. Since this is not the case in a reset, the PnL will never be accurate. I will check out the EURGBP however.RayNinjaTrader Customer Service
Comment
-
Ray,
It is not that I forgot something but rather was looking for the sequence of event that might help you understand what might be causing the issue that caused me to post(#47) about issues I was seeing with regards to trade P/L.
Before asking you in post #56 about rebuilding or resetting, I never touched that feature. I had no desire to reset it, but it seemed like it was worth a shot, being that my p/l and timestamps were wrong
The problems I experienced without resetting the database, were identical to those I experienced when I did reset the database.
That means some event took place without any action on my part that was the equivalent of resetting the database.
That event was either a result of the Windows crash or that event caused the database problem and Windows crash. As it was upon restarting from the crash that I had gone to the various trade reports and noticed the price and timestamp issues.
While there could be other events that caused the problem, I think the following are possibilities
1. NT caused a crash which blew-out the database
2. The database blew-out which caused NT to crash causing Windows to crash.
3. That Windows crashed blowing out the database.
To follow is the info from Windows on the crash - saying it was a hang in NT.
Hanging application NinjaTrader.exe, version 6.5.1000.1, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Details
Product:Windows Operating SystemID:1002Source:Application HangVersion:5.2Symbolic Name:ER_HANG_LOGMessage:Hanging application %1, version %2, hang module %3, version %4, hang address 0x%5. ExplanationThe indicated program stopped responding. The message contains details on which program and module stopped responding. A matching event with EventID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.
The following minimally says that I am not the only one having a problem.
Posted by another user (Larry22) in another thread..
Well I had the same kind of problem using Windows XP, and it's not the first time.
This only happened while Ninja was in operation otherwise it never crashed, my friend also had the same problem a few times.
Unfortunately I have no logs of what happened beside the fact that I got a blue screen.
So yes Ninja 6.5 can make Windows crashed and that is a fact.
Thanks
Don
Comment
-
I had thought the values update so there would be no need for adjustment. I changed the point value to 100000 from 200000 and now it matches MB.
I am sure if I modified GBPJPY I could get it to match as well. Although this pair did match once I installed the build so it seems the point value needs manual changing time to time to have it be in sync with MB.Last edited by BIGRED; 05-06-2008, 08:21 AM.
Comment
Latest Posts
Collapse
| Topics | Statistics | Last Post | ||
|---|---|---|---|---|
|
Started by NullPointStrategies, Yesterday, 05:17 AM
|
0 responses
62 views
0 likes
|
Last Post
|
||
|
Started by argusthome, 03-08-2026, 10:06 AM
|
0 responses
134 views
0 likes
|
Last Post
by argusthome
03-08-2026, 10:06 AM
|
||
|
Started by NabilKhattabi, 03-06-2026, 11:18 AM
|
0 responses
75 views
0 likes
|
Last Post
|
||
|
Started by Deep42, 03-06-2026, 12:28 AM
|
0 responses
45 views
0 likes
|
Last Post
by Deep42
03-06-2026, 12:28 AM
|
||
|
Started by TheRealMorford, 03-05-2026, 06:15 PM
|
0 responses
50 views
0 likes
|
Last Post
|

Comment