Adam Georgeson

When running a Data Lab project.... sometimes the push command writes to an existing signal and sometimes the push command creates a new signal (with the same name as the existing signal) and writes to that. The result is duplicates. It wastes time to stay organized by switching broken formulas and deleting the duplicates. Is there a way to force the push command only to write to existing signals, never to create new signals?

Thanks Teddy!

DFW Airport right now has 8 mph winds, per the National Weather Service website. NOAA connector in Seeq is reporting 14 m/s winds, which is 30 mph. That is not the case. I live right by DFW Airport and confirm it is not a storm. Doing a deeper analysis, the wind speed reported by NOAA connector is always 3.6x faster than wind speed reported elsewhere. Are the units for wind speed wrong? Did someone put m/s when it should be km/h? (0.001 m/km * 3600 s/h = 3.6)

Lindsey, The 7 days forecast is looking like that today. The Connector has low reliability which Seeq has said is due to the NOAA's servers. It is possible the NOAA's servers were not providing forecast data when I investigated. For portions of last month, the NOAA's servers did not even provide current data.

Temperature would be most helpful

Morgan, Is there a way to obtain NOAA Weather Forecasts as part of this Connector? We used this Connector to obtain historical weather data and then used Prediction to build equations relating weather data and certain performance metrics. We would like to obtain the upcoming weather forecast and apply the equations to it, thus anticipating what the performance metrics will be, a few days into the future. Excel can manually be used for this purpose, of course, but like most things it would be great to have a solution in Seeq

Lindsey, We upgraded not long ago. The new layout is much better than the old one on mobile. We do have a lot of Iphone users so yes, please update me on CRAB-20100 Thanks, Adam

Thanks Lindsey. Would you mind posting a few screenshots of the new homepage on a mobile device? I'm interested to see how the new layout affects mobile navigation before we upgrade.

Makes sense, thanks!

What benefit does .valueSearch() provide? I've typically written it this way and see no difference of outcome $conditionclosed = $OP.validValues().isLessThanOrEqualTo(0) $flowsignal.splice(0.toSignal(),$conditionclosed)

The screenshot for the new home page shows categories "Home" "My Items" "All" "Shared" and "Trash" Has "Public" been eliminated? https://support.seeq.com/space/KB/736035141/What's+New+in+R22.0.48

You're right Allison. It happened again. Chrome at 80% zoom. Monitor 1366x768. Looks good at 67% zoom and 90%. At the 70% and 80% zoom, the "i" merges into an "I" Not a great font for the variable names. The word "Variables" is written at the top in a different font. At the same zoom level, the "i" is clearly visible.

Why is Seeq R21.0.44.0 preventing me from using a lower case "i" in a formula's variable name? For example, variable name $bi is automatically changed to variable name $bI (upper case). I don't prefer to use the upper case "I" since it looks similar to the number 1, and to the lower case "l"

Need to clarify the difference between a "calendar month" (per an actual calendar) and a "normalized month" (365/12) Example screenshots: 1. I set the time window to 1 month, starting January 1st at 12:00am. It ends January 31st at 10:00am. This is a "normalized month" 2. I do an integral over months, UTC-12:00. It resets on the 1st of each month at 6:00am. This is a "calendar month". 3. If I manually type in "6 months," it is 1/1/2020 12:01am to 7/1/2020 1:01pm. However if I manually type in "26 weeks" it is automatically converted by Seeq to "6 months" and it is 1/1/2020 12:01am to 7/1/2020 1:01am. The length of the 6 months is different! Here's the real kicker: I manually type in 6 weeks and it is automatically converted by Seeq to "6 months". I then manually type in "6 months". The time scale doesn't change, it still ends at 7/1/2020 1:01am. So the length of the "6 months" that I entered depends on the previous state of the chart. Same thing happens for a year. One year is 365 days (or 366 days for a leap year). It is not 52 weeks * 7 days = 364 days. It would greatly help us to get these time frames resolved. Contracts and accounting run on true calendar months and years. 3 How long is six months.pdf 1 Normalized Month.pdf 2 Calendar Month.pdf

When opening a Dashboard in View-Only mode: please default to "comments pane minimized" rather than "comments pane open". This is particularly important on mobile where screen real estate is limited. Otherwise, as you can see in my phone screenshot, the comments pane takes up the whole screen and the actual content is hidden to the right.