Forum Replies Created
-
Posts
-
Hello William,
The short answer is that I am not sure why you are getting some of these errors, I don’t think they necessarily indicate a problem.* The first error, “codap-config.js” not found, is, unfortunately, normal. This is a file used to customize a production configuration, and is not used in the development environment, and not present. Its absence does not cause any harm, except for the warning.* The next two warnings about react method being deprecated comes apparently from a library that is included in codap-lib-bundle.js. I do not see these warnings on my machine (Mac running latest OS-X). In any case they are warnings about future removal, so they should not affect current libraries.* The next warning and two errors concern the manifest. They are new to me. I will look into them, but as the manifest is only informative in CODAP’s current implementation, they should not affect things.* We are down to the last error: “Access to XMLHttpRequest …has been blocked.”: This is the error that causes the dialog “Unable to load Parachute Model” to come up. This is a CORS error that is occurring because the development instance comes from an HTTP only server. The examples files come from the CODAP server which was recently made to enforce an HTTPS-only policy. This is an unfortunate change for developers, but we have to live with it. One thing to do is to save example CODAP documents on your local file system, and simply drag the files into the CODAP workspace when you need them.I am sorry that you encountered these warnings and errors, but I do think you have successfully set up the development environment.Thanks,JonathanDan’s response is exactly right if your goal really is to create a parallel attribute with “little or none” set if “original_attr” had a value of “little” or “none” and the original value otherwise.
If you don’t mind altering the original attribute, then you can accomplish it in place quite easily without a formula. This technique makes use of CODAP’s dynamic grouping capability. To do this you would open the Case Table. You will see a blank region on the left side of the leftmost table. Drag the column header, “original_attr”, to the left over to this blank area and drop it. This should create a new parent collection containing just the unique values in “original_attr”. Edit the cell that contains “little” and the cell that contains “none” to have the value “little or none”. Then simple drag “original_attr” back to its original position in the case table. The parent group should go away and all the values that were “little” or “none” will have the alteration.
Jonathan Sandoe
Hello Traci,
I was assuming that you had the two data sets already in a single CODAP document, but apparently that is not the case. It seems that you have two separate CODAP documents, one with a Climate data set and the other with the Lyme Disease data set.
A single CODAP document can have many datasets. Each data set corresponds with exactly one Case Table, so you can see how many data sets you have by opening the Case Table menu in the CODAP tool bar.
There are many ways to get a data set into a CODAP document. It is easiest if the source data is in a comma separated values (“CSV”, usually a file with a ‘.csv’ extension) file or a tab delimited text file (usually with a ‘.txt’ extension.) To bring one of these files into CODAP simply drag the file and drop it in the CODAP workspace. You can also drag and drop a URL that refers to a CSV or tab delimited file. You can drag and drop as many of these files as you like and they will be added to the current collection of data sets. If you drag a ‘.codap’ file over the workspace that will replace the current CODAP document with the one in the file.
So, if you have the data in two separate CODAP documents, and don’t have an equivalent CSV or tab delimited file, what do you do? Well, that is easy! CODAP can export the data from its tables into a CSV file. Select the Case Table for the data set and click on the ruler icon on the bottom of the right-hand inspector bar. Look for “Export Case Data…” in the menu that opens up.
Concerning the “lookUpByKey” function: it is not the easiest of functions to grasp. I have made a simple example document to demonstrate, here. I hope it makes clearer how it is set up.
Jonathan
There is no explicit way to merge data sets at this time in CODAP, but you can create an attribute that refers to the value of an attribute in another data set.
Suppose you have data set “Climate” as above with “Year” as an attribute, and you have another, “Lyme Disease”, with attributes, “Year” and “Incidence”. You can create an attribute “occurrences” in “Climate” and bring over the values from the other data set with a formula:
lookupByKey(“Lyme Disease”, “occurrences”, “Year”, Year)
You can do this with as many attributes as necessary to, effectively, merge the data sets.
Jonathan
Hello Dany and Filipo,
I have converted boundary data for Italian regions and put it on the server. It can be referenced as IT_region_boundaries. Here is a small document for demonstration: https://codap.concord.org/app/#shared=74838
You will note that a couple of the thumbnail icons did not get generated properly. This is likely a bug in our converter, and I will fix it when I can.
Jonathan
Hello Prof. Spririto,
The file looks like exactly what we need. Generating the small thumbnails is a part of the process we do. I’ll let you know when the boundary file is accessible.
Thanks,
Jonathan
Hi Dany,
We are very pleased by your interest in this (and we are very pleased to learn that you are using CODAP in your online course.) The steps for creating new boundary documents are, at least in theory, not difficult. They are:
1. Find a suitable GeoJSON file with boundary data for the Italian provinces or districts. GeoJSON is a standard format for the representation of geographic data. There are many openly licensed datasets on the web. For example, this one may suit: https://github.com/deldersveld/topojson/blob/master/countries/italy/italy-regions.json. Save the one you like as a file on your computer.
2. Open CODAP with this URL: https://codap.concord.org/releases/staging/static/dg/en/cert/index.html?di=https://concord-consortium.github.io/codap-data-interactives//GeoJSONImporter/GeoJSONImporter.html . This will create a CODAP instance with a GeoJSON Importer plugin in it.
3. Click on the “Choose File” button, then select your GeoJSON file.
4. Click on “Import”.
If all goes well the plugin will upload and convert the file to a dataset named “Boundaries”. You should be able to open it by clicking on the “Tables” menu or by opening a map.
5. Close the plugin, map and any other components, then create a share URL for the document (in the file menu in the upper left of CODAP, select “Share…”, then “Get link to shared view”, then follow the instructions to copy the shared URL.
6. Send us the link. There are a couple of steps on our side to get it on the server that we have not automated, which we will happily do. We will let you know how to access.By the way, as you may have noticed, CODAP has been translated into a number of languages. This has been done by volunteers, since it is not something in our capacity to do, but it is not difficult. We use a very nice cloud based translation service called Po Editor (https://poeditor.com). If you would be interested in taking on an Italian translation or know someone who might be interested, we can set you up.
Thanks,
Jonathan Sandoe
Andrew,
I am curious how big the data sets are in the documents you are sharing. We have seen the same behavior recently with documents with large data sets. (For current CODAP, a data set with more than 40,000 cases would be considered large.)
Jonathan Sandoe
Hi Andee,
I tried to reproduce this problem with a variety of datasets and have been unable to. I wonder if there was something about your dataset that provokes the problem. If you were able to tell us a little more about the dataset or provide a sample, that would be helpful for resolving this issue.
Jonathan
Your browser opens (or should open) a new tab with a copy of the original document. This may appear as if nothing changed if your browser tabs are not visible.
Jonathan
Hi Andee,
Its hard to think that you did anything wrong. It seems that CODAP is confused. There is often a correspondence between file name and document name in CODAP, but it they are not always 100% in synch. Document name is the name presented in the field on the top left of the CODAP screen. I am having difficulty replicating what you are reporting. When you say you saved the file did you save it to your local file system or to Google Drive, and were you on a Mac or PC?
Thanks,
Jonathan SandoeCreate new attributes named, for example ‘month’. Click on the column header for the attribute, then select “Edit Formula…”. For the formula, type “month(dt)”. Apply a similar strategy for year.
Jonathan
Currently, CODAP exports CSV files only, which has no standard way of expressing meta-data, so you are correct, you would lose the attribute descriptions in the export.
Jonathan
Hello Max,
CODAP employs the SproutCore framework and uses SproutCore tools to deploy a development version. We build a static website to deploy a production instance. Each formal build can be found in the form of a Zip archive in https://codap.concord.org/releases/zips. If you are interested in deploying CODAP on a server the easiest way to do this is to download the zip file and unzip it into the file system of a web server. Nearly any web server will suit. CODAP makes no special demands on the server. Apache is fine. So would the Python Simple HTTP Server.
If you have set up a development environment using the process described here, it would be possible to run in production mode by appending ‘–mode=production’ to the normal sc-server command, I think.
I am curious about your use case, Max. Are you engaged in, or interested in, developing new CODAP features? If so, this is very interesting to us and we may be able to be of assistance.
Thanks,
Jonathan Sandoe
