Forum Replies Created
-
Posts
-
Hello Susanne,
That’s a lot of attributes, so it makes sense you want students to delete them. Deleting each one separately is the most straightforward way to do this within CODAP. You, and they, may find it a bit easier to use the case card instead of the case table.
As an alternative, import the Choosy plugin into the document containing the data using this url: https://codap.xyz/plugins/choosy/
Go to the Attributes tab of Choosy and in the gray stripe next to none press the closed eye to hide all the attributes. (See image below.) Then click the slider next to each of the attributes you wish to keep. Voilá, you’re done and can close Choosy.
The downside of this method is that the data values of all the hidden attributes are still present in the document, just hidden. This means that the document isn’t any smaller than when you started, in contrast to the first method.
Hope this helps,
Bill
Attachments:
Para ver el menú más largo, debe arrastrar uno de los nombres de columna (atributos) a un eje del gráfico.
Hi Andee,
Nope. Keep these questions coming!
- There is no interface for setting axis limits other than dragging. Sorry.
- There is also no way to prevent CODAP from changing the axis limits when the user does certain things. In Fathom there is a way to link the axes of two or more graphs together, but we haven’t implemented that in CODAP.
The screenshot didn’t make it for some reason. But placement of the zero can be finicky because if an axis limit is zero we want the zero to display even though there is an implementation detail that gets in the way of proper placement.
Bill
The screenshot shows how to structure data so that you can get more than one “set” of values on the y-axis with a categorical attribute on the x-axis.
Here is a link to that example document.
Hope this helps,
Bill
Attachments:
Hi Andee,
CODAP supports multiple y-axis attributes for scatterplots because it is such a common use case. While I’m sure there a many situations like the one you put forward where it would be useful they just don’t come up among our audience. (You’re the first.)
Incidentally, I couldn’t resist creating this (unsatisfactory) workaround by superimposing two graphs, the top one with a transparent background.
Bill
Thanks for this. The problem is to determine whether to stack the points in each cell vertically or horizontally. Perhaps we could make that decision heuristically based on cell dimensions. Or we could add (yet another) control in the ruler menu.
Stack Points
- Vertically
- Horizontally
Got a preference?
Thanks again,
Bill
Attachments:
Hi Traci,
Thanks for this. I wonder if you could try again to upload the screen capture, or, if that doesn’t work, send it to me by email. There are a lot of alignment issues with dot charts and I want to be sure I understand what you’re referring to.
Alternatively, tell me how to reproduce the problem with a particular dataset.
Thanks,
Bill
Hello,
This is a real problem since you can’t “hover” with your finger. We sort of solved this with getting attribute descriptions so that if you hold your finger down on the table’s column header, the description pops up. We could do something similar with the mean and median lines in a graph. I bet you would be happy if we did this.
Or, we could always display the mean and median values when the user is on a touch-based system. Again, I think this would help you. I’ll add both of these as “stories” in our tracking system.
In the meantime, here are two rather clumsy workarounds.
- In addition to the mean or median, add a “movable value” to the plot. Then you can drag this value to be on top of the mean or median.
- Define an attribute like meanHeight with the formula
mean(height). It helps a little bit to then drag this new attribute all the way to the left of the case table to create a “parent” collection in which you just see the single value.
I hope this helps,
Bill
Hi Emerlyn,
Other users have reported this difficulty as well. There is discussion about it in this thread. Here is the take-home from that:
- From within CODAP choose Open from the “three strips” menu in the upper left corner.
- Choose Google Drive.
- Login to your Google account.
This is a one-time thing. After having logged via CODAP you will be able to open CODAP documents from Google Drive by double-clicking.
I hope this helps!
Bill
Hi Andee,
I’m sorry that you still have occasional problems with saving to and opening from Google Drive. If you get a better sense of when the problem occurs, please let us know and we’ll try to reproduce and fix it.
And thanks for the typo tip!
Bill
Hi Margaret,
Ah yes, parentheses! When importing, if CODAP encounters parentheses in an attribute name, it (usually helpfully but not always) treats what is inside as the unit for the attribute.
But I’m logging a bug, ’cause CODAP should be able to handle correctly the file with the entire attribute name in parens. Thanks for sending the file!
And I’m glad you figured things out,
Bill
Hi Margaret,
That is confusing! Nothing has changed on our end, and I just verified that importing a csv still works as usual for me.
Could you include the file itself so we can see if we get the same results and, if so, figure out why?
Thanks,
Bill
Hi folks,
Just to be clear, the bottom line is that you need to:
- From within CODAP choose Open from the “three strips” menu in the upper left corner.
- Choose Google Drive.
- Login to your Google account.
This is a one-time thing. After having logged via CODAP you will be able to open CODAP documents from Google Drive by double-clicking.
Note, this has nothing to do with shared CODAP documents since those are stored separately from Google Drive.
Hope this helps,
Bill
Hi again,
We think that once you have logged into Google Drive in CODAP things will go back to the way they have always been. It’s the transition to a new Google Drive API that has caused this.
Note: You can log in to Google Drive in CODAP by choosing OPEN and then clicking on the Google Drive option. If you’re not already logged in, that’s where you’ll see the login button.
Hope this helps and let us know of any further problems,
Bill
