Tonight I will show to debug a log which your trading system generates
I posted this on my Facebook Live as a video to explain the rationale and details. If you are interested, get in touch with me as soon as possible. This event takes place tonight starting at 6 PM so you should say we are into the final hours.
This topic is on
Debugging your log for algo trading patterns with crypto currency asset class
I have reversed yesterdays topics. This event on Tuesday is becoming more crucial in my recent success in the down market of the crypto currency asset class
I have an important event for my Quant Elite memberson Tues regarding debugging you trading strategy with logs, I thought I would make a last offer for those interested in this event. I don’t think I will even record as it is meant for ANNUAL FULL ELITE members. If you are interested in knowing further about this, get in touch with me right away to be included on the details of this. It takes place this Tues Sep 11 6pm Eastern Standard time
I just posted this yesterday.
I have put together a 20 minute video describing the wild losses of yesterday my system picked up. It was apparently one of the worst days for the crypto currency asset class in about a year. As a result, I made some huge improvements which looks like I may have resolved. I even offer some debugging tips to help out here. As a result of this, you may want to check out this video here.
As said, if you are interested in this event for Tuesday, get in touch right away to make your arrangements to be part of this. This is a topic that not many talk about but as a programmer, this point of view gives you a unique perspective in trading for big profit!
Sawzall is a procedural domain-specific programming language, used by Google to process large numbers of individual log records
Google’s server logs are stored as large collections of records (protocol buffers) that are partitioned over many disks within GFS. In order to perform calculations involving the logs, engineers can write MapReduce programs in C++ or Java. MapReduce programs need to be compiled and may be more verbose than necessary, so writing a program to analyze the logs can be time-consuming. To make it easier to write quick scripts, Rob Pike et al. developed the Sawzall language. A Sawzall script runs within the Map phase of a MapReduce and “emits” values to tables. Then the Reduce phase (which the script writer does not have to be concerned about) aggregates the tables from multiple runs into a single set of tables.
Currently, only the language runtime (which runs a Sawzall script once over a single input) has been open-sourced, and the supporting program built on MapReduce has not been released
Sawzall was first described in 2003, and the szl runtime was open-sourced in August 2010. However, since the MapReduce table aggregators have not been released, the open-sourced runtime is not useful for large-scale data analysis off-the-shelf