Was wondering if anyone has crossed upon this problem:
Using MSFT Cognitive Services Face API to persist Person Groups, Persons and Person Faces
Am sending an image to the Face-Identify API and receiving a candidate list that includes "phantom" personIds that are not persisted by me and are not listed in the person group used for identification.
When I run List Persons in a Person Group API I don't receive that personID.
Overall everything is working but for some images I get these invalid responses.
Any clue would be appreciated.
Hello from Microsoft Cognitive Service Face Team,
And really sorry for the inconvenience cause by our current training strategy. AFAIK, it is still computation/time cost to train a person group, that is why we make it as an asynchronous call and need training again after the person group is modified.
If you have any further problem, please feel free to update.
Related
I am working on a research project based on the six degrees of separation theory (based on the works of Stanley Milgram 1967 and later, Duncan Watts 2001). I just wanted to plot the connections of every user part of the study.
I wanted to show a users connections list, from LinkedIn. I read that there was something like a peoples API which could be used, but I think it is deprecated now. Is there any way of getting a users list of connections, even if we take the users permission?
I also read that there is something like a LinkedIn partners program, I cannot find much information about how I can apply for it.
I'm curious to see when accounts started following me on Twitter (and when I started following accounts). It'd be interesting to see my user activity related to the types of accounts I follow, as well as maps of my followers/followings over time + season.
I've tried getting followers and lookup users in the following manner:
followers <- get_followers("twitterhandlehere", n = 50)
followers_data <- lookup_users(followers$user_id)
Followers_data is a data frame with user info including profile picture, bio, and when the user's account was created, but no where in there does it indicate when the relationship started, as far as I can tell.
Nor does this function seem to indicate the date in which the follow/following started:
lookup_friendship("BarackObama", "MyUsername")
It appears the API didn't support this functionality in the past, and I understand I can stream this data in the future - but is there any way to salvage specificity in the past data?
No, this is not available in the API. You would have to have been regularly polling the friends and followers endpoints to record those changes. You cannot discover it from the API at a specific point in time, you'd have to make the record of follower list changes youself.
I work for a non-profit that needs to see how our fundraising efforts are going in 'real-time'.
We look at results in blocks of about a half hour - so we need to report on how we finished the last 24 hours or so and also where we're at in the current half-hour. We're accomplishing this through google analytics, as we have multiple fundraising streams all pointing to a common GA account.
I have tried using datastudio to report against the GA API, but that connector does not seem to refresh at a reliable rate - someitmes it'll pull fresh data within a minute, sometimes it can take twenty minutes to report on recent transactions. I believe the 'real-time' API could be used to get fresher GA data, but as far as I can tell, that will only report 'live' data, and not prior/historical data (say from four hours ago). Does anyone know what API I could use if any to pull all data historical through current datetime?
I apologize if this request is vague, but I'm just looking for a conceptual approach at this point to get the freshest data - preferably in one fell swoop (API call). There is more complexity post-data intake (I have to then compare it to goals we've set for each half-hour, amongst other nuances to the transacitons themselves), so i wanted to start with this fundamental piece/question.
Thanks!
Given the context provided, I believe that the API solution would not be feasible. Among other reasons:
The real time API only offers a limited amount of dimensions and metrics. For example, e-commerce data is not available.
https://ga-dev-tools.appspot.com/dimensions-metrics-explorer/
https://developers.google.com/analytics/devguides/reporting/realtime/dimsmets
The Standard intraday processing SLA for the Core Reporting API is < 24 hours for standard properties. The processing occurs on a best effort basis. Meaning that an hourly availability can occur from time to time but can not be guaranteed.
https://support.google.com/analytics/answer/7084038?hl=en
As an alternative approach to the API solution, you could consider the use of an App + Web property which would allow you to stream event data in real time to BigQuery. However, this solution has some cost implications and would introduce you to a new tracking paradigm.
https://developers.google.com/analytics/devguides/collection/app-web/tag-guide
https://support.google.com/firebase/answer/6318765?hl=en
https://www.simoahava.com/analytics/getting-started-with-google-analytics-app-web/
I'm using the Microsoft Face API to track people in front of a webcam by sending a screenshot from the camera to the API every second or so
If a particular person is in front of the camera for multiple API calls, the API should return the same faceId for that person in each response, but it is returning a new faceId for that person instead. This makes it impossible for me to know whether there is a new person in front of the camera, or a different person
This was not the case a couple of weeks ago, it's just something which has started happening recently
The parameters that I'm sending are...
returnFaceId:true,returnFaceLandmarks:false,returnFaceAttributes:age,gender
... the gender and age detection are working fine, it's just the faceId that I'm having problems with
Is there a limit to how many faceIds it'll assign per month or something? I can't find any reference to a limit in the documentation
here is Shuolin from Microsoft Cognitive Service Face Team. Referring to Face Detect API is provided (https://westus.dev.cognitive.microsoft.com/docs/services/563879b61984550e40cbbe8d/operations/563879b61984550f30395236), each Detect API call will return a unique FaceId (even same face is used in different call). For your situation, I suggest that you can use Identify API to recognize person (https://westus.dev.cognitive.microsoft.com/docs/services/563879b61984550e40cbbe8d/operations/563879b61984550f30395239).
I want to develop one robot using watson conversation, this robot can answer some frequently asked question about my application. Here is my thinking, every question has its own intent, and the answer will be returned by response. but I have over 50 questions, that means I need to define over 50 intents, but watson conversation limited 25 intents for one workspace. Does anyone have any idea about how to resolve it? Thanks.
There are two options for you
Purchase Standard plan ($0.0025 USD/API call)Includes upto Up to 2000 Intents.Check out more on pricing here
Link similar questions together and try to reduce the questions.For example, take two questions regarding Bank withdrawals and Bank deposits could be asked in one intent as Bank transaction and then put type of transactions as entities(dialogue box condition as entities).
And besides that limit, there is another one: max 1000 API queries/month. It if fine for a proof of concept or to development phase. If you intend to go to production, you should purchase a plan. https://www.ibm.com/watson/developercloud/conversation.html