This is the terminology list I wish I’d had to start with. A page with content something like this should be prominently linked in a post stickied where beginners will find it. Input - An incoming datasource. Each input has an associated “node” identifier and a “key” sub-identifier. You can’t really do anything with an input except hang a single chain of “feed” processes off it. Node - a grouping identifier for your inputs or feeds. Key - a sub-identifier for items within each Node. Feed - A series of operations (process nodes) to execute against all new data coming to an Input. Each “process” (step) in a feed seems to get stored in a time-series database, usually either phpfina or phpfiwa. Most of the interesting ones require php-redis, which doesn’t exist on all hosts. Virtual Feed - A feed which hangs off any other process node.

Thanks, I’ve added this to this FAQ

[image] thundersun: Feed - A series of operations (process nodes) to execute against all new data coming to an Input. Each “process” (step) in a feed seems to get stored in a time-series database, usually either phpfina or phpfiwa.Most of the interesting ones require php-redis, which doesn’t exist on all hosts. This sounds a little more like a description for input processing than a feed. Input process list (or input processing) A list of processes performed sequentially on each input value as it is received on that input. Process A function that can be attached to the process list of an input to change the value or to save the value to a feed. Feed A place where data is recorded, usually as a time series of datapoints. I’m all for chipping in to a fuller list of terms and abbreviations used though out the project. A simple “glossary” could serve as a helpful first step into understanding OEM and emoncms, adding some links to further info and you have the beginnings of a documentation “index”, not to be confused with a “contents” list which has been discussed elsewhere

Thanks @thundersun @pb66 I have added a terminology note to the emoncms github, alongside other improvements to the user documentation section: emoncms/emoncms/blob/master/readme.md # Emoncms [![Build Status](https://travis-ci.org/emoncms/emoncms.svg?branch=master)](https://travis-ci.org/emoncms/emoncms) [![Codacy Badge](https://api.codacy.com/project/badge/Grade/fd6200361ad442a49651f1ebe10542c4)](https://www.codacy.com/app/emoncms/emoncms?utm_source=github.com&utm_medium=referral&utm_content=emoncms/emoncms&utm_campaign=Badge_Grade) Emoncms is an open-source web application for processing, logging and visualising energy, temperature and other environmental data and is part of the [OpenEnergyMonitor project](http://openenergymonitor.org). ![Emoncms](docs/files/emoncms_graphic.png) ## Requirements - PHP (tested with 7.0.30) - MYSQL or MariaDB (tested with 15.1) - Apache (tested with 2.4.25) - Redis* (tested with 3.2.6) _*Redis is recommended because it reduces the number of disk writes and therefore prolongs disk life (noticeably on SD cards e.g. RaspberryPi). Some input-processors also require redis and fail silently if redis is not installed. Some environments such as shared hosting or as far as we have tried windows servers don't support redis hence why emoncms has a fall back mode that allows core operation without redis._ ## Using Emoncms This file has been truncated. show original

Community

OpenEnergyMonitor

OpenEnergyMonitor Community

EmonCMS terminology list

Getting Started FAQ