MarkCov

In the documentation for spy.pull, there's a section for Mixing Conditions with Signals.  If I'm using the totalized statistic, how do I either determine what time units SEEQ is sending the results back as, or specify them.

This post  implies that I would pass totalized("min") similar to how it asks for Rate("min"), but SEEQ doesn't like that, see error message below.

I ask because it gave me results with the time units of seconds in one particular test, but another later test gave me it in minutes.  I'm not clear what I did to change the results.

I was only able to deduce it by checking the value and knowing what answer to expect.

Thank you, John. Apologies for asking a question that's clearly covered in the help.  I was even on that page!  For some reason my eyes just kept scrolling past that part.

I've got it working now.  Looking forward to scaling up my tree.

I'm building an asset tree in SDL and I'm trying to import an ordered list of signals into multiple parents, one signal per parent.  

I've tried a couple variations on tree.insert and it doesn't seem to do what I want.

tree = spy.assets.Tree('My Tree')
tree.insert(children=['Area D','Area E','Area F'])
search_results = spy.search(query = {'Name': '/Area [D,E,F]_Compressor Power/'},
                            order_by = 'Name')
tree.insert(children= search_results,
                 friendly_name = 'Power',
                  parent = 'Area ?')
tree.visualize()

My Tree
|-- Area D
|   |-- Power   (is actually Area D_Compressor Power)
|-- Area E
|   |-- Power   (is actually Area D_Compressor Power)
|-- Area F
    |-- Power   (is actually Area D_Compressor Power)

This appears to do what I want, but each "Power" is actually the same tag.  I tried removing the friendly_name parameter next.

tree2 = spy.assets.Tree('My Tree')
tree2.insert(children=['Area D','Area E','Area F'])
search_results2 = spy.search(query = {'Name': '/Area [D,E,F]_Compressor Power/'},
                            order_by = 'Name')
tree2.insert(children= search_results2,
                 
                  parent = 'Area ?')
tree2.visualize()

My Tree
|-- Area D
|   |-- Area D_Compressor Power
|   |-- Area E_Compressor Power
|   |-- Area F_Compressor Power
|-- Area E
|   |-- Area D_Compressor Power
|   |-- Area E_Compressor Power
|   |-- Area F_Compressor Power
|-- Area F
    |-- Area D_Compressor Power
    |-- Area E_Compressor Power
    |-- Area F_Compressor Power

Now that's too many signals.  If I have an ordered list of signals that I pull from spy.search, how can I insert one per parent?

My goal is a tree that looks like the one below.  I'm hoping there's a method other than manual insertion or CSV import

My Tree
|-- Area D
|   |-- Area D_Compressor Power
|-- Area E
|   |-- Area E_Compressor Power
|-- Area F
    |-- Area F_Compressor Power

Thanks!

Maybe it's a bug y'all fixed since R62?

The resulting excel file has 5 capsules in the "Information" and "Capsule Summary" tabs, but the "Grid" tab only has three.

Hello,

We're running SEEQ R62 and I'm having trouble trying to export capsules to Excel.  The capsules that are fully contained within the time range export fine, but the capsules that overlap the beginning / end are not.  I didn't see any options in export that would enable doing this.

One of my capsules that I was particularly interested in exporting runs up to current time so there is no end to the capsule.  See screenshot below, the capsule starting on Feb 22nd and "ends off screen" is the one I'm interested in.  When I go to Tools -> Import/Export ->Export to Excel that capsule starting on Feb 22nd is missing from the sample table grid.

Is there an export option I'm missing?  Or do I need to take some extra steps to close off that capsule so it will end at "now" so I can export it?  If so, do you have recommendations on how to do that?

I'm doing all this so that I can apply more complex formatting to the various plotted capsules.  I like how the Capsule Time view has added options for color, but if I dump the values into Excel I have a lot more control over how the graph is displayed.