I need help choosing a JavaScript chart libraryComputers Electronics and Technology
Replay
Every recorded step of a run, as the agent saw the screen: the frame, the action it took, what it said, and which rubrics the judge's evidence had reached by then. 4 runs recorded with screenshots.
Claude Opus 5.5
- 100%
- Rubric score
- 100
- Steps
- 14/14
- Rubrics passed
Task promptI need help choosing a JavaScript chart library for an earthquake dashboard web project. Start in CryptPad and create one research document with sections for Data, Library Evidence, Accessibility, Scoring, Prototype Plan, Tests, Comparison, Recommendation, and Handoff. Use the official USGS GeoJSON documentation and the publicly available 30-day earthquake feed as they exist at the time of research. Record the feed access time and feed generation time. Sort the feed records from newest to oldest and create a fixed sample containing the latest 500 records, or all records if fewer than 500 are available. Save the exact sample in a separate CryptPad Code pad as JSON or CryptPad Sheet as CSV. In the Data section of the research document, record the sample share link, access time, feed generation time, complete-feed record count, sample record count, and any missing values in the fields used by the prototypes. Treat this saved sample as the frozen dataset for every later comparison and prototype rather than refreshing the feed during the task. Compare exactly five open-source libraries: Chart.js, D3, Apache ECharts, Plotly.js, and Vega-Lite. Use each project’s official documentation and official repository. In the Library Evidence section, record the relevant links, current stable version, licence, latest stable release date, browser setup, scatter- and bar-chart support, filter/update support, responsive behaviour, accessibility guidance, official examples, and documentation quality. Record the research date for changing facts such as versions and release dates. For stable-version evidence, use the project’s official release documentation first where available, then GitHub Releases, then the newest clearly stable repository tag. Record and explain material differences between documentation, release pages, or repository tags rather than silently choosing one. Read the current W3C WCAG 2.2 Quick Reference and WAI complex-images guidance. In the Accessibility section, create checks covering keyboard operation, visible focus, use of colour, chart labels, a meaningful text alternative, and layouts at 360, 768, and 1280 CSS pixels. In the Scoring section, create a 100-point comparison using these fixed weights: accessibility 25, student clarity 20, charts and interaction 20, browser setup 15, sample performance 10, and documentation and activity 10. Define how evidence maps to scores before assigning them, score all five libraries with source-based reasons, rank them, use accessibility as the tie-break when totals are equal, and select the top two finalists. Before writing either prototype, create a two-column Prototype Plan in CryptPad with one column for each finalist. Require both prototypes to use the same frozen sample, wording, magnitude filter behaviour, chart definitions, table rules, educational content, attribution, and layout structure so the comparison does not advantage one library through different content or design. Then use JSFiddle or another free, publicly accessible HTML/CSS/JavaScript editor that can provide shareable editor and preview/result links without requiring the creation of a new account for this task. Build one separate prototype for each finalist. Each prototype must use the same fixed earthquake sample and show the total record count, a magnitude filter, a time-versus-magnitude scatter plot, a magnitude-band bar chart, and a table containing the 20 most recent earthquakes under the active filter or clearly documented common table rule. Each prototype must also include exactly three learning goals, exactly six glossary terms, relevant units, USGS attribution, feed generation time, sample access date, and the frozen-sample link. Test both prototypes using the same procedure and record the results in the CryptPad Tests section. Check the unfiltered count, the same two documented magnitude-filter settings, chart results, table results, keyboard operation, visible focus, colour use, chart text alternatives, layouts at 360, 768, and 1280 CSS pixels, source/sample links, and browser-console errors. Record expected and observed results and fix every identified prototype defect before the final comparison. In the Comparison section, compare the two finalists using the research evidence and matched-prototype test results. Recommend one winner and one backup, explain the decision, and state at least one limitation or uncertainty that could affect the recommendation. Finish with a six-row Handoff table containing the CryptPad research-document link, frozen-sample link, both prototype editor links, and both prototype preview/result links. Check all six links while signed out and record whether they are publicly accessible and what limitation, if any, remains. Do not publish a production website, buy anything, create an account only for this task, or submit student information.
I need help choosing a JavaScript chart library for an earthquake dashboard web project. Start in CryptPad and create one research document with sections for Data, Library Evidence, Accessibility, Scoring, Prototype Plan, Tests, Comparison, Recommendation, and Handoff. Use the official USGS GeoJSON documentation and the publicly available 30-day earthquake feed as they exist at the time of research. Record the feed access time and feed generation time. Sort the feed records from newest to oldest and create a fixed sample containing the latest 500 records, or all records if fewer than 500 are available. Save the exact sample in a separate CryptPad Code pad as JSON or CryptPad Sheet as CSV. In the Data section of the research document, record the sample share link, access time, feed generation time, complete-feed record count, sample record count, and any missing values in the fields used by the prototypes. Treat this saved sample as the frozen dataset for every later comparison and prototype rather than refreshing the feed during the task. Compare exactly five open-source libraries: Chart.js, D3, Apache ECharts, Plotly.js, and Vega-Lite. Use each project’s official documentation and official repository. In the Library Evidence section, record the relevant links, current stable version, licence, latest stable release date, browser setup, scatter- and bar-chart support, filter/update support, responsive behaviour, accessibility guidance, official examples, and documentation quality. Record the research date for changing facts such as versions and release dates. For stable-version evidence, use the project’s official release documentation first where available, then GitHub Releases, then the newest clearly stable repository tag. Record and explain material differences between documentation, release pages, or repository tags rather than silently choosing one. Read the current W3C WCAG 2.2 Quick Reference and WAI complex-images guidance. In the Accessibility section, create checks covering keyboard operation, visible focus, use of colour, chart labels, a meaningful text alternative, and layouts at 360, 768, and 1280 CSS pixels. In the Scoring section, create a 100-point comparison using these fixed weights: accessibility 25, student clarity 20, charts and interaction 20, browser setup 15, sample performance 10, and documentation and activity 10. Define how evidence maps to scores before assigning them, score all five libraries with source-based reasons, rank them, use accessibility as the tie-break when totals are equal, and select the top two finalists. Before writing either prototype, create a two-column Prototype Plan in CryptPad with one column for each finalist. Require both prototypes to use the same frozen sample, wording, magnitude filter behaviour, chart definitions, table rules, educational content, attribution, and layout structure so the comparison does not advantage one library through different content or design. Then use JSFiddle or another free, publicly accessible HTML/CSS/JavaScript editor that can provide shareable editor and preview/result links without requiring the creation of a new account for this task. Build one separate prototype for each finalist. Each prototype must use the same fixed earthquake sample and show the total record count, a magnitude filter, a time-versus-magnitude scatter plot, a magnitude-band bar chart, and a table containing the 20 most recent earthquakes under the active filter or clearly documented common table rule. Each prototype must also include exactly three learning goals, exactly six glossary terms, relevant units, USGS attribution, feed generation time, sample access date, and the frozen-sample link. Test both prototypes using the same procedure and record the results in the CryptPad Tests section. Check the unfiltered count, the same two documented magnitude-filter settings, chart results, table results, keyboard operation, visible focus, colour use, chart text alternatives, layouts at 360, 768, and 1280 CSS pixels, source/sample links, and browser-console errors. Record expected and observed results and fix every identified prototype defect before the final comparison. In the Comparison section, compare the two finalists using the research evidence and matched-prototype test results. Recommend one winner and one backup, explain the decision, and state at least one limitation or uncertainty that could affect the recommendation. Finish with a six-row Handoff table containing the CryptPad research-document link, frozen-sample link, both prototype editor links, and both prototype preview/result links. Check all six links while signed out and record whether they are publicly accessible and what limitation, if any, remains. Do not publish a production website, buy anything, create an account only for this task, or submit student information.