The WriteToDebugLog() output is currently organized by a BarHistory context. This is a good thing by default!
However, in some cases, the context isn't deterministic and in all cases, the chronology, which may be important for debugging, is lost (e.g., rotation systems).
The Request:
A preference for a chronological debug output.
However, in some cases, the context isn't deterministic and in all cases, the chronology, which may be important for debugging, is lost (e.g., rotation systems).
The Request:
A preference for a chronological debug output.
Rename
Whether or not this feature request is granted, some expandable help document should be included in the debug window explaining that the default debug output is reorganized and grouped-by-stock instrument (i.e. BarHistory), and not listed in chronological order (which is preferred for most debugging needs).
This feature request is offering an alternative chronological debug line output when needed. It may look messy (interwoven) because of the parallel execution threading of individual stock Execute{} operations.
This feature request is offering an alternative chronological debug line output when needed. It may look messy (interwoven) because of the parallel execution threading of individual stock Execute{} operations.
Your Response
Post
Edit Post
Login is required