Jump to content

James DeMarco

Seeq Team
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by James DeMarco

  1. Hi David, It seems the handling of enum signals involves providing some buffer from the edges of the lane, which is not configurable. I was able to produce a fairly good alignment by using the Customize > Axis settings in the Details panel to turn of Auto scaling of the numeric signal and set the min and max to -90 and 450, resp.: This will work as long as all enum values appear in the time range of interest but will produce misalignment if a proper subset of these is in the time range, because for enums the axis is only labeled with the values of those enums that are found in the time range. Hopefully this works for your visualization; if not, it may make sense to file a support ticket for a feature request to have more control over the visualization of enumerated data.
  2. If you modify your wind_dir variable to $wind_dir = group( capsule(0, 22.5).setProperty('Value', 'ENUM{{0|N}}'), capsule(22.5, 67.5).setProperty('Value', 'ENUM{{1|NE}}'), capsule(67.5, 112.5).setProperty('Value', 'ENUM{{2|E}}'), capsule(112.5, 158.5).setProperty('Value', 'ENUM{{3|SE}}'), capsule(158.5, 202.5).setProperty('Value', 'ENUM{{4|S}}'), capsule(202.5, 247.5).setProperty('Value', 'ENUM{{5|SW}}'), capsule(247.5, 292.5).setProperty('Value', 'ENUM{{6|W}}'), capsule(292.5, 337.5).setProperty('Value', 'ENUM{{7|NW}}'), capsule(337.5, 360).setProperty('Value', 'ENUM{{8|N}}') ) You will get an ordered Y axis: This is how Seeq handles enum Signal values from other systems - it has some limitations, but it seems like it should work well for your use case.
  3. Glad to help, Pat. This is expected behavior for Datafiles that are locally scoped. If you're ok with making the Datafile and associated Signals globally scoped, you can open the Item Properties for the Datafile and set the scope to global; note that setting the scope to global cannot be undone. Once the Datafile is global, workbook duplication should work as expected.
  4. Was this a duplicated analysis? If so, I suspect that the IDs you're seeing are associated to items that couldn't be cloned successfully. If this is the case, you should find a journal in the (new) first worksheet of the cloned analysis, which will list items that couldn't be cloned successfully for some reason. Often this has to do with permissions. These items are created in the cloned analysis, but they're assigned placeholder IDs that are serial numbers preceded by an appropriate number of 0s to make a GUID. If that's what happened here, examining the journal on the first worksheet of the analysis should provide clues as to what needs to be fixed before a subsequent attempt at duplication.
×
×
  • Create New...