Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
83 77 88 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
67 49 83 -
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 1 promise resolved, 5 needed for a score.
All types combined: 81 (likely 76 to 86, high confidence), from 87 claims: 79 factual claims, 8 predictions. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Rodney Brooks's claims
1 claim
| Verdict | Kind | Said | Claim | Topic |
|---|---|---|---|---|
| Delivered on time | Promise | 16 Dec 2014 | Starting in 2015, Rethink Robotics will provide APIs allowing developers to improve Baxter. Promise · 16 Dec 2014 | Their own work or organisation |
“Non, mais à partir de l’année prochaine, nous aurons des API qui permettront aux développeurs d’améliorer Baxter.”
Rodney Brooks, interviewee 16 December 2014 Interview de Rodney Brooks à Paris : Robots collaboratifs, Rethink Robotics et Baxter (Shy Robotics)
Starting in 2015, Rethink Robotics will provide APIs allowing developers to improve Baxter.
Delivered on time The record shows it happened or was so.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
Delivered means that during 2015 Rethink Robotics made available to developers or customers a programming interface, API or SDK through which third parties could program or extend Baxter's behaviour. An SDK or API that already existed and was still offered in 2015 also meets 'from next year'. Rethink's own announcement counts only if documentation or third-party use shows the interface was actually available. True: such an API/SDK was available in 2015. Mostly false: it became available only after 2015, or what was offered in 2015 was only an announcement or a closed beta without developer access. False: dated product documentation or reports show no developer API/SDK for Baxter existed during 2015, or that the plan was dropped.
Evidence
- Release of the new SDK 1.1.1 for the Baxter robot Generation Robots (blog) · 26 May 2015
“Rethink Robotics just released a new update of Baxter SDK: Baxter Research Robot SDK 1.1.1.”
- Repository Summary ROS Index (open-robotics index of ROS packages)
“1.1.0 (2015-1-2) - Updates baxter_interface to ROS Indigo”
- GitHub - RethinkRobotics/baxter: Baxter Research Robot SDK GitHub (repository owned by RethinkRobotics)
“The Baxter SDK provides a platform for development of custom applications for the Baxter Research Robot”
Reasoning
An independent robotics retailer reported on 2015-05-26 that Rethink Robotics had released Baxter Research Robot SDK 1.1.1 (E1). The ROS package index lists baxter_interface 1.1.0, dated 2015-1-2, updating it to ROS Indigo (E2). Rethink's public GitHub repository describes the SDK as a platform for building custom applications for Baxter (E3). Under the criteria, an SDK that existed and was still offered in 2015 counts as delivered, and this evidence shows developers could use one during 2015.
Cite this claim
Rodney Brooks, “Starting in 2015, Rethink Robotics will provide APIs allowing developers to improve Baxter.” (said 16 December 2014). Verdict: delivered on time. Reliability API, claim c_19025d9020a8, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_19025d9020a8
Claims without a verdict
Is a verdict here wrong, or do you speak for Rodney Brooks? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.