Voyager generates large log files over the course of the imaging night, however the file format was not designed to present a concise view of the night’s activities. These log files contain the entire story hidden amongst a lot of repetitive ‘noise’ and debugging information.
From midnight to dawn last night, my system generated nearly 285,000 lines in the 5.2MByte *Voyager.log file. The log extractor filtered this down to 296 lines and just 32kBytes. The extract is a time ordered and categorised record of Voyager’s activities that provides a detailed view of the unsupervised imaging session.
Now that would be a handy thing, I will give it a try. When I have needed to work out an issue by going to the logs (Invariably equipment or operator trouble) I have typically opened them in excel and used auto filters to boil it down to the lines useful to my problem. This should be much faster.
Hello for those interested by a concise log of events, i’ve posted last year a tool to persiste the “monitor log” file to the filesystem. I don’t use the voyager debug file. I guess this one is mainly focus on things leonardo can manage.