Skip to content
 
 

Latest commit

 

History

3,804 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Touching or Chatting: The Utility of LLMs and Tactile Charts for Learning about Complex Chart Types by BLV Individuals

This is a repository for the source code for the study of the paper "Touching or Chatting: The Utility of LLMs and Tactile Charts for Learning about Complex Chart Types by BLV Individuals", presented at IEEE Visualization 2026 and published in the journal IEEE Transactions on Visualization and Computer Graphics. The paper is also available on arXiv.

Citation

If you use the source code, study materials, or results in new projects or use them in a different way, we would appreciate a citation:

Tingying He, Maggie McCracken, Daniel Hajas, Sarah Creem-Regehr, and Alexander Lex. Touching or Chatting: The Utility of LLMs and Tactile Charts for Learning about Complex Chart Types by BLV Individuals. IEEE Transactions on Visualization and Computer Graphics, 2027.

Instructions

The study is built with reVISit, a framework for creating and deploying interactive visualization studies via declarative configuration.

Build Instructions

To run this demo experiment locally, you will need to install node on your computer.

  • Clone https://github.com/revisit-studies/study
  • Run yarn install. If you don't have yarn installed, run npm i -g yarn.
  • To run locally, run yarn serve.
  • Go to http://localhost:8080 to view it in your browser. The page will reload when you make changes.

Release Instructions

Releasing reVISit.dev happens automatically when a PR is merged into the main branch. The name of the pull request should be the title of the release, e.g. v1.0.0. Releasing creates a tag with the same name as the PR, but the official GitGub release should be created manually. The main branch is protected and requires two reviews before merging.

The workflow for release looks as follows: Develop features on feature branch | PRs Dev branch | PR (1 per release) Main branch | Run release workflow on merge References are updated and commit is tagged

About

Create your own study by cloning and editing configs; or check out the code behind the study components.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages