I'm working on identifying the falling and rising edges of the VAL_23-KA-9101-M01:HSI.StatusMotorOn signal. For that and shifting the TS and rest the values, if I get -1 is a falling edge and for 1 it is a rising edge. For the first row it works fine: But I’m also getting a lot of values different than 1 or -1. Especially for more recent years. I guess that the problem is at the aggregating step, since I downloaded the data at a 1m frequency I get not int values for some records. Now, I was trying to download this TS at a 1s frequency, but I get a different number of records depending on the year. E.G. for 2014 I get 34 records for a 10 days time windows with a granularity 1m. If I do the same but for 2020 I get 1411, much more than for 2014, but still a tenth of the expected count. If I change the granularity to 1s, I still get the same number of records, but with more precision in the time stamp: Considering this, is there a recommended granularity to download the data and min
There are some signals that in the names or the description have the words: alarm, warning, or fault. E.G. There is this alarm signal, (in red ) that I’m comparing with one of the vibration signals. And the alarm seems to be on when the vibrations are close to 0 and the Compressor is off. I’m plotting the label as a combination of the name and the description, but the externalId of the alarm is: pi:160268In most cases that alarm is on when the compressor is off, except in this case, Where I do not see any problem with the vibration signal: There are these other two alarms, from the plots: one is on when the compressor is off and the other one when it is starting up. But I do not see any strange behavior in the signal when they occur. Besides the alarms, I’ve also looked into some of the fault signals but those seem to be on for very long times: Is there another way to use the alarm and fault signals to label anomalies or failures? I don’t know if using the vibration signals is the bes
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.
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
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
I was looking at trends in the Remote App web version, using the cursor to touch tags. The detail pane shows the tag name(s) and current value where the cursor x axis crosses. The issue is the tag names are cutoff and mostly unreadable, the tag value is showing almost 10 or more decimal places. I would like to see the whole tag name and 1 or 2 decimal places, or use the signficant digits from the PI Server in the first place.
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.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
