Book Image

KNIME Essentials

By : Gábor Bakos
Book Image

KNIME Essentials

By: Gábor Bakos

Overview of this book

KNIME is an open source data analytics, reporting, and integration platform, which allows you to analyze a small or large amount of data without having to reach out to programming languages like R. "KNIME Essentials" teaches you all you need to know to start processing your first data sets using KNIME. It covers topics like installation, data processing, and data visualization including the KNIME reporting features. Data processing forms a fundamental part of KNIME, and KNIME Essentials ensures that you are fully comfortable with this aspect of KNIME before showing you how to visualize this data and generate reports. "KNIME Essentials" guides you through the process of the installation of KNIME through to the generation of reports based on data. The main parts between these two phases are the data processing and the visualization. The KNIME variants of data analysis concepts are introduced, and after the configuration and installation description comes the data processing which has many options to convert or extend it. Visualization makes it easier to get an overview for parts of the data, while reporting offers a way to summarize them in a nice way.
Table of Contents (11 chapters)

Using workflow variables


The following video link demonstrates how you can create a workflow with parameters set for the workflow but still used in the report generation:

http://youtu.be/RHvVuHsvf0U

Basically, the recipe is to create a workflow variable with a name and type you want to use in the report. This workflow variable will appear in the report designer as a report parameter.

If you use the workflow variable in the workflow in a way that can change the data passed to the report generating engine (in the example, the data was filtered according its value), you can use this variable as a report parameter and generate the report with the updated data.

In the example, it is also demonstrated that you can pass another table to the report generator, and use that information to set the domain of the possible values for that report parameter. This might be an unexpected way to parameterize your execution, but it is a quite powerful option. You can check this behavior using our example workflow...