Thorsten Vogt

Hello,

creating comments in View-Only mode seems not to be possible, the "New Comment" button is missing in the Comments area.

Hello,

this topic came up during a customer training. The presentation of the individual assets in the Treemap view looks strange at first glance. In the screenshot, the assets "Area J" and "Area K" are displayed as long rectangles, although all assets have the same number of sub-elements:

When the size of the display pane is changed it looks better:

According to your KB entry the size of the rectangles is determined by its number of assets and may be changed by the API. Is there an example for this?

Regards,

Thorsten

In case of the reference profile I don't have a use case.But I would like to know if this uncertainty resulting in using now() is a problem for predicting a signal into the future? In my case I have a signal that depends on two other signals. In Seeq example data I created a demo that creates a model of the "Temperature" signal by using "Wet Bulb" and "Relative Humidity". To get predicted values for the forecast of  5 days I take the values of the humidity for the last 24hs and repeat it the next 5 days. I then use the values of Wet Bulb from the last 24hs and repeat them also over the next 5 days with rising them by 1°C per day:

The prediction for the temperature signal is build upon this two signals:

Hello Ben,

does "uncertain" in this context mean the values could change because of getting the data dynamically by using now()?

If I change the code from my example above without using now() and changing to a fixed capsule the visualization changes (2. lane):

Is there any way to get around this issue?

Regards,

Thorsten

Hi Ruben,

maybe you can use a rolling training window in the following way. For this demo I want to create a reference profile for the Compressor Power when the stage of the compressor is != OFF. The rolling training window shall be the last 7 days as you said.

1. Add the data to the display pane

2. Create a new signal for the compressor power, that takes the data of the last 7 days and moves this data to some fixed date range (e.g. 01/01/2019):

3. Repeat this step for compressor stage signal:

4. Create a condition that identifies the times when the compressor is on during training window:

Your display now should look like this when you move to 01/01/2019:

5. Create a condition that identifies the times when the compressor is on (NOT during training). We will use this for the reference profile to be applied to:

6. Create the reference profile based on the training window. I had to shorten the training window by two minutes at end due to an error message ( Training window for reference table must be certain at 'captureReferenceSlice',).

The result looks like this:

To simulate a change of time you can modify the formulas for the training data like this  You can see that the shape of the profile changes:

I am not sure if this workaround may cause problems in some situations, as it seems the error message in step 6 is thrown because there is no sample at the end of the training window. Therefore this solutions has to be adjusted to your needs.

Regards,

Thorsten

Hi Ruben,

yes, you can export the data to Excel from your workbench analysis:

Include Summary Data adds a worksheet to the Excel file containing statistics of your signals and capsules, Include Signal Samples adds a worksheet with the samples for each signal in the display range.

More information can be found here: https://seeq12.atlassian.net/wiki/spaces/KB/pages/494436371/Export+Data+to+Excel+File

Regards,

Thorsten

Hello Adam,

Seeq provides a tool for this scenario. With "Directory Watch" you can monitor custom directories for new files. As soon as a file is copied to a monitored directory the data is processed and imported to Seeq. You should contact Seeq support about that tool.

Best regards,

Thorsten

Hello, if the tags are not present in an asset structure (e.g. AF framework), I would try to use the Tree File Connector to create my own asset structure in Seeq. This makes it easy to switch between the individual elements without having to create a new analysis or duplicate existing ones.

https://seeq12.atlassian.net/wiki/spaces/KB/pages/350978134/Building+Asset+Trees+using+Tree+File+Connector

Hi,

I have a strange issue when aggregating data in a histogram. I am counting the number of samples for a signal and aggregate by first using "Year" and the using "Day of the Week" as the aggregation type:

This gives me the following histogram with a count of 246 samples for monday in 2012:

But these data should belong to sunday. I set up another histogram using the following condition as the second aggregation type:

The result now looks like this (which is correct):

This is for the other days as well. Is there any way to get around this issue? Installed Seeq version is R21.0.40.01-v201812312325

Regards,

Thorsten

Hi Lindsey,

I tried solving this by using the externalCalculation-Function of Seeq. I created a python script and modified the functions initialize and compute as followed:

    def initialize(self):
        self.sum = 0
        pass

    def compute(self, key, samples_for_key):
        self.sum += samples_for_key[0]
        if self.sum < 0:
          self.sum = 0
        return key, self.sum

The script is called by using externalCalculation('CusumP.py:NUMERIC:M6CBe8UAQoSN',$d)

However, when I am using this script I get the following error message on execution:

Error getting data: Client data source exception: Error processing external calculation request: Script CusumP.py:NUMERIC:M6CBe8UAQoSN is not respecting the requirement to do only calculations that operate on data at a single key. Script needs to be changed. Exception: java.lang.RuntimeException at 'externalCalculation', line=1, column=1. To retry, use the button to the right.

Why is this behaviour blocked by Seeq?

Thorsten