> 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/w7-february-23.md).

# W7 February 23 ✓

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

## Agenda

* **During Lunch**
  * **Techpoint Xplore Program** (<https://youtu.be/nDRxF7g1VGU>)
  * **Indy Modern Apprenticeship** (<https://youtu.be/4GF1o0jLYWw>)
* **Recognize Perfect Attendance**
* **Explain Upcoming Incentives**&#x20;
  * *Data Analytics*
    * Complete First Two Coursera Courses by [March 8](/industry-connect-2024/founding-cohort/google-data-analytics-pacing.md) :shirt:
    * Complete the Full Google Data Analytics Cert and Capstone by [July 12](/industry-connect-2024/founding-cohort/google-data-analytics-pacing.md) :computer:
  * *Robotics*
    * Pass Cobot Programming Level 1 Challenge and Quiz by March 8 :shirt:
    * Complete the Full LaunchBoard Cobot  Certification by July 12 :gift:
* **Computer Checkout Policies**
* :star: **Sign Up / Apply** :star:
  * [**https://indymodernapprenticeship.com/**](https://indymodernapprenticeship.com/)
  * [**https://www.techpointyouth.org/xplore/**](https://www.techpointyouth.org/xplore/)

### Data Analytics

We will focus on Coursera today by discussing strategies and making progress.

* Notes and preparing for challenges (quizzes).
* Use [**these summaries**](https://docs.idew.org/gda-cohort-1/a801YJyWh1IWZBYOdSXN/course-1-lead-ins/c1-week-1) for first two courses if you would like.
* Completing the challenges — "open book" and retries.
* Set short sprint goals.&#x20;
* :star: **Get the first module (week 1) complete to build momentum.** :star:

***

### **Robotics**

See the Robotics tab for today's challenge.
{% endtab %}

{% tab title="Robotics" %}

## Adapting a Flow with a Vacuum Gripper Loop

{% embed url="<https://youtu.be/GiREqNC8rZ4>" %}

### Demos

* Quick demo of the [vacuum gripper attachment](https://onrobot.com/en/products/vgc10). It can be controlled much like the [finger gripper](https://onrobot.com/en/products/rg2-gripper).
* Demo of the flow that individually picks tiles placed in a row and drops each in a cup.
* Demo of how to modify the flow to adapt to different positions of the cup and tiles.

### Screen Images for Reference

<div data-full-width="false"><figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FbZbvTmFU1xjUdKNFgP9T%2Fimage.png?alt=media&amp;token=1c47f1f2-20b2-45d6-bc22-c320d5cd5559" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FkFLAm3JQKgjT9HpnU2MX%2Fimage.png?alt=media&amp;token=10a96289-349e-441d-916d-7568f412688a" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FFnLi6TA0RYEzY3s12zl6%2Fimage.png?alt=media&amp;token=be4e299b-3c76-42f0-8e11-4a056d68a382" alt="" width="188"><figcaption></figcaption></figure></div>

<figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FwLKTKJ7GVCIeQEzRFux1%2Fimage.png?alt=media&amp;token=2301c906-5922-4a41-9920-889e748c4be6" alt="" width="375"><figcaption></figcaption></figure>

<div><figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FGLOWmuvt7uLxcw9RuMOX%2Fimage.png?alt=media&amp;token=43ecb26a-29da-4202-a47d-83b33daa83a8" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FkkZQQg9DMDQP2ebvJS85%2Fimage.png?alt=media&amp;token=93311e75-351d-4c19-b53f-186257a7d4f8" alt="" width="375"><figcaption></figcaption></figure></div>

### Challenge

In this challenge we will use a programmed loop to place objects in a container. Your challenge will be to adapt the program to changing conditions.

1. Modify the *"hover" point node* to a position above the first tile in the row.
2. Modify the *set point node* that increments the position in each cycle of the loop.
3. Modify the *point node* to a position above the cup.&#x20;
4. Play the flow to test your modifications.
5. Edit as needed.
   {% endtab %}

{% tab title="Tabled" %}

## Spreadsheets: Summary Tables with Functions&#x20;

### Exercise

In this exercise we will create and format two tables which will provide summary statistics for the movie data. This will build off of the Google sheet of movie data we created in the [last exercise](/industry-connect-2024/founding-cohort/weekly-sessions/w5-february-9.md).

<figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FkHJfCN2rYyQ3RTGb5YQM%2FScreenshot%202024-02-20%20at%2010.12.25%E2%80%AFAM.png?alt=media&amp;token=bfc9ec78-7158-4290-8fda-1be678b9a058" alt=""><figcaption></figcaption></figure>

#### Review Last Exercise

1. Open your spreadsheet from the last exercise and review we accomplished.
2. Continue to use your spreadsheet for this exercise. If you missed the last exercise and need to jump into this one, use this link below and make a copy of the template spreadsheet. :link: [Spreadsheet 3 Exercise](https://docs.google.com/spreadsheets/d/1SVIZ-A47YmnUR9SWjXxJ7uMzvoPnTU4ED5cnDLFagJw/edit?usp=sharing)

#### Create a Summary Table of Statistics for All Movies

1. Before you begin, make sure your graphs from the previous exercises are NOT in columns K-Q. If they are obstructing any of the those columns, move them over to the right past column Q.
2. Starting in column `K5`, build the 2 table structures below:
   * The top table will contain the statistics for all movies. Add the Title in cell `K5` - **Table 1: Summary Statistics for All Movies**.
   * The bottom table contains the statistics for only Drama and Action movies. Add the Title in cell `K12` - **Table 2: Summary Statistics for each Movie Genre**.
   * Highlight the table headers in `K6:P6` and `K13:P13` and fill the cells in light blue

<figure><img src="https://1625728016-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk2eSlWeIIlewSK7TTGHl%2Fuploads%2FGxDx9AkPIdWbX3cydGoK%2FScreenshot%202024-01-29%20at%203.43.39%E2%80%AFPM.png?alt=media&amp;token=9c6a3b45-686c-4b25-a250-084f0c18bfec" alt=""><figcaption></figcaption></figure>

3. Now let's start filling in the table with the statistics for *All Movies*:

   * In field `M7` calculate the *Average (all data)* for `budget` using the formula: `=average(E:E)`
   * In field `M8` calculate the *Average (no 0's)* for `budget` using the formula: `=averageif(E:E, ">0")`
   * In field `M9` calculate the *Min (no 0's)* for `budget` using the formula: `=minifs(E:E, E:E, ">0")`
   * In field `M10` calculate the *Max* for `budget` using the formula: `=max(E:E)`
   * Highlight and copy the cells (**Edit > Copy**) of all the calculations you just generated for `budget(M7:M10)`
   * Paste the formulas in the `Revenue`, `Runtime`, and `Profit` columns by highlighting cells `N7-P10` and pasting (**Edit > Paste**). Change the columns in the formulas to match the column in the table header. So for example you would change `=average(E:E)` to `=average(I:I)` for `Profit`.

   Observe the difference between the Average (all data) and Average (no 0's) values. Why do we remove the 0's from the averages and minimum values? Which do you think is more accurate? Why?<br>
4. Now let's fill in the Table 2 for movie genres *Drama* and *Action*:
   * In field `M14` calculate the *Average (no 0's)*  `budget` for *Drama* movies only using the formula: `=averageifs(E:E, E:E, ">0", H:H, "*Drama*")`.
   * Can you do the same calculation for *Action* movies only in cell `M15`? \
     **Hint**: Copy the formula first.\
     \
     Where have you seen  this before? It should be familiar because we did this in week 3's assignment!
   * Now complete Table 2 by copying and pasting the formulas to the other cells and changing the column references to reflect the table headers. \
     **Hint**: For `revenue` change `E:E` which references the `budget` column to `F:F`.
   * **CHALLENGE**: Can you create the same summary statistics for the genres *Comedy* and *Thriller*?

:heavy\_check\_mark: <mark style="color:red;">**Individual Deliverable: TBD.**</mark>

***

### Review the [Pacing with the Coursera coursework](/industry-connect-2024/founding-cohort/google-data-analytics-pacing.md)

{% 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/w7-february-23.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.