Difference between revisions of "PTL Trader Changelog"
From Pair Trading Lab WIKI
| Line 1: | Line 1: | ||
| + | == 1.0.0 == | ||
| + | * changed valid range for instrument margins (15% - 100%) | ||
| + | * cooldown period after closing a pair trade (it is not possible to open new pair trade earlier than in two minutes) - to prevent IB stats to settle | ||
| + | * more verbose logging of executions and commission reports (internal log) | ||
| + | * reworked periodic premium membership checks | ||
| + | * updated logo and icons | ||
| + | |||
| + | This version has not been released to the public yet. | ||
== 0.9.6b == | == 0.9.6b == | ||
* just a small fix - NYSEAMEX exchange has been apparently renamed to NYSEMKT, so both exchanges are now supported | * just a small fix - NYSEAMEX exchange has been apparently renamed to NYSEMKT, so both exchanges are now supported | ||
| Line 4: | Line 12: | ||
* Initial version released to public. | * Initial version released to public. | ||
* Status = BETA, not recommended for real trading yet (although we already use it that way ourselves) | * Status = BETA, not recommended for real trading yet (although we already use it that way ourselves) | ||
| + | |||
| + | |||
| + | == Known issues we are working on == | ||
| + | * slippage tracking sometimes does not work correctly in rare situations | ||
Revision as of 15:52, 26 June 2013
Contents |
1.0.0
- changed valid range for instrument margins (15% - 100%)
- cooldown period after closing a pair trade (it is not possible to open new pair trade earlier than in two minutes) - to prevent IB stats to settle
- more verbose logging of executions and commission reports (internal log)
- reworked periodic premium membership checks
- updated logo and icons
This version has not been released to the public yet.
0.9.6b
- just a small fix - NYSEAMEX exchange has been apparently renamed to NYSEMKT, so both exchanges are now supported
0.9.6
- Initial version released to public.
- Status = BETA, not recommended for real trading yet (although we already use it that way ourselves)
Known issues we are working on
- slippage tracking sometimes does not work correctly in rare situations
