 Posted 2/22/2007 11:18:35
|
|
|
|
I understand how it can be useful to have several "System Result" pages while testing along and changing some parameters here and some code there.
The way it is now it is not too useful, because I get lost in all these identical looking "System Results".
I miss some "Date/Time" of test-run.
Probably some more annotations like
* WatchList
* System Settings (Start/End Date, Position sizing, etc)
* A comment field that finds its way to the printed output, so I can add things
like: "in this version we changed the calculation for XYZ to fuzzy-overwhelming mode"
As always, the most important thing is documentation. Good if RE helps the system developer here.
www.finantic.de
Our Trading System at C2: Topaz
|
|
|
Posted 2/22/2007 11:35:28
|
|
|
|
DrKoch (2/22/2007)
I understand how it can be useful to have several "System Result" pages while testing along and changing some parameters here and some code there.
The way it is now it is not too useful, because I get lost in all these identical looking "System Results".
I miss some "Date/Time" of test-run.
Probably some more annotations like
* WatchList
* System Settings (Start/End Date, Position sizing, etc)
* A comment field that finds its way to the printed output, so I can add things
like: "in this version we changed the calculation for XYZ to fuzzy-overwhelming mode"
As always, the most important thing is documentation. Good if RE helps the system developer here.Date/Time - Good idea. This was something that was planned, but fell through the cracks. I am adding it to the bug tracker. Bug 798. I see this as the date range for bars run regardless of system settings limiting date. In other words if you specificy a start date of 1970 and no end date, but there is only data from 1980-1990 we would show that we ran the system on bars from 1980-1990. Watchlist - We already show the symbol list that the system ran against in the 'Symbol Results' subpane, so that is covered. System Settings - Good idea. Added Bug 800 . This should also include system variables. Comment Field - How would this be implemented? A method called to set this from the system? A freeform entry field ojn the system results where you type this in?
|
|
|
Posted 2/22/2007 11:43:13
|
|
|
|
| Daniel just had another good idea. Charts opened from system results should be labeled with what system result window they were opened from. Bug 801.
|
|
|
Posted 2/22/2007 12:00:45
|
|
|
|
> I see this as the date range for bars run
Yes, this is an important piece of information.
What I had in mind was the Date/Time of the "Run" i.e. when did I press the "Run Simulation" button.
So it gives me a clue, which version of my script was used.
This wonderful run before lunch or the bad one after the coffee break?
If I dream along this lines I'd be happy about another entry in the Tools menu.
And guess what, I want the ability to enter the name of this entry and a commandline which gets executed if I click this entry.
My first use for this: I'd add an entry "Put Script Version into Subversion" and connect it with a call to subversion which adds the current version of my script(s) to the Subversion version control system.
A feature bitterly missing from WL - could save endless hours of seraching for the last damn changes that destroyed this marvolous system (mentioned above, the one before lunch)
www.finantic.de
Our Trading System at C2: Topaz
|
|
|
Posted 2/22/2007 12:13:53
|
|
|
|
DrKoch (2/22/2007)
> I see this as the date range for bars run
Yes, this is an important piece of information.
What I had in mind was the Date/Time of the "Run" i.e. when did I press the "Run Simulation" button.
So it gives me a clue, which version of my script was used.
This wonderful run before lunch or the bad one after the coffee break?
If I dream along this lines I'd be happy about another entry in the Tools menu.
And guess what, I want the ability to enter the name of this entry and a commandline which gets executed if I click this entry.
My first use for this: I'd add an entry "Put Script Version into Subversion" and connect it with a call to subversion which adds the current version of my script(s) to the Subversion version control system.
A feature bitterly missing from WL - could save endless hours of seraching for the last damn changes that destroyed this marvolous system (mentioned above, the one before lunch)Bug 802 added regarding date/time of system run. As for a 'run command' on the tools menu, what sort of things would we need to provide you with here so that you could pass them to the command line. I would imagine something like this is necesary so you know what it is you want to check in and where it lives.
|
|
|
Posted 2/22/2007 12:21:21
|
|
|
|
Hmmm, look at Visual Studio, Build Events. They define some variables and (undocumented) allow environment variables as well. That would be the right way to go...
At least for one of these old fashioned command line types like me... 
www.finantic.de
Our Trading System at C2: Topaz
|
|
|
|