Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. HI Thorsten, Thankyou very much, these functions are great solutions to my questions (and more...)
  3. One more comment on the post above: The within() function is creating additional samples at the beginning and the end of the capsule. These additional sample have an effect on the calculations performed in the histogram. To avoid this you can use the remove() and inverse() function to remove parts of the data when the condition is not met: In contrast to within() the remove() function will interpolate values if the distance between samples is less than the Maximum Interpolation setting of the signal. To avoid this when using remove you can combine the signal that the remove function creates with a signal that adds an "invalid" value at the beginning of each capsule so that the interpolation cannot be calculated: $invalidsAtCapsuleStart = $condition.removeLongerThan(1wk).tosamples($c -> sample($c.startkey(), SCALAR.INVALID), 1s) $signal.remove($condition.inverse()).combineWith($invalidsAtCapsuleStart) You can see the different behaviours of the three described methods in the screenshot:
  4. Hi VpJ, If you build it out using any of the solutions mentioned above, it is relatively easy to make it available in all workbenches.
  5. Thank you for the quick response, Joe! Will try making asset trees through the datalab so that it's accessible globally!
  6. Hi VpJ, Currently, asset groups are only available in a single workbench. You can see some differences between asset groups and asset trees (including that workbook/global scoping) here: https://seeq.atlassian.net/wiki/spaces/KB/pages/1590165555/Asset+Groups#Asset-Trees-vs.-Asset-Groups
  7. Can these asset groups be accessed by different work-benches? I spent quite a bit of time creating asset groups manually in a workbench only to later realize it wasn't accessible from other work-benches. Is it possible to make that available globally? Thank you!
  8. Hi SBC, applying the the within() function to your signal will result in a new signal that only keeps those parts of the signal where the condition is met. The filtered signal can then be used for the histogram. Regards, Thorsten
  9. Last week
  10. I have a continuous time signal (say T) and a capsule defined by value search (eg. simple capsule Y>120) where Y is another signal. I want to get the histogram of only the values of T that satisfy the the capsule condition, i.e., Get hist(T) from data pulled for all capsules where (Y(t)>120)
  11. Thanks Joanna! The idea of a new Organizer Topic each week had not occurred to me but may work pretty well. The other thing I tried was to make a seeq data tag for comments and just insert a data table with the comment but I can't format the font or text size.
  12. Hi Jessica, I would recommend opening your file in Notepad or some sort of text editor. From the error message, it looks like the columns in the file may be semi-colon separated (;) instead of comma separated (,). If that's the case, you'll want to change the "Column delimiter" option in the Import CSV and try again.
  13. Hi all, I keep receiving the "error" message above for the csv file I'm trying to import. The csv file is really simple, one column for the date and the 2nd column for the signal, each one with its unique name (as you can see below). Could you help me on that?
  14. Seeq's grouping functionality is helpful when you want to align multiple conditions and signals, but a signal (or set of signals) only applies to a subset of the conditions. Grouping a signal with a condition will only display that signal during the grouped condition. For example, here I have two temperature signals and a condition for each signal. I have used Profile Search to identify the profile for each signal I would like to compare. When I use Chain View or Capsule Time, the default will cause both signals to show up during each capsule. In this Chain View, the information of Reactor Temperature 1 is not relevant during the Profile Reactor 3 condition and vice versa: In order to view only the relevant signal information, I can use the grouping functionality in Chain View and Capsule Time to compare the relevant signals during each condition: 1) Select grouping in the toolbar. 2) Navigate to the grouping icon next to the condition in the details pane and select the signal that corresponds to the condition. Select multiple signals, if necessary. I can also view this in Capsule Time. As an additional option, I can overlay both signals using the One Lane and One Axis selections in the tool bar:
  15. yeah just shoot me an email with workbench link in which you had the worksheet.
  16. If I accidentally deleted a Worksheet (send it to Trash), is there any way SeeQ internal support can help to recover it ?
  17. Thanks Thorsten. We are currently using R56, but good to know this is fixed.
  18. Hello John, beginning in R57 you can adjust the number of characters to be displayed. https://seeq.atlassian.net/wiki/spaces/KB/pages/2344943627/What+s+New+in+R57#Customizable-formatting-for-string-labels-on-the-y-axis Regards, Thorsten
  19. Hi, I have a String signal that is having its label truncated on the y-axis. Is there any way to widen the area for these labels to avoid this? In case this doesn't make sense, hopefully this image will help: Thanks.
  20. Earlier
  21. Hi Matthias, There are a few ways you could display the average of each of these columns in the manner you describe. The first option is to calculate the average of the columns per year and display them in a separate scorecard with only one row. Then bring these two tables together in an organizer topic for the final display. Below is an example of what this could look like (using days instead of months and a week instead of a year): Tip: By inserting the table as interactive (in versions R54+) the table will render more clearly and the columns will line up. Another option is to create a condition for years and then combine this yearly condition with your monthly condition using the combineWith() formula function. This will create a condition with both the monthly capsules used for your averages, and a yearly capsule. By using this condition in your scorecard metric, you will get a row for each month, as well as a row for the year. A few things to note with this approach. First, the row for the year will appear at the top of your table instead of at the bottom because it is ordered on capsule start time, not capsule end time. In fact, you may want to delay your monthly condition by 1 second to ensure that the yearly condition shows as the first row. Second, the average result you will see for the year will be an average of all the samples in the input signal over the course of the year, instead of an average of the monthly averages. Below is an example of what this would look like (again with days instead of months and a week instead of a year): Thanks, Emily
  22. Hi Surendra, This post also works in reverse by simply defining the $reset period to when you want the sawtooth to reset:
  23. How do I convert a continuously increasing signal to saw-tooth signal?
  24. Hello everybody, I have the following question: I am building an organizer topic, where I display averages per months of different phases of this year: I did this with the scorecard metric and it worked very well. However, I would like to display the average of each of these columns (phases) of the complete year in the last row below Dez.22. How can I do that? Ofc. I know how to calculate the average of the phases (columns) per year but how to display them the way I described above. Any Ideas? Thank you very much. Regards Matthias
  25. Hi Jesse. Thanks for this input. While text boxes cannot yet be tied to date ranges in Organizer, our team has been thinking about ways to improve the process of entering and discovering comments around data. What some of our customers do in this scenario is have an Organizer Topic for each week, and they can navigate to a Topic representing a week in the past when they want to see what comments they had entered alongside the data. Some users duplicate that report each new week and clear out comments that may not be applicable when entering in new comments, and step the date ranges to now. This would be my recommendation for the time being. Another route you could explore is Annotations in Workbench. They have a date/time context and can appear on the trend as a little chat bubble, but the information added there is not yet available in Organizer. We hope to bring the concepts of Annotations in Workbench and Comments entered in Organizer together some time in the future. We might reach out for more feedback from you on these ideas.
  26. I write a weekly unit report (currently using excel) I want to use Seeq for this report but one functionality I need is to be able to save the comments I put in and look back at them. Basically in 3 years form now I want to be able to enter a date into Seeq and pull up my old report even with the comments I made back then. Is this possible?
  27. You cannot use spy.search result in the move function
  1. Load more activity
  • Create New...