Forum: C2 Software Development
| |
| Subject: | [C2ATI] confirgsig (delay and localid) |
| Posted by: | Pranas B |
 |
| |
|
| When: | 6/17/07 (13:32) | |
|
|
|
|
| | Hi,
Is delay for each confirgsig request invocation needed?
I guess NO, but need some advice (not documented).
What is purpose of parameter "localid" (not documented clearly)?
Can the "localid" be skipped and only "permid" used instead?
Thanks |
|
| | |
|
| |
|
| |
|
|
|
| | In response to post by Pranas B of 6/17/07 (13:32) Hi,
Is delay for each confirgsig request invocation needed?
I guess NO, but need some advice (not documented)....
See entire
No delay is needed between confirmsigs. Localid is not necessary; you can use permid instead (or neither if you choose). I will try to put together a thoughtful answer to your other questions late tonight. - MK |
|
| | |
|
| |
|
|
|
|
What is the C2 Score?
Collective2 rates every trading advisor in its database and assigns a score between 100 and 1000.
In general, a rating above 500 is good. A rating above 700 is excellent.
Collective2 Ratings are recalculated daily based on the entire performance history in our database. The exact formula we use is proprietary, but there are several key variables that go into the Collective2 Rating. One of the most important factors is the length of time we have been able to observe the performance of the trader. Another key factor is the amount by which the trader over-performs or under-performs the S&P 500 index. Finally, the choppiness of the trader's results is taken into account. Certainly a more consistent trader will be rated more highly than a trader with erratic results.
