> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/industry-connect-2024/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/industry-connect-2024/founding-cohort/weekly-sessions/w8-march-1.md).

# W8 March 1 ✓

{% tabs %}
{% tab title="Main" %}

## Agenda

* **During Lunch:** Custom GPT Demo with Audio :speaking\_head:
* **Review Progress** on Coursera and Summer Opportunities
* **Breakouts into Data Analytics and Robotics** :rocket:
  {% endtab %}

{% tab title="Data Analytics" %}

## SQL: SELECT, FROM, ORDER BY

### Exercise

Today we will use Structured Query Language (SQL) to pull data from a movie database. SQL, like spreadsheets, is an indispensable tool for data analysts.

**Demo:** `SELECT`, `FROM`, `ORDER BY`, `ASC`, `DESC`

#### Practice: Constructing SQL Statements

Construct the appropriate SQL statements to satisfy each of the following requests. Use the [LaunchBoard SQL Lab](https://sql.launchboard.app/) to test your statements.

1. List all movies in the `movies` table. Include all columns.
2. List all movies, but include only `title` and `year` columns.
3. List all movies by ascending `year`. Include all columns.
4. List all movies by descending `vote_count`. Include only `title` and `vote_count` columns.

:heavy\_check\_mark: <mark style="color:red;">**Demonstrate your executed SQL statements with an instructor.**</mark>

### **Continue work on the Data Analytics Certificate on Coursera (**[Pacing](/industry-connect-2024/founding-cohort/google-data-analytics-pacing.md))

{% endtab %}

{% tab title="Robotics" %}

## Using Cobot Vision to Recognize and Pick Objects

<figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2Fk1yyNkbK7Vy0fDPfl7V0%2Fimage.png?alt=media&amp;token=2d16d642-0e4a-4234-b104-c4c77fe41499" alt="" width="250"><figcaption></figcaption></figure>

### Demo

We will demonstrate how to define a ***visual servoing job*** to a cobot flow to recognize the position of objects. This will create a ***base*** that we can use to then pick up the object and move to another location. We will also use a ***subflow*** to separate functions.

***

### Challenge

Work in small groups to modify the demo flow.

* **Create a new&#x20;*****visual servoing job*****&#x20;that picks up a different object.**\
  This will require learning the new pattern to match
* **Update the&#x20;*****point node*****&#x20;to position the cobot vacuum gripper above the object.**
* **If needed, adjust the&#x20;*****move node*****&#x20;to grip the object.**
* **Test your updated flow.**

***

:heavy\_check\_mark: <mark style="color:red;">**Demonstrate your solution.**</mark>
{% endtab %}
{% endtabs %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.launchboard.app/industry-connect-2024/founding-cohort/weekly-sessions/w8-march-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.