Feb. 05 Update:

I’ve been working on a couple of different things over the past few days:

Lack of Recent Publishing

Late yesterday afternoon, @KTm made me aware of an issue that she discovered. Her reporting scripts were still running, but information wasn’t making its way to Github. When I investigated the issue it turned out that the Excoin outage was indirectly responsible. There is an oversight in the current set of reporting tools that puts the report processing into a fatal logic loop if an exchange’s API isn’t accessible. This is a straight-forward enhancement, so I’ll get that fixed and push out a new version to the custodians as soon as I get a chance to work on it today.

My apologies on missing something that, in retrospect, is very obvious.

Reporting Visual Interface

The front end for the reporting has temporarily been reduced in priority while I work on the other items listed. My goal is to get back on this ASAP, but if there is anyone in the community with a background in front-end development, who would be interested in working with me to accellerate the speed that I can get this portion out, please let me know. I’m not the fastest developer, and am learning as I go along – getting faster every day, but not nearly fast enough

Enhanced Historical Logging

By design NuBot creates a new subdirectory in the logs directory where it runs for each session. Previously we had been relying on the discrete output in wall_shifts.json and orders_history.csv to pull together the information that appears in the custodian’s summary.json report (in addition to the trade data returned from the different exchanges’ APIs).

NuBot activity logs are now being parsed in aggregate across different sessions (anytime the bot operator starts/stops/restarts the bot). This change has not been pushed live and is still undergoing testing. So far the test results are looking very positive and I’m optimistic that I’ll be able to migrate these changes to the Raportisto repository in the next few days.

With this added information, we’ll be able to provide a historic view of all* of the orders placed and the prices they were placed at, along with the reported price of NBT in whatever market is being supported. With this data we should be able to build a picture of how liquidity has changed over time and identify time periods when the bot was more (or less) susceptible to potential value losses or gains.

* ‘All’ of the data retained, which is likely every session, but there are probably still going to be a few gaps in the data set due to external issues like bot server downtime.