Loader and fsm execution

The loader is provided help the user create a single launcher of many FSMs sharing resources. All the configuration options are available via convenient methods. It takes care of instantiating the classes for loggers, timers, and shared inputs and all the instances of the user defined FSM as required.

Warning

When upgrading from version 2 to 3 of the library, loader becomes a class. Update your code from this:

from smlib import loader
loader.load(myfsm, args)
loader.start()

to this:

from smlib import loader
l = loader()
l.load(myfsm, args)
l.start()

loader class reference

class loader

Create an instance of the loader class.

setVerbosity(level)
Parameters:

level (int or string) – The verbosity level: all the messages with lower or equal level are printed. Accepted parameters are: [0, 1, 2, 3] or, equivalently, [“error”, “warning”, “info”,”debug”].

The available verbosity levels are:

  • Error: these messages are always printed, and contain critical information on failures.

  • Warning: these messages are printed only when the verbosity level is 1 or higher.

  • Info: these messages are printed only when the verbosity level is 2 or higher

  • Debug: these messages are printed only when the verbosity level is 3 or higher. They contain a lot of detailed information useful while debugging applications.

logToFile(path, prefix)
Parameters:

  • path – The path of a directory where to store all the logs. Can be both relative or absolute.

  • prefix (string) – A prefix for log file names, to identify all the logs belonging to this executable.

While logging to file, a file will be created for each FSM loaded, plus one more for all the information on the main thread. If this function is called, the logger will be instantiated from fsmFileLogger instead of the default one (fsmLogger).

setIoMap(ioMapPath)
Parameters:

ioMapPath (string) – The path of a file defining a map for the inputs. See mappedIOs.

load(myFsmClass, name, *args, **kwargs)
Parameters:

  • myFsmClass – The definition of a FSM.

  • name (string) – The unique name of this FSM instance.

  • args – The custom arguments to be passed to the FSM constructor.

  • kwargs – The optional keyword arguments to be passed to the FSM constructor.

This function is used to load multiple FSM in this executable. The first parameter is the FSM class, not one of its instances. In fact, the loader will create the instance, adding the required optional arguments to the constructor. Then an arbitrary number of parameters can be passed, as required by each different FSM constructor.

start()

This is usually the last function to be called: it starts the execution of all the loaded FSMs and suspends the main thread, waiting for a signal.

The supported signals are:

  • SIGINT (Ctrl-C): Terminate the execution of all the FSMs.

  • SIGUSR1: Print a report of all the inputs connections.

In this way each FSM is executed in a separate thread until the kill signal is received.

Example

from smlib import loader
from myfsm import myfsm

l = loader()

## -------------------
# logger options
## -------------------
l.setVerbosity("debug")  ##use only this if you want to print log to shell
l.logToFile("mypath", "daemon")  ##use also this if you want to print to file

## -------------------
# inputs options
## -------------------
l.setIoMap("pathToMapFile")  #this will set the map file path

## -------------------
# load each fsm
## -------------------
l.load(myfsm, "fsm1", "ciao", "come", "va?")
l.load(myfsm, "fsm2", "ciao")

## -------------------
# start execution
## -------------------
l.start()

How to run the application

All the parameters are specified via the loader, so you can easily run the application with python. For example, if the example above is saved on a file named myDaemon.py, you can execute it with:

python myDaemon.py

and it can be stopped by the Ctrl-C key combination or (on linux) with:

pkill -SIGINT -f myDaemon.py

If you want to print a report on the connected inputs, during execution run:

pkill -SIGUSR1 -f myDaemon.py

and check logs for the output. This will not affect FSM execution.