[MAS-announce] Signal generation: file logging bug has been fixed

[Jim C. <jt...@di...>]

I have just discovered that the bug that caused a core dump when
using the file logging options for trading signal generation is fixed.
This may especially be good news to Windows users who have struggled
unsuccessfully to get event (signal) logging working with the the awkward
"fake_mailer.bat" script.  The facility is also available to Linux users,
of course - for those who wish to log their signals to a file instead
of have them sent as email.  (See below for a description of how to use
file logging.)

I should mention that I tested this on Windows with the new mas.exe
(1.6.6g) and on Linux with 1.6.6g and the old 1.6.5 release.  Since all
tests were successful, I think there's a very good chance that Windows
users will also find that it works with 1.6.5.

However, as many of you know, a couple tests cannot ensure that a problem
does not exist.  I think the chances that the bug remains are small, since
the previous behavior was quite consistent: generate a core dump.  If
anyone tries out file logging with 1.6.5 or later and still runs into
problems, please let me know.

Why did I not discover this earlier?  Simply because I had done nothing to
fix the bug and hadn't thought to test it before - too much to do.  Chances
are 99.9% that the bug was in the ISE library class I was using and it has
been fixed there.

To use file logging for trading signals: From the MAS command line enter
'r' for Edit event registrants, then 'a' for Add registrants, then 'l' for
Log file.  Type a file name for the log file.  Then choose the event types
you want.  Then type '-' for Previous, then 's' for Save changes.  The next
time you run a market analysis, this "registrant" will be used and the
generated signals will be written to the log file whose name you specified.


Jim