Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
3
datasets available to search
ShareScore release 0.9.0
Dataset results
3 results for “end user programming”
Replication Package: Block-based or Graph-Based? Why Not Both? Designing a Hybrid Programming Environment for End-users
<p><strong>Block-based or Graph-based? Why Not Both? Designing a Hybrid Programming Environment for End-users: Replication Package</strong></p> <p>This repository contains supplementary materials for the paper "Block-based or Graph-based? Why Not Both? Designing a Hybrid Programming Environment for End-users". We provide this data for transparency reasons and to support replications of our experiments.</p> <p><strong>Summary of files contained in this package</strong></p> <p>This package contains two parts:</p> <ul> <li> <p>The <code>data-analysis/</code> folder contains the raw dataset we collected for our experiment in CSV format, as well as scripts we used for our analyses.</p> <ul> <li>Column <code>ID</code> contains a unique 4-digit identifier for each participant that they were assigned throughout our study.</li> <li>Column <code>Group</code> contains the group (Blocks/Graph) that participants were randomly assigned to.</li> <li>Columns <code>Task1Time</code> and <code>Task2Time</code> contain the time participants spent to complete the two programming tasks of our study in minutes.</li> <li>Columns <code>Task1Success</code> and <code>Task2Success</code> contain a boolean value indicating whether the participants successfully completed the given task. Note that participants had unlimited attempts until they timed out after a strict time limit of 30 minutes, so if a participant was unsuccessful the corresponding time value is 30.</li> <li>Columns <code>Task1Tests</code> and <code>Task2Tests</code> contain the number of times a participant executed their code throughout a task, including their final submission if they were successful.</li> <li>Columns <code>LearnTask</code>, <code>ReadTask</code> and <code>WriteTask</code> contain the scores that participants gave to the task editor component of their assigned programming environment. There are 3 scores for the categories "learnability", "readability" and "writability". Scores are on a 5-point scale from 1 (worst) to 5 (best).</li> <li>Columns <code>LearnTrig</code>, <code>ReadTrig</code> and <code>WriteTrig</code> contain the scores that participants gave to the trigger editor component of their assigned programming environment. There are 3 scores for the categories "learnability", "readability" and "writability". Scores are on a 5-point scale from 1 (worst) to 5 (best).</li> <li>Columns <code>LearnComp</code>, <code>ReadComp</code> and <code>WriteComp</code> contain the scores that participants gave to their assigned assigned programming environment in direct comparison to the other alternative. There are 3 scores for the categories "learnability", "readability" and "writability". Unlike in the paper, where scores are on a scale from -2 to 2, the raw scores here are on a 5-point scale from 1 (strong preference for other environment) to 5 (strong preference for own environment).</li> <li>The script <code>successplot.py</code> was used to generate the success rate plot used in a figure in the paper</li> <li>The script <code>survival.py</code> was used to perform the survival analysis presented in the paper and generate the related figure.</li> <li>The script <code>batplot.py</code> was used to generate the 3x3 grid of ratings used in a figure in the paper.</li> </ul> </li> <li> <p>The <code>materials/</code> folder contains the tutorials and task descriptions we presented to study participants. It also contains the exact wording of pre-screening and post-experiemental survey questions.</p> <ul> <li>The image <code>pre-screening.png</code> shows the three pre-screening questions we used to determine whether our participants could be included in our study.</li> <li>The images <code>tutorial1_instructions.png</code> and <code>tutorial1_sim.png</code> contain the instructions and initial simulator state we provided to participants for the first programming tutorial. This tutorial did not provide starter code and was identical for both participant groups.</li> <li>The images <code>tutorial2_instructions.png</code> and <code>tutorial2_sim.png</code> contain the instructions and initial simulator state we provided to participants for the second programming tutorial. This tutorial was identical for both participant groups and provided participants with starter code, which is shown in the images: <ul> <li><code>tutorial2_code_main.png</code> for the main program in the left canvas</li> <li><code>tutorial2_code_move.png</code> for the definition of "Move box to the right".</li> </ul> </li> <li>The images <code>tutorial3_instructions_blocks.png</code>/<code>tutorial3_instructions_graph.png</code> and <code>tutorial3_sim.png</code> contain the instructions and initial simulator state we provided to participants for the third programming tutorial. This tutorial also provided participants with starter code, which is shown in the images: <ul> <li><code>tutorial3_code_main.png</code> for the main program in the left canvas</li> <li><code>tutorial3_code_pick.png</code> for the definition of "Pick up box"</li> <li><code>tutorial3_code_place.png</code> for the definition of "Place box"</li> </ul> </li> <li>The images <code>task1_instructions.png</code> and <code>task1_sim.png</code> contain the instructions and initial simulator state we provided to participants for the first programming task. The task did not provide starter code and the instructions were identical for both participant groups.</li> <li>The images <code>task2_instructions.png</code> and <code>task2_sim.png</code> contain the instructions and initial simulator state we provided to participants for the second programming task. The instructions were identical for both groups. This task also provided participants with starter code, which is shown in the images: <ul> <li><code>task2_code_main.png</code> for the main program in the left canvas</li> <li><code>task2_code_pick_prog.png</code> for the definition of "Pick up block"</li> <li><code>task2_code_load_trig_blocks.png</code>/<code>task2_code_load_trig_graph.png</code> for the definition of the trigger "Ready to load machine"</li> <li><code>task2_code_load_prog.png</code> for the definition of "Load and activate machine"</li> <li><code>task2_code_finished_trig_blocks.png</code>/<code>task2_code_finished_trig_graph.png</code> for the definition of the trigger "Machine finished"</li> <li><code>task2_code_finished_prog1.png</code> for the definition of "Get block from machine"</li> <li><code>task2_code_finished_prog2.png</code> for the definition of "Place block in bin"</li> </ul> </li> <li> <div>The document <code>post_survey_full.pdf</code> contains a raw export of the comprehension questions and post-experimental survey as they were presented to participants </div> </li> <li>The image <code>usability.png</code> shows the usability questions we used to determine a participant's rating of their assigned programming environment. The questions were identical for both participant groups.</li> <li>The images <code>comprehension_blocks_1.png</code> and <code>comprehension_blocks_2.png</code> show the program comprehension questions we used to determine whether participants in the Blocks group could understand more complex triggers.</li> <li>The images <code>comprehension_graph_1.png</code> and <code>comprehension_graph_2.png</code> show the program comprehension questions we used to determine whether participants in the Graph group could understand more complex triggers.</li> <li>The images <code>comparison_blocks.png</code> and <code>comparison_graph.png</code> show the images of triggers in the alternative environment that we showed to our participants before choosing their preferred environment. The questions were identical for both participant groups.</li> <li>The image <code>comparison.png</code> shows the questions we used to determine a participant's preference between the two programming environment alternatives.</li> </ul> </li> </ul>
# Blocks? Graphs? Why Not Both? Designing and Evaluating a Hybrid Programming Environment for End-users: Replication Package
<p><strong>Blocks? Graphs? Why Not Both? Designing and Evaluating a Hybrid Programming Environment for End-users: Replication Package</strong></p> <p>This repository contains supplementary materials for the paper "Blocks? Graphs? Why Not Both? Designing and Evaluating a Hybrid Programming Environment for End-users". We provide this data for transparency reasons and to support replications of our experiemnts.</p> <p><em>Note: This package is anonymized for peer review purposes. We will provide contact information for the authors at a later date. We also plan to add interactive versions of our tasks and tutorials in an updated version to allow readers easier exploration/experimentation.</em></p> <p><strong>Summary of files contained in this package</strong></p> <p>This package contains two parts:</p> <ul> <li> <p>The <code>data-analysis/</code> folder contains the raw dataset we collected for our experiment in CSV format, as well as scripts we used for our analyses.</p> <ul> <li>Column <code>ID</code> contains a unique 4-digit identifier for each participant that they were assigned throughout our study.</li> <li>Column <code>Group</code> contains the group (Blocks/Graph) that participants were randomly assigned to.</li> <li>Columns <code>Task1Time</code> and <code>Task2Time</code> contain the time participants spent to complete the two programming tasks of our study in minutes.</li> <li>Columns <code>Task1Success</code> and <code>Task2Success</code> contain a boolean value indicating whether the participants successfully completed the given task. Note that participants had unlimited attempts until they timed out after a strict time limit of 30 minutes, so if a participant was unsuccessful the corresponding time value is 30.</li> <li>Columns <code>Task1Tests</code> and <code>Task2Tests</code> contain the number of times a participant executed their code throughout a task, including their final submission if they were successful.</li> <li>Columns <code>LearnTask</code>, <code>ReadTask</code> and <code>WriteTask</code> contain the scores that participants gave to the task editor component of their assigned programming environment. There are 3 scores for the categories "learnability", "readability" and "writability". Scores are on a 5-point scale from 1 (worst) to 5 (best).</li> <li>Columns <code>LearnTrig</code>, <code>ReadTrig</code> and <code>WriteTrig</code> contain the scores that participants gave to the trigger editor component of their assigned programming environment. There are 3 scores for the categories "learnability", "readability" and "writability". Scores are on a 5-point scale from 1 (worst) to 5 (best).</li> <li>Columns <code>LearnComp</code>, <code>ReadComp</code> and <code>WriteComp</code> contain the scores that participants gave to their assigned assigned programming environment in direct comparison to the other alternative. There are 3 scores for the categories "learnability", "readability" and "writability". Unlike in the paper, where scores are on a scale from -2 to 2, the raw scores here are on a 5-point scale from 1 (strong preference for other environment) to 5 (strong preference for own environment).</li> <li>The script <code>survival.py</code> was used to perform the survival analysis presented in the paper and generate the related figure.</li> <li>The script <code>batplot.py</code> was used to generate the 3x3 grid of ratings used in a figure in the paper.</li> </ul> </li> <li> <p>The <code>materials/</code> folder contains the tutorials and task descriptions we presented to study participants. It also contains the exact wording of pre-screening and post-experiemental survey questions.</p> <ul> <li>The image <code>pre-screening.png</code> shows the three pre-screening questions we used to determine whether our participants could be included in our study.</li> <li>The images <code>tutorial1_instructions.png</code> and <code>tutorial1_sim.png</code> contain the instructions and initial simulator state we provided to participants for the first programming tutorial. This tutorial did not provide starter code and was identical for both participant groups.</li> <li>The images <code>tutorial2_instructions.png</code> and <code>tutorial2_sim.png</code> contain the instructions and initial simulator state we provided to participants for the second programming tutorial. This tutorial was identical for both participant groups and provided participants with starter code, which is shown in the images: <ul> <li><code>tutorial2_code_main.png</code> for the main program in the left canvas</li> <li><code>tutorial2_code_move.png</code> for the definition of "Move box to the right".</li> </ul> </li> <li>The images <code>tutorial3_instructions_blocks.png</code>/<code>tutorial3_instructions_graph.png</code> and <code>tutorial3_sim.png</code> contain the instructions and initial simulator state we provided to participants for the third programming tutorial. This tutorial also provided participants with starter code, which is shown in the images: <ul> <li><code>tutorial3_code_main.png</code> for the main program in the left canvas</li> <li><code>tutorial3_code_pick.png</code> for the definition of "Pick up box"</li> <li><code>tutorial3_code_place.png</code> for the definition of "Place box"</li> </ul> </li> <li>The images <code>task1_instructions.png</code> and <code>task1_sim.png</code> contain the instructions and initial simulator state we provided to participants for the first programming task. The task did not provide starter code and the instructions were identical for both participant groups.</li> <li>The images <code>task2_instructions.png</code> and <code>task2_sim.png</code> contain the instructions and initial simulator state we provided to participants for the second programming task. The instructions were identical for both groups. This task also provided participants with starter code, which is shown in the images: <ul> <li><code>task2_code_main.png</code> for the main program in the left canvas</li> <li><code>task2_code_pick_prog.png</code> for the definition of "Pick up block"</li> <li><code>task2_code_load_trig_blocks.png</code>/<code>task2_code_load_trig_graph.png</code> for the definition of the trigger "Ready to load machine"</li> <li><code>task2_code_load_prog.png</code> for the definition of "Load and activate machine"</li> <li><code>task2_code_finished_trig_blocks.png</code>/<code>task2_code_finished_trig_graph.png</code> for the definition of the trigger "Machine finished"</li> <li><code>task2_code_finished_prog1.png</code> for the definition of "Get block from machine"</li> <li><code>task2_code_finished_prog2.png</code> for the definition of "Place block in bin"</li> </ul> </li> <li>The image <code>usability.png</code> shows the usability questions we used to determine a participant's rating of their assigned programming environment. The questions were identical for both participant groups.</li> <li>The images <code>comprehension_blocks_1.png</code> and <code>comprehension_blocks_2.png</code> show the program comprehension questions we used to determine whether participants in the Blocks group could understand more complex triggers.</li> <li>The images <code>comprehension_graph_1.png</code> and <code>comprehension_graph_2.png</code> show the program comprehension questions we used to determine whether participants in the Graph group could understand more complex triggers.</li> <li>The images <code>comparison_blocks.png</code> and <code>comparison_graph.png</code> show the images of triggers in the alternative environment that we showed to our participants before choosing their preferred environment. The questions were identical for both participant groups.</li> <li>The image <code>comparison.png</code> shows the questions we used to determine a participant's preference between the two programming environment alternatives.</li> </ul> </li> </ul>
Can Guided Decomposition Help End-Users Write Larger Block-Based Programs? A Mobile Robot Experiment. (supplementary materials)
<p>Supplementary Material for the research paper "<strong>Can Guided Decomposition Help End-users Write Larger Block-based Programs? a Mobile Robot Experiment</strong>", published at the <em>Conference on Object-oriented Programming, Systems, Languages (OOPSLA 22).</em></p> <p>Paper DOI: <a href="http://doi.org/10.1145/3563296">http://doi.org/10.1145/3563296</a> </p> <p>This archive contains:</p> <ul> <li>An interactive demonstration of the used tutorials and tasks (in the folders tut1-3/ and task1-3/).</li> <li>An interactive playground to test out the presented development environments (onecanvas.html and twocanvas.html in the root folder).</li> <li>The raw data collected throughout the controlled experiment presented in the paper (mobilerobots-data.csv and mobilerobots-data.html)</li> <li>An overview page that allows convenient access to each of the previously described contents.</li> </ul> <p>A non-archival version of the contents is also available here: <a href="https://vcuse.github.io/alvo/first-experiment/">vcuse.github.io/alvo/first-experiment/</a></p> <p><em>Note: The interactive demonstrations work locally. However, several other files and folders contained in the archive are required to run the interactive demonstrations. Deleting or moving any parts of the archive may break the interactive elements. This demo was tested to work as intended on all commonly used web browsers in their most recent versions of 2022. Use at own risk</em></p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.