5,838
edits
Category:Cumulus MX: Difference between revisions
m
→The Data Log Viewing and Editing interface: back to MX 3.6.0 state
m (→Data logs: deleted) |
m (→The Data Log Viewing and Editing interface: back to MX 3.6.0 state) |
||
| Line 963: | Line 963: | ||
== The Data Log Viewing and Editing interface == | == The Data Log Viewing and Editing interface == | ||
The '''Data logs''' tab in the admin interface | The '''Data logs''' tab in the admin interface, gives access to screens that can display the contents of 3 types of log files: | ||
#The [[Standard log files|standard log file]]; there is one of these for each month - choose menu item '''Data logs''' (yes same name as tab) | #The [[Standard log files|standard log file]]; there is one of these for each month - choose menu item '''Data logs''' (yes same name as tab) | ||
#The [[Extra Sensor Files|Extra Sensor log File]]; there is one of these for each month - choose menu item '''Extra Data Logs''' | #The [[Extra Sensor Files|Extra Sensor log File]]; there is one of these for each month - choose menu item '''Extra Data Logs''' | ||
| Line 1,000: | Line 1,000: | ||
*#'''Edit''' - rather obviously brings up a dialog (known as modal by the '''altEditor''' software that generates it) showing all fields and letting you change the contents of most individual fields. Scroll down and in the footer are two buttons: | *#'''Edit''' - rather obviously brings up a dialog (known as modal by the '''altEditor''' software that generates it) showing all fields and letting you change the contents of most individual fields. Scroll down and in the footer are two buttons: | ||
*##''Save'' will send the edited line back to the MX engine where the log file is then read into an array, and the relevant array element is replaced by the line received. After that the log file is overwritten from the amended array. After that the log file as a whole is converted back to dataTables format and returned by the api that delivered the table originally. | *##''Save'' will send the edited line back to the MX engine where the log file is then read into an array, and the relevant array element is replaced by the line received. After that the log file is overwritten from the amended array. After that the log file as a whole is converted back to dataTables format and returned by the api that delivered the table originally. | ||
*#''' | *#'''Close'''. You can close this dialog in 3 ways: | ||
*##clicking that Close button | *##clicking that Close button | ||
*##Clicking the small '''x''' at the top right | *##Clicking the small '''x''' at the top right | ||
| Line 1,015: | Line 1,015: | ||
*Lines in the log files created by earlier versions of Cumulus (Cumulus 1 or MX) may have fewer fields | *Lines in the log files created by earlier versions of Cumulus (Cumulus 1 or MX) may have fewer fields | ||
*The way that MX has been written is inconsistent in the way it deals with fields that MX now expects but at the time that log line was created did not exist. When adding the missing fields, some are added with empty string as content and some are added with a single space as content. When the editing modal is opened it will display placeholder text where a missing field is empty, but if you don't see that, there is a space that you can't see, but may well muck up any number you want to enter there. | *The way that MX has been written is inconsistent in the way it deals with fields that MX now expects but at the time that log line was created did not exist. When adding the missing fields, some are added with empty string as content and some are added with a single space as content. When the editing modal is opened it will display placeholder text where a missing field is empty, but if you don't see that, there is a space that you can't see, but may well muck up any number you want to enter there. | ||
*If you do edit a line, and then '''Save | *If you do edit a line, and then '''Save''', then that particular line (but no others in the log file) will change its length to that used by the current version of MX and you will see additional trailing field separators (commas, semicolons, or whatever defined for your locale) in that line making it seem different from its neighbours. Again you may spot that inconsistency in content as some gaps may appear between delimiters. | ||
== Changing Settings == | == Changing Settings == | ||