April 13 2017, MyL3 Meeting Notes

Owned by Dana Ayotte
Last updated: Apr 13, 2017
1 min read

Dana, Simon, Jess, Michelle, Jenn, Alan

  • “Nexus data analysis tool” might be best way to describe/name the tool for now (other ideas: Nexus data viewer, Nexus data analyzer, Nexus science lab)
  • The Nexus analysis tool allows multi-modal exploration of the raw data generated through Nexus
  • “Options” might be a better way to describe the data-analysis preferences used in Nexus
  • For the purposes of learner collection and reflection in the MyL3 journal interface, what level of specificity is desirable?
    • Nexus data analysis options could be defined/categorised according to the type of data or type of analysis
    • “Types” of data might include single or multi-value data and time-varying continuous data
    • Right now, the data we are collecting with Nexus (temperature and pH) are both continuous, time-varying, single-value sets of data
    • Other types of data might include multi-dimensional / multi-value data (e.g. data that varies with something other than or in addition to time)
    • The learner could also decide at what level of specificity they want to reflect on what’s working / what isn’t. For example - visualizations in general work for me, or for temperature analysis I prefer colour-based visualizations. i.e. the learner might want to create their own categories/levels of specificity for collection and reflection
  • Right now the Nexus has options for real-time colour-based visualizations (with presentation style specific to T or pH), real-time line graph visualization (value vs. time), as well as (eventually) sonification options for each data set
  • Eventually the analysis tool could include options for 1. general-purpose modes of analysis, 2. data-specific modes of analysis, and 3. custom/learner-created modes of analysis