Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Hi, Peter. Thank you for adding the product idea here.Would love to hear more customers feedback on this feature, and how you would use it too. Best regards, Knut
Right, I understand. Then I assume you want to keep it at the last X days/hours/min. What are the typical time frames you look at? And how often would you expect the data to refresh?
Hi, Peter. Thank you for the product idea, and if I understand you correctly, you would like there to be a way to set the chart to automatically update with new values as new values come in?I will change this post to a product idea and you can track it's progress, and see how others engage with the idea and up vote it. Best regards, Knut Vidvei
Hi, @Maysaa Almatny It seems like you are trying to access Cognite Functions in a project where you don’t have access to Functions.Contact your Admin to get the right access, or go to a project where you have the right access level. Best regards, Knut Vidvei
Hi Ibrahim, thanks for highlighting this need.We definitely want to support use cases where near real-time access to data is necessary. As of today, this is best served through our Grafana connector which (although not streaming) supports 10sec updates, and we see is the preferred choice across our customers for an easy-to-use no-code tool for SMEs. We are also updating it currently to support FDM alongside Cognite's traditional data types.We are improving event-based support across the platform as well, starting with the MQTT data ingestion, which is in development now and planned for initial release this quarter (Q2 2023). We have plans to iteratively add more streaming support through workflow orchestration (i.e., running transformations on-event rather than schedule) as well this quarter. We do not currently have plans to support streaming in PowerBI; however, we do have support for Azure Stream Analytics on the roadmap for Q4 '23 - Q1 '24.It would be interesting to hear more about
Great feedback, Richard.And thank you for including the workflow examples of the engineers at Hess.Knut
Hello, @Stig Grafsrønningen Thank you for the request and the description of how you are working today. I understand that it is time consuming to manually keep track of the time zones and daylight savings, and vessels in different time zones.Please use the “upvote” functionality at the top of this thread, as we gauge the needs across features and users across customers. All the best, Knut J. Vidvei
Hi, @Brendan Buckbee . I’ve been able to reproduce on your exact data. The events you are looking for does not appear to have an end date, and with the current implementation it only shows events with both start and end date.If you zoom out in time to a date when you have with end dates lower in the table below you will see those events in the chart.We will create an update to Charts where events without end dates are still listed, and the start time will be visible in the graph as a line on the start time. And the events will be listed in the side panel. Best regards, Knut
New→Gathering Interest
Hi, @Stig Harald Gustavsen Thank you for a great suggestion. An it’s great that you describe your current workflow and what can be improved in it. If I may ask some clarifying questions so I understand what you mean when you say “ruler”.Is it the ability to add one or more markers that show the values at a specific point in time? Like in the concept sketch below? And he additional feature to have a “save to clipboard” button or similar so you dont have to write it down manually the values at each ruler? Best regards, Knut
Hi @ibrahim.alsyed abd @Brendan Buckbee .The vessel volume calculations are available now both as no-code in Charts and as Python in the Industrial Data Science Library. Under the category “Equipment” you have calculations for Spherical, Torispherical and Ellipsoidal in both horizontal and vertical orientation. See an example below with the geometry as constants and the tank level as input: Here is the link to the Python code and more detailed documentation: https://indsl.docs.cognite.com/equipment.html#vessels Looking forward to you feedback!Knut J. Vidvei
Hi, Brendan. You should be able to see all the events here connected to the pump, with the start and end time within the time frame you are looking at. Thank you for both the description and the screenshots. Those are very helpful. Let us try to reproduce it and find out what is happening here. Knut Vidvei
Hello @ibrahim.alsyed This has been reviewed and approved, and will become available after testing in staging. I'll give an update when it is available for users here in this thread. All the best Knut Vidvei
Thank you, Then I understand your concern and we'll take this into consideration. I appreciate the detailed explanation. Best regards, Knut Vidvei
Understand,.Thank you for the clarification!Knut
Hi, I’m still a bit uncertain what granularity you are referring to. Do you mean when viewing a time series and choosing different time windows?Today, it automatically shows raw data points when it’s less than 1000 datapoints. Above 1000 datapoints we show aggregates (in the same way as in API calls). If not, the UI will quickly become very sluggish and give a bad user experience.I like your idea of making this a user preference. This will come with the “danger” of creating a very slow experience, if we choose to include it. We’ll keep this thread open for comments from other users as well. Best regards, Knut
Yes,I believe I understand what you want to be the best experience.We’ll add this to our input to improve the stacking experience, and we really appreciate your input. Best regards, Knut
Hi, Anders.Thank you for the feedback. I understand that this feels like a restriction. And the reason it was implemented this way was to be convenient. How I understand your need you would like the stacked button to stack up your time series in the chart, and then not “lock” the axes. You would prefer this to stack them each time you press the button. FYI @Magdalena Rut Best regards, Knut
Hi, Anders!Thank you for this idea, and we do have a solution that helps you in this matter.If you have a chart with some calculations you don’t want to rebuild again every time, you can download the calculations to a (json) file, and store it as a template on your computer. These files can also be shared with your co-workers.Here is a video showing downloading a template in one chart: And adding them again in a new chart using this button, and adding the template (json) file: We also have concrete ideas to be able to do this inside the application, as you describe. What are some examples of calculation graphs that you would like to templatize?Best regards, Knut
Hi, Irie.Thank you for following up this item. We have done more research across our users, and see that there are variations in how many significant digits that a user needs depending on the problem they are working with in Charts. We would like to make this a user preference. Since Cognite is working on implementing a user setting across Cognite Data Fusion, we have postponed this feature to make sure we are implementing a good solution for this. We apologize for this delay, and will get back to you when the timeline is clearer. Best regards, Knut Vidvei
Hi, Stig.Yes, I understand with existing Charts. And we will take that input as a product idea for arguments in the url. Very happy to see these type of requests as always. As for your second question, yes you can add as many ExternalIds as you want. Just use & as a separator, and you can easily build a dynamic url creator in a web app or similar. We even have examples of people building Cognite Functions that generate the url to the chart as a Metadata field with results of daily batch calculations. And the url is click able in the Data Explorer. Keep the ideas coming! Knut
Hi, Stig Harald. We have an option which is used to “Open in” from other applications or solutions. You embed the timeseries externalIds and start and end time in milliseconds. We dont have relative parameters as in your example, but the milliseconds can be easily calculated. timeserieExternalIds=stringstartTime=number // in milliseconds endTime=number // in milliseconds You can also add a chart name and it will allow you to create a new chart or add to existing Charts. Example urlhttps://cog-demo.fusion.cognite.com/lervik-industries/charts?cluster=api.cognitedata.com&timeserieExternalIds=LOR_ARENDAL_WELL_29_Well_TOTAL_GAS_PRODUCTION&startTime=1603289653055&endTime=1622038604539&chartName=Custom+chart+name
Thank you for the response. Would you please clarify if I understand ypu correctly. Is the issue that when you have multiple time series with multiple axes that are not aligned you get too many grid lines? Perhaps you could add a screenshot with an example?Best regards, Knut Vidvei
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.