Jump to content

Joe Reckamp

Seeq Team
  • Posts

    97
  • Joined

  • Last visited

  • Days Won

    29

Joe Reckamp last won the day on September 15

Joe Reckamp had the most liked content!

Personal Information

  • Company
    Seeq Corporation
  • Title
    Analytics Engineer
  • Level of Seeq User
    Seeq Advanced

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Joe Reckamp's Achievements

Contributor

Contributor (5/14)

  • Conversation Starter
  • Reacting Well
  • First Post
  • Collaborator Rare
  • Dedicated Rare

Recent Badges

65

Reputation

  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
×
×
  • Create New...