This section is used to configure the internal service engine in WeeWX. It is for advanced customization. Details on how to do this can be found in the section Customizing the service engine of the Customization Guide.
Internally, WeeWX consists of many services, each responsible for some aspect
of the program's functionality. After an event happens, such as the arrival of
a new LOOP packet, any interested service gets a chance to do some useful work
on the event. For example, a service might manipulate the packet, print it
out, store it in a database, etc. This section controls which services are
loaded and in what order they get their opportunity to do that work. Before
WeeWX v2.6, this section held one, long, option called
held the names of all the services that should be run. Since then, this list
has been broken down into smaller lists.
Service lists are run in the order given below.
|Perform any actions before the main loop is run.
|Augment data, before it is processed.
|Process, filter, and massage the data.
|Add derived types to the data stream.
|Record the data in a database.
|Upload processed data to an external RESTful service.
|Run any reports.
For reference, here is the standard set of services that are run with the default distribution.
If you're the type who likes to clean out your car trunk after every use, then you may also be the type who wants to pare this down to the bare minimum. However, this will only make a slight difference in execution speed and memory use.
These services get called before any others. They are typically used to
prepare the console. For example, the service
which is responsible for making sure the console's clock is up-to-date, is a
member of this group.
Augment data before processing. Typically, this means adding fields to a LOOP packet or archive record.
Services in this group tend to process any incoming data. They typically do things like quality control, or unit conversion, or sensor calibration.
These are services that use the
WeeWX XTypes system to augment
the data. Typically, they calculate derived variables such as
Once data have been processed, services in this group archive them.
RESTful services, such as the Weather Underground, or CWOP, are in this group. They need processed data that have been archived, hence they are run after the preceeding groups.
The various reporting services run in this group, including the standard reporting engine.