<commit_before># About Easel

Data visualization can be a powerful tool for analyzing and communicating data. However, the overwhelming diversity of options for visualization make it difficult to know how to most effectively visualize data given a specific task. Easel, a visualization recommendation system, was built in response to this problem, specifically for university educators and education support staff looking to improve their visualization techniques of educational data. Its purpose is two-fold: 

* Guide a user towards well-formed questions regarding your educational data.
* Provide recommendations for visualizations that will help answer those questions.

The recommended visualizations were created using a design processes and principles outlined in visualization literature, largely from [Munzer's Visualization Analysis and Design](http://www.cs.ubc.ca/~tmm/vadbook/). We repurposed a visualization selection methodology for the context of education, which can be found by clicking the Selection Process option above along with examples of its usage.

# Using Easel

To view the current (development) version of Easel, please visit: [shiny.engineering.queensu.ca/easel](https://shiny.engineering.queensu.ca/easel) or using `shiny::runGithub("jkaupp/easel")`

# Development

The framework underlying Easel was the work of <NAME> for his  Masters of Applied Science degree at Queen's University in Kingston, Ontario, with Dr. <NAME>.  This work was graciously funded by the Higher Education Quality Council of Ontario (HEQCO).

The Easel application was collaboratively developed by Dr. <NAME> (Queen's University) building the functional application, with the content aspects of the application being provided by Ajay Sivanand.

# Questions

Any questions regarding the framework can be directed to Ajay (<EMAIL>), any questions about the app can be directed to Jake (<EMAIL>) and any bugs or issues reported using the issues tab.


<commit_msg>Updated d README<commit_after>Data visualization can be a powerful tool for analyzing and communicating data. However, the overwhelming diversity of options for visualization make it difficult to know how to most effectively visualize data given a specific task. Easel, a visualization recommendation system, was built in response to this problem, specifically for university educators and education support staff looking to improve their visualization techniques of educational data. Its purpose is two-fold: 

* Guide a user towards well-formed questions regarding your educational data.
* Provide recommendations for visualizations that will help answer those questions.

The recommended visualizations were created using a design processes and principles outlined in visualization literature, largely from [Munzer's Visualization Analysis and Design](http://www.cs.ubc.ca/~tmm/vadbook/). We repurposed a visualization selection methodology for the context of education, which can be found by clicking the Selection Process option above along with examples of its usage.

# Using easel

To view the current (development) version of easel, please visit: [shiny.engineering.queensu.ca/easel](https://shiny.engineering.queensu.ca/easel) or using `shiny::runGithub("jkaupp/easel")`

# Development

The framework underlying sasel was the work of <NAME> for his  Masters of Applied Science degree at Queen's University in Kingston, Ontario, with Dr. <NAME>.  This work was graciously funded by the Higher Education Quality Council of Ontario (HEQCO).

The easel application was collaboratively developed by Dr. <NAME> (Queen's University) building the functional application, with the content aspects of the application being provided by Ajay Sivanand.

# Questions

Any questions regarding the framework can be directed to Ajay (<EMAIL>), any questions about the app can be directed to Jake (<EMAIL>) and any bugs or issues reported using the issues tab.



{'fraction_non_alphanumeric': 0.049719530851606325, 'fraction_numerical': 0.0, 'mean_word_length': 5.3172302737520125, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 2, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7670205', 'n_tokens_mistral': 932, 'n_tokens_neox': 868, 'n_words': 513}