This proposal has been approved and the Eclipse TRACE4CPS project has been created.
Visit the project page for the latest information and development.

Eclipse TRACE4CPS

Friday, January 22, 2021 - 04:22 by Bas Huijbrechts
This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.
Parent Project
Proposal State
Created
Background

Eclipse TRACE4CPS (TRACE) originates from a concept tool which was initially designed in 2012 in a research collaboration between ASML, the ESI (Embedded Systems Innovation) joint research center of TNO (the Netherlands Organisation for Applied Scientific Research), and the TU/e (Eindhoven University of Technology). TRACE is used to visualize execution traces of cyber-physical systems (e.g., wafer scanners, professional printers, pick-and-place equipment and medical scanners), which typically contain information from multiple domains (software, mechatronics, etcetera). During the following years, research projects with ESI, the TU/e and Océ Technologies B.V. (now Canon Production Printing) have extended TRACE with analysis capabilities that are tailored to performance engineering. TRACE is currently used by several industrial manufacturing equipment companies such as Canon Production Printing, ASML, and Nexperia.

Scope

Eclipse TRACE4CPS (TRACE) maintains and evolves a visualization and analysis tool for the performance engineering of cyber-physical systems. It has a strong focus on industrial applicability. The tool supports visualization of concepts such as events, claims on resources, dependencies, and continuous signals. TRACE typically works on a single execution trace, or, in the very specific case of distance analysis, on a handful of execution traces. Extensions for visualization and analysis of multiple/many execution traces are out of scope.

Description

There are many reasons why a system’s behavior over time is difficult to understand or, worse, confusing – even when the system is performing as designed. An example is a situation in which many concurrent activities share resources. Unforeseen interactions may arise due to the specific timing of the activities. Moreover, if the timing of the activities changes (e.g. due to an upgrade to the computational platform), the interactions may also change, which could result in significantly different behavior. Insight into the hows and whys of a system’s behavior over time is of paramount importance for making effective (design) choices and trade-offs in all phases of the system lifecycle, from the design of a new system to the maintenance of an old legacy system. The TRACE tool can help with this.

The TRACE tool works with execution traces. These capture (a single) system behavior over time. An execution trace contains time-stamped and user-annotated data for claims on resources, events and continuous signals. This execution trace concept is generic, which makes TRACE widely applicable:

  • All levels of abstraction: the TRACE format can capture all levels of abstraction, from low-level embedded activities to system-level activities.
  • Domain-independent: the TRACE format is domain-independent but nevertheless has the means to be tailored to a specific domain via the user-defined attributes.
  • Source-independent: TRACE input can be created from any source, e.g. from the log files of legacy systems or from a discrete-event simulation model.

The TRACE tool provides insights into the system dynamics of all kinds of systems through the visualization and analysis of execution traces. The TRACE Gantt chart view offers coloring, grouping and filtering options. This visualization alone is already very powerful and can bring quick insights into the system dynamics. TRACE also provides several analysis methods, which sets it apart from other Gantt-chart visualization tools.

  • Critical-path analysis can be used to detect activities and resources that are bottlenecks for performance.
  • Distance analysis can be used to compare execution traces with respect to structure, e.g. to check a model trace against an implementation trace.
  • Runtime verification provides a means to formally specify and verify the properties of execution traces using temporal logic. It is useful for expressing and checking performance properties, e.g., “the processing latency is at most 50 ms.”
  • Latency, throughput and work-in-progress analysis provides built-in methods to derive these properties from an execution trace.
  • Behavioral analysis can be used to visualize repetitive / cyclic patterns that often are present in systems such as image-processing pipelines and manufacturing machines.
  • Resource-usage analysis can quickly give insights into the details of the resource usage.

The TRACE tool and the underlying concepts are relatively easy to learn and the TRACE input is easy to use.

Why Here?

The objective is, together with diverse parties interested in the use of TRACE, to create a larger community around TRACE. The aim is to make it easier for all parties to contribute together to the development of the tooling in an open setting, and to enable managed open source support by third parties. TRACE should not be longer seen as research tool but should receive more industrial focus. Therefore, TNO believes the Eclipse Foundation is an excellent fit for the future of TRACE.

Project Scheduling

The initial contribution is scheduled for 2021 Q3. It will include a fully compiling and tested version of the TRACE product. The first release as an Eclipse project is foreseen for 2021 Q4.

Future Work

There is a backlog of short-term feature extensions and improvements which is currently (planned to be) worked on:

  • UI improvements, including support for improved navigation in the visualization, bookmarking mechanism, improved rendering of certain parts of the visualization, re-running checks from the ETL result view.
  • Improvements of existing features, including improved validation in the temporal-logic DSL, providing the temporal implicant for non-satisfied properties, inclusion mechanism in the temporal-logic DSL to improve re-use.
  • Bug-fixes for reported issues.

We foresee that, in the future, TRACE will be extended to support more diverse industry application. By extending to more diverse domains, the tool will become more generically applicable and thereby more appealing. To build up a growing user community, TRACE will be applied in projects together with industrial partners, closely aligning with addressing their daily development challenges. Furthermore, knowledge institute ESI (TNO) will actively disseminate the tool and its benefits with the high-tech systems eco-system.

Finally, the project aims to realize a support platform for the tool addressing bug-fixing, regular builds following the Eclipse release cycle, manuals and instruction material. The grand idea is that this platform will enable commercial users (industry, high-tech companies) to commission proprietary software partners (e.g. software houses) to support, extend and improve TRACE.

Committers
Mentors
Interested Parties

We expect to start a TRACE user community based on following interested companies and organizations:

  • TNO;
  • ASML;
  • Canon Production Printing;
  • TU/e;
  • Nexperia;
  • Altran;
  • ICT;
  • Additive Industries;
  • Cordis Automation.
Initial Contribution

The initial contribution of the TRACE project is the full TRACE source, including source code (Java) and documentation, more specifically:

  • Core library with TRACE domain model, I/O functionality, and analysis algorithms;
  • Visualization library with generic visualization functionality;
  • UI plugin that provides the TRACE-Eclipse UI (editors and views);
  • Plugins for the temporal-logic specification DSL (based on Xtext);
  • Library with command-line tooling for temporal-logic checking;
  • Several plugins with unit tests;
  • TRACE user documentation (included in the UI plugin as Eclipse on-line help contribution);
  • Plugin with extensions of the JFreeChart visualization library;
  • Several examples.

TNO is the copyright holder of the code and the other artifacts.

TRACE requires the following other toolsets, to be downloaded separately from their original download location:

  • Eclipse Modeling Framework (EMF);
  • Xtext;
  • Xtend.

We used the Eclipse Dash License Tool (github.com/eclipse/dash-licenses) to analyze the dependencies of TRACE. The list below excludes all approved dependencies and only lists the dependencies that require investigation.

ASM - 3-Clause BSD License

  • maven/mavencentral/org.ow2.asm/asm-tree/7.2, unknown, restricted, none
  • maven/mavencentral/org.ow2.asm/asm/7.2, unknown, restricted, none
  • maven/mavencentral/org.ow2.asm/asm-commons/7.2, unknown, restricted, none
  • maven/mavencentral/org.ow2.asm/asm-analysis/7.2, unknown, restricted, none

JFreeChart - LGPL

  • p2/orbit/p2.eclipse-plugin/org.jfree.jfreechart.swt/1.0.19.202011261203, unknown, restricted, none
  • p2/orbit/p2.eclipse-plugin/org.jfree.jfreechart/1.0.19.202011261203, unknown, restricted, none
  • p2/orbit/p2.eclipse-feature/org.jfree.jfreechart.feature/1.0.19.202011261203, unknown, restricted, none
  • p2/orbit/p2.eclipse-plugin/org.jfree.jcommon/1.0.19.202011261203, unknown, restricted, none

Miscellaneous:

  • maven/mavencentral/com.google.code.findbugs/jsr305/3.0.2, LGPL-2.0, restricted, emo_ip_team
  • maven/mavencentral/com.google.guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava, unknown, restricted, none
  • maven/mavencentral/org.codehaus.mojo/animal-sniffer-annotations/1.17, unknown, restricted, none
  • maven/mavencentral/com.google.errorprone/error_prone_annotations/2.2.0, unknown, restricted, none
  • maven/mavencentral/org.checkerframework/checker-qual/2.5.2, unknown, restricted, none

The community around developing the code consists of:

  • scientific programmers working for ESI (TNO);
  • software programmers working for Altran (software house);
  • students and PhD candidates from the TU/e.
Source Repository Type