Sympathy for Data v1.2.2 available!


Sympathy for Data version 1.2 is a significant minor release for Sympathy for Data. It features several prominent new features, improved stability and more. It has however not been redesigned and with only a few small modifications, all existing nodes and flows should work as in 1.1.

Version 1.2.2 is a maintenance release in the 1.2 series. It improves on 1.2.1 with significant new reporting functionality, improved stability and improved performance.


Download Sympathy for Data built for Windows:


Changes Compared to version 1.2.1

  • New Features:
    • Added a new report type and associated nodes for generating, combining and writing reports to file. This is a major improvement in the ability to produce nice reports
    • Added locked subflows which provide better performance by executing without intermediate files. Subflows can not be configured or edited while they are locked
    • Added benchmarking support for workflows and the platform installation
    • Added support for a “_resources” folder in the library structure for containing rst documentation, svg icons, etc.
    • Added optional precompilation of python files in windows installer. This can greatly improve startup performance when Sympathy doesn’t have permission to write in the installation directory
  • New nodes:
    • Partition list Predicate: Similar to Filter list Predicate but producing two output lists
    • Match list length: Similar to Match Table Length but for lists
  • Node changes:
    • Time sync and Interpolate can now handle datetime bases. If an explicit time step is given in Interpolate and the origin time basis is of type datetime, the time step is assumed to be in seconds
    • Datasource(s): Filename completion and better handling of relative paths
  • API changes:
    • validate_parameters no longer has access to input data, making flow validation potentially faster. “Moved data validation to execute.”
  • Stability:
    • Fixed a severe bug which prevented Sympathy from starting under some circumstances.
    • Increased the number of retries before giving up on communicating with workers
    • Improved stability of config aggregation when data is missing
    • Improved loading of workflows allowing workflows, where some of the nodes in a config aggregation are missing, to still be loaded