Jump to content

Joe Reckamp

Seeq Team
  • Posts

    97
  • Joined

  • Last visited

  • Days Won

    29

Everything posted by Joe Reckamp

  1. Hi Pat, Can you try making the spy.search line include all properties so that hopefully it brings in the maximum duration for you: RampCond_Tags = spy.search({'Name': '*_RampCond'}, all_properties=True)
  2. Hi Pat, Did you spy.push the dataframe back to Seeq after the Data Lab screenshots you show here? You set the Archived value in Data Lab, but it doesn't actually occur in Seeq until you push that metadata back to Seeq. So you'll want to add a line of spy.push(metadata=RampCond_Tags)
  3. Here's a quick example of setting the width to 5 for all signals on the display for a single worksheet:
  4. Hi Surendra, You could modify the widths programmatically in Seeq Data Lab by looping through each worksheet and changing the display items dataframe in python, but no way currently to do this across multiple worksheets directly in Workbench.
  5. You just would change the third value to a 1: spy.jobs.schedule('0 0 1 ? * 6#1 *')
  6. Hi Ruby, This should work instead: spy.jobs.schedule('0 0 0 ? * 6#1 *')
  7. Ultimately this depends on the network setup and what your IT department may allow. If Data Lab is hosted in your company's network, it may be possible to get access to and directly pull from SharePoint, but would likely need to be provided access through the firewalls by IT to get there. If Data Lab is hosted as SaaS, it is unlikely that an IT department would allow that access into their network.
  8. If you check out the docstring for the spy.push function, you should see an option for "replace". If you set the values to np.NaN and then push with the replace around the timestamps you want to remove, you should be able to remove that data in those time frames.
  9. Generally, pushing to a different workbook should result in two separate items only scoped to that particular workbook. Therefore, what you are seeing may have been a bug. If you want the same signal in both workbooks, you can push with workbook=None to make the item globally scoped instead.
  10. Hi Surendra, Please see the following Knowledge Base article on how to set up email notifications: https://seeq.atlassian.net/wiki/spaces/KB/pages/2242740294/Data+Lab+Notifications
  11. This is the example of the formulas I sent you: It starts with the Signal in blue. I then calculated the timesince value in orange, followed by the hourly average for each day in dark blue. The spot it seems you are running into issues is with the green signal, which is calculating the latest hourly average. Notice that all the other signals stop at "now" about halfway through the screen. In order to see the result of the latest hourly average, you'll have to set your display range to view the remainder of the day beyond "now" as I have done above as that signal will only appear in the future remaining part of the day. From there, the last formula I mentioned creates the red extrapolation at the top that continues the trend using that hourly average. The formula that you suggested: $hourlyaverage.aggregate( average(), periods(1hour, 5min), endKey()) is not going to do the same function as the green signal above and should not be used as a replacement.
  12. You can use the formula you suggested for latest hourly average, but that would not provide the same result. In that case, you would be averaging an hour worth of data rather than the entire last day of data. In addition, the result would need to extend until the end of the day instead of stopping at the latest data point.
  13. Does the display range go out into the future? That formula would only have data beyond the "now" timestamp.
  14. Hi Surendra, 1. You will need to first create a capsule that represents the sawtooth schedule. If it's always 6am reset time, I would recommend creating a periodic condition that is daily, running from 6am to 6am in your time zone. From there, a formula function known as timesince exists to calculate the amount of time that has passed in each capsule. Therefore, you could do the following formula to get the time passed since the last capsule (ending the calculation at "now"): timesince($condition, 1h).within(past()) From there, you can simply do the calculation you want to get hourly average: $signal/$timesince 2. First, you can get the latest hourly average value and project that forward until the end of the day using: $hourlyaverage.aggregate(endvalue(true), $condition, durationkey()).within(not past()) Then you can multiply that by the hours in the day to get the extrapolation going forward: $LatestHourlyAverage * timesince($condition, 1h) 3. For this, you'll probably want to use the Reference Profile tool: https://seeq.atlassian.net/wiki/spaces/KB/pages/142770210/Reference+Profile
  15. 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
  16. 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.
  17. Hi Surendra, This post also works in reverse by simply defining the $reset period to when you want the sawtooth to reset:
  18. Hi Surendra, Please check out the Data Lab Notifications Knowledge Base article on how to send out email notifications: https://seeq.atlassian.net/wiki/spaces/KB/pages/2242740294/Data+Lab+Notifications
  19. Hi Adewale, When you create an OData endpoint for PowerBI, there are two separate links for the Capsule Summary Table and the Sample Table. The Sample Table is equivalent to the "Grid" tab on the Excel export.
  20. Hi patjdixon, For the aggregate function, you currently are using “startkey”, which means that the value of the aggregate is placed at the start time stamp of the capsule you are aggregating over. Instead, if you switch that to “durationkey”, it will place the value as a constant straight line across the length of the capsule.
  21. Hi SBC, Interactive content has been added in recent releases. Tables were the first item introduced in R54 so that option will only be available on R54 or later. Other visuals (e.g. XY Plot, Trend) have been released in even more recent versions. In terms of what interactivity does, please check out the What's New in R55 page located here, which describes the interactivity of tables and table-based charts: https://seeq.atlassian.net/wiki/spaces/KB/pages/2218229877/What+s+New+in+R55#Trend-lines,-pie-charts-and-bar-graphs,-oh-my! Regards, Joe
  22. Hi SBC, All users that access Organizer must also login to authenticate to Seeq so they must have an account. Regards, Joe
  23. Hi John, As you mention, currently the metrics cannot be moved around the table like the statistics can be. However, the order of the metrics is based on the lane of the metric in the details pane. If you change the order of those lanes and refresh/change time range, the order of the metrics will change.
  24. Hi Filip, In the Release Notes, you should see that it mentions this change (see excerpt below). You should still be able to click on the links to move to the previous views even in edit mode. Workbench Analysis Editor Changes In R55.0.0, the journal will no longer be able to be toggled from edit mode to view mode. When the analysis is in edit mode the journal will always be in edit mode, and when the analysis is in view only mode the journal will be in view only mode.
×
×
  • Create New...