# CL for practicing estimation

**URL:** <https://cl.desmos.com/t/cl-for-practicing-estimation/2733>\
**Category:** Questions\
**Tags:** aggregate\
**Created:** [February 22, 2021, 6:52pm UTC](https://cl.desmos.com/t/cl-for-practicing-estimation/2733 "2021-02-22T18:52:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ms\_Peterson](https://yyz1.discourse-cdn.com/flex031/user_avatar/cl.desmos.com/ms_peterson/32/1740_2.png) [@Ms\_Peterson](https://cl.desmos.com/u/Ms_Peterson)\
**Post date:** [February 22, 2021, 6:52pm UTC](https://cl.desmos.com/t/cl-for-practicing-estimation/2733/1 "2021-02-22T18:52:48Z")

</div>

I want to create a screen in which the students estimate a too low, too high, and a just right.

I would like to be able to provide them feedback when their estimate for low is too high, for high is too low, and when their just right is within reason.

I currently have a separate math input for each category. too high for ‘low’ might tell a student that \>500 is too high. too low for ‘high’ might tell a student that \<250 is too low. just right would want the student to enter a value between 350 and 400 without giving away an exact answer.

> **[MOwWM: ES2.L5 ~ Value of Timber • Activity by Mrs. Peterson](https://classroom.amplify.com/activity/6033efdb9ae92e41eba64483)**
>
> Students will use the volume of the trees they found in the previous lesson to approximate the number of board feet in each tree. They will then use this information to predict the value of the timber on the plot they surveyed in lesson...

second screen.

Thank you in advance,  
~K

---

<div class="post-metadata">

**Author:** ![Daniel\_Grubbs](https://yyz1.discourse-cdn.com/flex031/user_avatar/cl.desmos.com/daniel_grubbs/32/719_2.png) [@Daniel\_Grubbs](https://cl.desmos.com/u/Daniel_Grubbs)\
**Post date:** [February 22, 2021, 7:47pm UTC](https://cl.desmos.com/t/cl-for-practicing-estimation/2733/2 "2021-02-22T19:47:48Z")

</div>

You could use a note that is hidden when the input is greater than 500:  
`hidden: yourInputNameHere.numericValue>500`

I personally don’t think this is necessary. Instead, maybe aggregate class estimates in a graph on the next screen. And allow them to go back and change their mind. Or wait to aggregate guesses later before the answer is revealed. I feel like there’s value in seeing their mistaken perceptions.

---

<div class="post-metadata">

**Author:** ![Ms\_Peterson](https://yyz1.discourse-cdn.com/flex031/user_avatar/cl.desmos.com/ms_peterson/32/1740_2.png) [@Ms\_Peterson](https://cl.desmos.com/u/Ms_Peterson)\
**Post date:** [February 23, 2021, 6:07pm UTC](https://cl.desmos.com/t/cl-for-practicing-estimation/2733/3 "2021-02-23T18:07:29Z")

</div>

I like the idea of aggregating their estimates. I just didn’t know it could be done. How would I aggregate their estimates on the next screen? Have you created an activity that I could learn from?

Thank you.

---

<div class="post-metadata">

**Author:** ![Daniel\_Grubbs](https://yyz1.discourse-cdn.com/flex031/user_avatar/cl.desmos.com/daniel_grubbs/32/719_2.png) [@Daniel\_Grubbs](https://cl.desmos.com/u/Daniel_Grubbs)\
**Post date:** [February 23, 2021, 9:45pm UTC](https://cl.desmos.com/t/cl-for-practicing-estimation/2733/4 "2021-02-23T21:45:28Z")

</div>

I don’t have an example. You can aggregate any number into a numberList in a graph, say L, H, and J for low, high, just right:

```auto
numberList(`L`): aggregate(yourInputNameHere.latex)
numberList(`H`): aggregate(yourInputNameHere.latex)
numberList(`J`): aggregate(yourInputNameHere.latex)

```

Then, you can use that list, L, however you deem fit in your graph. I recommend putting an initial dummy list in the graph to get things to display the way you want (colors, bounds, etc.). The list will be overridden by the CL when in the activity or preview mode.
