Join the discussions about products powered by Cognite Data Fusion. Click the + CREATE TOPIC button in the menu bar to start the conversation.
Recently active
Hi! After switching from experimental to cognite-sdk 3.9.0 I struggle with deployment. 1: Using handleIf i try to deploy using the handle, then the requirements are not handled. The function deploys, but failing at the imports. How should requiremenents be used when deploying like this? Imports are inside handle():def handle(client, data, secrets): from googleapiclient.discovery import build from googleapiclient.errors import HttpErrorCreating function like this:cognite_client.functions.create( name=function_name, external_id=function_ext_id, function_handle=handle)2 - Using a folder.Then I get this error: [WinError 267] The directory name is invalid: 'C:\\Users\\hknap\\AppData\\Local\\Temp\\tmptzkywbdl\\function.zip'If I debug, the folder “tmptzkywbdl” is created, so there should be no permission issues. 3- Manually uploading the zip fileThis works (including the requirements.txt), thanks for adding this possibility. It is just a little extra hassle ;) would prefer if
Hi!Almost three years ago we made a feature request regarding search. Specifically we want to:Have support for paging. Do grouping on metadata-fields. Define which fields yields relevance to the search-results. Inclusive search-terms using AND instead of OR.I do understand that satisfying the search-requirements of all your users is a daunting task, but perhaps it would be easier to let us do the job instead? I believe it would be very beneficial if we were able to access ElasticSearch directly in some manner.And please keep in mind that the data itself defines relevancy. No two customers are alike and therefore a good generic solution likely doesn’t exist. @Knut Vidvei @Andreea Pastinaru
Schedule a personalized demo to learn how Cognite Data Fusion™ generates fast, scalable value from your data, enabling better decision making about maintenance, production and safety.In the demo, we will:Understand your priorities, initiatives and challenges that you are looking to solve Introduce Cognite and share examples of use cases we deliver for our customers today Identify areas where Cognite Data Fusion can help your organizationRequest demo with one of our product experts
If you are curious on how to get the most out of your Cognite Data Fusion subscription, you have come to the right place. This is part of a series of posts where we share some of our experience from working with customers in their journey towards an Industrial DataOps organization. We want to share lessons learned, mistakes made, good practices observed, and observations of pitfalls and risks. This is not the absolute truth, but hopefully a way to spark good discussions around an inherently complex topic!To quickly introduce ourselves, we are @Arjo Oosten, Digital Transformation Leader, winter sport addict and passionate about driving hands-on digital growth strategies and value based decision making, and @Karolina Luna, Solution Architect, cat lover, and passionate about the lifecycle perspective of everything (like solutions and data products). To learn more about Cognite Data Fusion, we recommend this post.Planning your solutions and Industrial DataOps with Cognite Data FusionTo be
Hello Charts Early Adopter Community,I know it’s been a bit quiet in this group lately, but rest assured, the team and I have been hard at work. We have just released several new features and fixes to production. You can scroll down to read about each of them in detail.Please do leave comments below with questions and feedback!What’s coming next?We’re in the middle of our development cycle in preparation for the next major release of Cognite Data Fusion in December 2022. There are the two major features our team is working on that you can look forward to having available:Moving Charts (charts.cogniteapp.com) into Cognite Data Fusion (fusion.cognite.com) We’ve received plenty of feedback that our product experience can and need to be more tightly integrated and we’ve heard you loud and clear. As you all know, Charts is currently available on charts.cogniteapp.com, which is separate from Cognite Data Fusion (fusion.cognite.com). Despite starting out on its standalone URL, Charts has alw
In many cases in diagrams including P&ID, there are shortcuts to represent tags, for instance:F2014A/B/C for F2014A , F2014B and F2014C.The contextualization engine in some cases will pick one of the 3 or none at all.Is there a way for the engine to detect trailing slashes and match to multiple tags?See example of patterns below:Example of patterns
I am listing time series for a given asset, and get a lot of results. I need to filter based on the time series external ID, but the only option is by using the “external_id_prefix” argument to the list function. So I build up the prefix left to right. Somewhere in the external id is a parameter that I do not care about, and after comes a new parameter that I want a particular value of. Concrete example of external IDs:IAA_Miros_Weather_Data_WIA_008IAA_Miros_Weather_Data_WIB_008IAA_Miros_Weather_Data_WIC_008IAA_Miros_Weather_Data_WID_008IAA_Miros_Weather_Data_WIE_008I am interested in only getting time series with external IDs that contain “_WI” and that end with “008”. Is there a way to list time series with a wildcard? Something like this:client.time_series.list( asset_ids=[my_asset_id], limit=None, external_id_prefix="IAA_Miros_Weather_Data_WI*_008", partitions=4)I could of course obtain the relevant time series by filtering after the fact. Something like thisresult = cl
Are you a Power BI user who wants to gain hands-on experience with Cognite Data Fusion? Are you curious to learn how to handle a large set of CDF data in Power BI?The Cognite Power BI connector lets you use a CDF project as a data source in Power BI Desktop to query, transform and visualize data, share insights across your organization, or embed dashboards in your app or website. When working with the Cognite Power BI connector, it is important to know how to refresh the data and apply best practices to deliver accurate results. The newest course from Cognite Academy introduces you to implementing incremental refresh - one of the best practices to get the most out of the Cognite Power BI connector. Our instructors first explain when to use incremental refresh, then show you how to set it up in four steps. In this course, the training data comes from the Open Industrial Data (OID) project, a live stream of industrial data from the Valhall oil platform.After completing this course, you’l
Hi Team I am trying to deploy the code into new env facing issue because of black --check.
HiI have retrieved timeseries from an asset in PowerBi. That asset is linked through a relationship column to a group of assets. However the asset and the group it belongs to are connected trough 4 steps:groupwanted <- belongsTo - subgroup<- belongsTo - type of group <- connectsTo - group of a few timeseries assets<- belongsTo - timeseries asset Im wondering how to link the relationships in power bi, and how to orient to the right place.
Hi Team I am trying to deploy ML Model into the AIR but Creating Env Variable Step is showing the error. Also attached image consisting issue details. Regards.
On serveral occations we have encountered limitations in metadata key length, most frequently when flattening JSON-formatted strings from our event stream data source systems. When the source system presents nested structure of as many as 4 levels we frequently encounter metadata keys that require more than 128 bytes. Up to now we have “solved” the issue by abbreviating the metadatakeys at the price of higher maintenance cost of the code and more importantly, that end-users get the perception that we have transformed the data or even dont understand what it represents. We now consider moving towards a solution where we simply put the entire JSON-formatted string into one single metadata value field, and leave to front-end teams and end users to flatten the structure. We have a similar issue with max number of metadata keys for timesseries (16). Question 1) Could you please suggest other, better options for handling these metadata limitations? Question 2) Will templates come to the resc
Hi everyone, I tried to upload my own dataset(time-series data) into CDF, but I always get error: Request with id 87b235ea-78dd-963a-b343-ff58a0ee084d to https://westeurope-1.cognitedata.com/api/v1/projects/learn/timeseries/data failed with status 400: Timestamp is too high, must be at most 2556143999999 which is 31-12-2050 23:59:59 GMT.I followed with this link:https://learn.cognite.com/path/cognite-data-fusion-fundamentals/working-with-cdf-integrate. I created an assest, 3 time-series. What I want to do is to upload my data to the 3 time-series, and show the variation of my data in CDF. I change the time_stamp of my data into the format of 2022-02-10T17:00:00.000Z, I am not sure if this is necessary but when I preview my datapoints in RAW explorer and CDF automatically change the this format into for example, 164998440000, so I am wondering if this is why I have this error? I also want to ask what is the meaning of span in IFSDB.sensors? It means this time-series is 100 days? or 100
Screenshot for reference.
The curl command suggested here needs quotes around all JSON property names, needs to use " instead of ', and needs trailing commas removed before curl will stop reporting invalid JSON payload.
More details here: https://github.com/cognitedata/react-auth-wrapper/issues/15Perhaps it could be removed all together?
One thing that would make the finding of the correct data is to label the CDF resources better with labels. https://docs.cognite.com/dev/concepts/resource_types/labels In the contextualization pipeline could things be automatically labeled such as:Document type: P&ID, PDF(Process Flow Diagram), loop diagrams, datasheets, single line. that theses documents are either labeled from the metadata. document ID schema (regex will do it) or from classification algorithm the file, and then gives it a label to the file. that we can see from the label on the resource what it is.The same is for Asset: Is it a Junction box, Transmitter, Skid, Pump, Motor, valve etc etc. Time series: is it a physical measurement, is an inference / calculation / “soft-tag”, is a parameter (like the gain or integration time on PID controller) this could be determent by simple analyzing of the data-point behavior of the time series. cause now when we search for a time series often a time series of a parameter that
If you have lost access to your previous device, you can reach out to support@cognite.com and request to re-register for multi-factor authentication. You can also reach out to support here.
Morten Andreas Strøm / Ben Skal September 12, 2022 What makes Cognite unique? Why is partnering with Cognite the best investment of your time and resources?This is a 3 part series where @Morten and I answer these questions through an indepth look at how our product, Cognite Data Fusion, can help you use industrial data to ignite your digital roadmaps. The topics we discussing are: What is Cognite Data Fusion and why did we build it? (First post) Data modeling grounded in business impact (Previous post) The opportunity cost of custom building your industrial data platform (This post) In the first Why Cognite post, we discussed the data problem Cognite Data Fusion is built to address. The short answer, industrial companies need simple access to complex industrial data. The reason, most operations teams have many business opportunities, but are struggling to effectively use data to improve production. In the
I just finished the cognite academy examples on contextualization. I did notice on the PID contextualization example that there were quite a few errors in what seems potentially character recognition pipeline to identify tags in the PDF.The tutorial stated that “these were all good” and “we can accept all”. I suspect such a process would create missing or strange links in the contextualized dataset.Are these known issues?I lack a bit the understanding of the context for the importance of these mispredictions,but I thought to report them anyway just in case.Happy to support you on improving these if they are something that needs improvement.
When I try to access cdf tenant URL (https://slb.fusion.cognite.com/), I get this error.I have been trying to figure this out but nothing so far, kindly suggest where to get these permissions from.
<<URGENT>>Hi ,We are Unable to deploy Cognite Function. Below is the snippet for the same.Function ID : 269293733668660 @Philippe Bettler could you please prioritize this issue.
It would be really nice if we could control these log-messages in a more granular way:
Please add better documentation around the behavior of status code 422 for Create Time Series. Specifically, I’d like these questions answered:When multiple external ids are given and some are duplicate and some are not, will the time series that are not duplicates be inserted and will these created ids be returned in the response? Does this function similar to datapoints where create is actually create or update and the duplicates are updated with the data provided? If not, what is the recommended pattern for create or update of time series entities through the API?I am aware of advice here around “EAFP vs LBYL”, but I am in a case where 98% of the time the time series will not exist and I’d like to optimize for this case. Thanks!
This post is a hands-on introduction to the features supported in the Transformations Python SDK.Prerequisites Use Case 1: Triggering Transformations Step 1 - Create RAW Tables Step 2 - Uploading data to RAW using Postgres Gateway Step 3 - Create new SQL Transformations Step 4 - Trigger the transformation from Azure Data Factory Use Case 2: Orchestrating Transformations Step 1 - Create RAW Tables Step 2 - Create new SQL Transformations Step 3 - Orchestrate Transformations in sequence PrerequisitesKnowledge: Basic knowledge of Azure Functions and Azure Data Factory Basic knowledge of Cognite Data Fusion RAW and SQL Transformations Prior experience with Python, Postgres and SQL Required Datasets:Download and Unzip the attached hub.zip file, you should find the below structure Use Case 1 : asset-hierarchy.csv UseCase 2: OID-Asset-hirerachy.csv OID-Timeseries.csv OID-Datapoints.csv Use Case 1: Triggering TransformationsData is extracted from source systems and