Jump to content

Ruby Han

Members
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

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

Ruby Han's Achievements

Apprentice

Apprentice (3/14)

  • Collaborator Rare
  • One Month Later
  • Week One Done
  • First Post
  • Conversation Starter

Recent Badges

0

Reputation

  1. Thanks for the help! @Emilio Conde is working on this with me and modifying the expression you've provided and we're close to what I'm trying to get at! Thank you!
  2. I'm getting this error. Not sure if I'm implementing this correctly.
  3. Thanks for responding. I have not really tried your approach yet as I found a post that provided a solution that I was kind of looking for. This is the post URL: Replace Gaps in Data with an Average Value from Previous Time Frame - General Seeq Discussions - Seeq Community Website To summarize the post, it's basically imputing on the missing gaps with the average value for X time period which is essentially what I'm looking for. However, when I tried replicating the solution and modifying the 10 min in order to make it a dynamic parameter for $conditionForDataGaps.move(-10min,0min), I'm getting an error as the dynamic parameter is basically the capsule duration which is a variable signal type. $w - brown trend $capsuleDuration - yellow trend $gapCondition - pink capsules green trend is the signal I'm determining where $gapCondition is at. @Chris Orr recommended a transform for the move parameter but I'm not knowledgeable enough to implement that here. I hope this clarifies my problem. Thanks!
  4. Hello, I am wondering if there is a Seeq function to determine the last X days of valid data. For instance, in the last 7 days, 2 of those days are downtime or invalid data while 5 days are valid data. So hence, I would like to expand the reference window size to more than the set 7 days in order to include 7 days of actual valid data. Is there currently an out of the box function or a workaround? Thank you.
  5. I've archived the workbook and tried replicating what I did and recreated a pushed signal so not exactly the same as the previous example. It looks like it's working. I will send a support ticket if I see the same phenomena again.
  6. I do think there is a valid value at that timestamp for the first example. The second example's timestamp is the exact same as the first. I tried setting grid=None and it did work, but I still am a little baffled as to why the first example displays null values instead.
  7. Hello, I am seeing something off in the spy.pull output on the same dataset. The only difference is that my 'start' argument was set differently. I suspect something's going on in the spy.pull library?
  8. Hello, I was referencing the spy documentations and found this (I think it was in one of the spy.assets module). May I know what open source libraries Seeq is using to generate the tree visualization show below? Or was that made from scratch within Seeq? Thank you, Ruby Han
  9. I'm receiving an error for scheduling every 1st sunday of the month.
  10. Thank you for the quick response! To go one step further, how do I express "every 1st saturday of the month at 1am"?
  11. Hello, I am trying to express "every 1st saturday of the month" for spy.jobs.schedule(). Referenced site: https://www.freeformatter.com/cron-expression-generator-quartz.html based on helper doc string but gave me an error as shown below. Thanks in advance for the help! Ruby Han
×
×
  • Create New...