[Bill Finzer]

Hi Andrew,

This problem has occurred for a couple other folks and it’s on our list. Sorry that we haven’t gotten to it yet!

What we suggest is the following:

1. On a large monitor, fill up the screen with your CODAP window.
2. Use the browser View menu to increase the resolution as much as you can, keeping your graph in view.
3. Now do a screen capture.

When you shrink the screen captured image back down to what you want, it will be of higher resolution. Some tools will let you set the pixels per inch of the image.

Hope that helps,

Bill

[Bill Finzer]

Hi Jacob,

Amazing catch! It certainly appears to be a bug. I’ll attempt to replicate and log.

As to how missing values are (supposed to be) treated: They are never treated as zero and they don’t appear in plots except in legend coloration where their color is gray. Calculations in plots or attributes ignore missing values. One exception I can think of is the formula: count(!test). Suppose test is an attribute with one missing value. Then the result of this formula will be 1 because the exclamation point signifies negation and returns true for the missing value.

[Bill Finzer]

Maggie,

I just tried on a chromebook and it worked for me. Has it ever worked for you?

Bill

[Bill Finzer]

I’m copying here a response from Sally Wu of the NetLogo team that she posted in another thread about NetLogo/CODAP integration.

We have developed an updated NetLogo CODAP integration guide. It includes instructions as well as links to example CODAP/NetLogo models used in high school curricula. Please reach out if you would like additional support on your model.

[Bill Finzer]

Thanks Susanne! I’ve added your request to our desired features list.

[Bill Finzer]

Hi Susanne,

I’m sorry to report that you cannot create a hat plot in CODAP. Would you mind describing how you would use it and how important you think it is? This will help us in prioritizing it as a feature. (I’m familiar with it in TinkerPlots.)

Thanks very much,

Bill

[Bill Finzer]

Hi Darren,

I’m going to reach out to the NetLogo team so they can help us. Stay tuned.

Bill

[Bill Finzer]

Hi Sara V,

I’m not sure I understand your question, but, if you haven’t already, check out CODAP’s bar charts as shown in the accompanying screen shot. They aren’t colored by a gradient, but they do show two different ways to think about part and whole.

The second screen shot shows that you can use a gradient to color bars (and points). But I was disappointed that the result is not smoothly uniform from light to dark.

Does that get anywhere close to what you were thinking about?

Bill

p.s. No pie charts in CODAP.

Attachments:

1. 

   Bar-Charts.png
   

2. 

   Bar-chart-gradient.png
   

[Bill Finzer]

Hi Laura,

Thanks for your detailed response. It really helps us think about how to prioritize the median-median line as a CODAP feature.

Bill

[Bill Finzer]

• There is no affordance in CODAP for plotting a median median line on a scatterplot. You’re the first to ask about it. How important do you think it is?
• You’re not the first to want to plot more than one value. It’s on our list of desired features.

Thanks very much for helping us prioritize feature development!

Bill

[Bill Finzer]

Hi Susanne,

Unfortunately it has never been possible to change the size of the formula editor window in CODAP. I’ve wished for this as well and will add it to our list of desired features.

Thanks for letting us know!

Bill

[Bill Finzer]

I can think of a couple possibilities and I bet others can think of more.

1. The easiest might be to use the graph’s “brush” menu to reduce the size of the points. That doesn’t change the number of points of course, but it might make the graph easy to read.
2. Define a new attribute with a formula that returns the measurement value if the caseIndex is a multiple of, say, 25, and returns an empty value otherwise. Let’s say the measurement attribute is altitude. Then the formula for the new attribute would be:

if(caseIndex % 25 = 0, altitude, ”)

Hope that helps,

Bill

[Bill Finzer]

Hi Kaitlyn,

Did you convert it to “json” or “geojson?” The latter is what you need.

If the file is less than 512K, would you upload it here so we can try it to figure out what’s going on? If it’s too big, or you would prefer, send it by email.

Bill

[Bill Finzer]

Hello Kaitlyn,

The trick is to find a “geojson” file with the watershed “boundary” information in it. Once you have such a file on your desktop, drag it into a CODAP document. It should open a case table and a map displaying the boundary information.

I did a quick search and, like you, didn’t immediately stumble on anything. Sigh.

Sometimes I’ve only been able to find a file in a different format from geojson such as KML or a Shapefile. There are online converters that convert from a given format to geojson and these have worked for me in the past.

CODAP doesn’t have any builtin tools for helping you create boundary information. But one colleague was successful in creating his own boundaries for, if I remember correctly, bike lanes in NYC. So that would be an outside possibility.

Don’t hesitate to post here again if you get stuck. Anyone else have any experience with watershed boundary geojson files?

Bill

[Bill Finzer]

Hi Traci,

Thanks so much for this bug report. I’ve logged it in our bug tracking database. And, because of your post, I’ve given it a high priority!

Bill

[Author]

Posts