Reading list
Technical reference documents: a sample of papers describing methods used
A sample, not a complete list.
These are technical reference documents: papers that describe the methods behind the tracking and the measures. It's a sample, not a complete list. Looking for published studies that used HVS Image? Try the live Google Scholar search on the Classic papers page.
- Baker & Hawthorne (2026). vrScript: A Domain-Specific Language for Specifying Protocols in HVS 6D VR Fully Immersive Virtual Reality. HVS Image Software Ltd . doi:10.5281/zenodo.22303968 Classic
This HVS technical reference describes vrScript, the domain-specific language used to specify protocols for the HVS 6D VR fully immersive virtual reality system. It covers the language's syntax and execution model, configuration of environments, navigation, timing and data collection, with worked examples. - Hawthorne (2026). Baker-Hawthorne Direct Path Measures in Morris Water Maze Analysis. HVS Image Software Ltd . doi:10.5281/zenodo.21870806 Classic
This HVS technical note defines the Baker-Hawthorne Direct Path Measures for Morris water maze analysis, which identify different forms of initial goal-directed navigation towards the target or its immediate vicinity. It covers their implementation, interpretation and limitations, and applies to rodent water maze and human virtual reality navigation tasks. - Hawthorne (2026). Inactivity or Slow Movement (Floating) in Morris Water Maze Analysis. HVS Image Software Ltd . doi:10.5281/zenodo.21797205 Classic
This HVS technical note defines the inactivity (floating or slow movement) measure used in Morris water maze analysis. It explains how to interpret inactivity alongside other measures to separate cognitive impairment from non-cognitive influences, for rodent and human virtual reality tasks.
For how to cite each method in your own write-up, see the citations for HVS Image analyses and methods. Researchers using HVS Image are listed on who uses HVS Image.
Spotted a mistake, or know a better source? Tell us and we'll fix it and say so on our corrections page.