I’ve done a bit of work on improving the Emoncms post processing module. v2.4.6 is now available for testing in the master branch. New features include:
Ability to select existing feeds to reprocess when creating new processes and the option to select between processing of recent data and reprocessing the whole feed. Previously a new feed always needed to be created and so this could end up being a bit of a fiddle if you wanted to apply post processing to a feed that is already linked to live data coming in via inputs.
The option to Edit an existing process, can be useful for reprocessing with different limits, e.g max and min power limits if these settings were not correct the first time.
Improved process list user interface without the log view, but with status feedback provided in the list directly. Statuses include: Queued, Finished & Error. The error message is displayed alongside the Error status.
Better process descriptions and human readable names, a categorised post process selection drop down.
There’s a feed selector helper for the formula process, that adds the f123 feed text into the formula box.
There’s also a lot of refactoring behind the scenes. Processes are implemented as classes with the process descriptions in the same file as the process code. The user interface is now implemented using vue.js.
I’d like to be able to generate summary data, especially for weather data, then trim off some of the older 10s data. This could also be used to build a summary history of hourly/daily/weekly/monthly/yearly energy use so you can build a summary of your data (and trim the old fine grain data).
Could this be added with all the refactoring?
If this could run automatically (say once a day) and add those data points to Feeds, all the better.
@TrystanLea : Thanks, just tested, very nice and flexible
As I am now running emoncms in container, I made some tests with the container and as systemd is not installed inside, the app does not see that it is running and tells you to go for command line…
to make it work, I just modified the check_service_runner() fonction in the postprocess model so that it return true…
rather than referring to systemd, woudn’t it be more generic to just do something like ps -aux | grep service-runner instead if systemctl show service-runner | grep State ?
