> For the complete documentation index, see [llms.txt](https://sliu583.gitbook.io/blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sliu583.gitbook.io/blog/specific-work/seminar-and-talk/fall-21-reading-list/are-machine-learning-cloud-apis-used-correctly.md).

# Are Machine Learning Cloud APIs Used Correctly?

### Presentation 

* Machine learning provides effective solutions 
* Software development: problems --> bugs 
* ML cloud API
  * Function as a service 
  * Help incorporating learning solutions into software systems 
    * Require less domain knowledge 
    * No need to design and train neural networks 
* ML APIs raise unique challenges 
  * Performing cognitive tasks: how people ask questions greatly affect the result  
  * Largely defined by training data: properties might not be known by API users  
  * Numeric vector output: high-dim, tricky to interpret
  * Complicated accuracy - performance tradeoffs 
*  Corpus 
  * Google / Amazon ML cloud API 
  * 3 ML domains: vision, language, speech 
  * 18 months, size of 2,200 lines 
* Anti-pattern identification methodology
  * Manual examine
  * Design test cases 
  * Report bugs 
* Result 
  * Most applications: misuses! 
  * Pattern
    * Calling the wrong API 
      * Subtle semantics difference among cognitive tasks 
      * e.g. image classification, object detection. Which one to use? 
      * e.g. text-detection, document-text-detection 
      * Escape the traditional testing 
    * Misinterpreting outputs 
      * Numeric vector outputs are difficult to interpret 
    * Misuse of async APIs 
      * complicated accuracy-performance tradeoffs 
    * Necessarily high-resolution inputs 
      * higher resolution - performance degrades 
    * Many other misuses --> what types of impact (reduce functionality, degraded performance, increased cost) 
* Design checkers 
  * Three static analysis tools for three misuses 
  * API wrappers for four misuses 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sliu583.gitbook.io/blog/specific-work/seminar-and-talk/fall-21-reading-list/are-machine-learning-cloud-apis-used-correctly.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.