User’s Manual for the Mobile Usability & Accessibility Lab (MUA-Lab)
Authors: Melissa R. Lemke, Jack M. Winters, Molly Follette Story, Sarma Danturthi, Sean Campbell, Alan Barr, Elizabeth Omiatek, David Rempel
- Version 0.1: January 2004
- Version 0.2: June 2004
- Version 0.3: October 2004
- Version 1.0: January 2005
- Version 1.1: June 2005
- Version 1.2: May 2006
- Version 2.0: February 2008
Copyright © 2005 RERC on Accessible Medical Instrumentation
Funding for the RERC-AMI was provided by the National Institute on Disability and Rehabilitation Research, U.S. Department of Education, grant #H133E020729
Table of Contents
1. Introduction
1.1 Background
1.2 MUA-Lab Design Criteria and Specifications
1.3 General Design of the Protocol Manager2. Advance Preparation
2.1 Advance Preparation Using the Protocol Manager
2.2 Preparation for Multimedia Data Acquisition3. Hardware Components and Assembly
3.1 Suitcase and Components
3.2 Color Quad Processor
3.3 Vanguard Pan/Tilt/Zoom Cameras
3.4 XCam2 and WideEye Wireless Video Cameras
3.5 Wireless Video Receivers
3.6 Wireless Microphone Transmitters and Receiver
3.7 Boundary Microphone
3.8 Camera Stands4. Technical Data Collection on the Day of Testing
4.1 Preparation & Documentation of Data Acquisition using the Protocol Manager
4.2 Using SVDA to Collect Data
4.3 Troubleshooting with the MUA-Lab
4.4 File Naming Protocol
4.5 Post-Activity Questionnaire & Video Review with the Protocol Manager5. Technical Data Analysis
5.1 Using the PM for Survey Data Compilation and Comparison
5.2 Using Adobe Premiere-Based Tools for Video Editing
5.3 Using Dr. DivX for Compressing Video Files to DivX Format (mpeg4)
5.4 Using MVTA for Event-Based Ergonomic AnalysisAcknowledgement
Appendices
A.1 Photographs of Hardware Components
A.2 Detailed Table of Hardware Components
A.3 Wiring Diagram for Hardware Setup
A.4 Selected Hardware Component Tech Sheets
A.5 Advanced Hardware Settings
A.6 Using Adobe Premiere v6.5 for Video Editing
A.7 Protocol Manager Backend Instructions
1. Introduction
1.1 Background
The Mobile Usability and Accessibility Lab (MUA-Lab) is a tool developed by the Rehabilitation Engineering Research Center on Accessible Medical Instrumentation (RERC-AMI). The MUA-Lab is designed to perform usability analyses of medical devices used by individuals with diverse abilities. The system integrates data collection hardware and software with a Protocol Manager (PM) that helps facilitate problem identification, planning, data collection and data analysis across the continuum of medical instrumentation analyses. The MUA-Lab is an all-inclusive research lab that has been specifically designed for detailed product accessibility and usability analyses in multiple locations in the greater Milwaukee area (based at Marquette University) and San Francisco Bay area (based at the University of California Ergonomics Lab).
1.2 MUA-Lab Design Criteria and Specifications
The MUA-Lab meets several design criteria established by the team in that it is portable, lightweight, reliable, and easy-to-use for conducting accessibility and usability analyses. The system synchronizes real-time collection of video, audio and sensor data using Synchronized Video Data Acquisition (SVDA) software (see Section 4.2). All of the hardware components fit into one standard carry-on suitcase that includes the laptop and laptop case. The hardware components are securely housed within foam packaging for adequate protection during travel and several models of video cameras, camera stands and microphones are available to accommodate different research requirements.
Some of the wireless cameras can be tethered with video cables, for situations where wireless communication is not permitted. Audio is collected through the microphone port of the laptop via a multi-channel wireless microphone system or via a tethered boundary microphone. A data acquisition card (16 channels analog, 8 channels digital I/O) and light-emitting diode (LED) video signaling are available options for sensor data collection. SVDA must support the data acquisition card for the software to successfully capture sensor signals. Several National Instruments cards (NI-DAQ, PCMCIA port) and their associated drivers are currently supported.
1.3 General Design of the Protocol Manager
A Protocol Manager (PM) is included within the MUA-Lab, which is a web-based software product (available on the Internet at http://rerc-ami.org/D1Three/UserLogin.aspx, implemented in ASP.Net, C# and XML in the Microsoft Video Studio .Net environment). The PM guides the multi-site research team and on-site experimenters through all stages involved in performing accessibility and usability analyses. Although it is not necessary to use the PM with the MUA-Lab, it is recommended to help ensure a thorough and consistent research methodology.
The PM guides the user through various procedures, including: formation of a research problem statement, understanding all aspects of instrument usage, universal design analyses, pre-screening and tracking of subjects (both healthcare patients and practitioners), activity performance observations during data collection, post-activity interviews of subjects, post-activity data analysis and documentation, and data tracking for each targeted medical device. The PM also includes tools to summarize the pre-activity and post-activity questionnaire data.
The PM can be implemented on a single computer without an Internet connection (where data is stored on the computer’s hard drive) or online at http://rerc-ami.org/D1Three/UserLogin.aspx when an Internet connection is available (where data is stored directly to the network database). Each PM page contains several buttons on the bottom of the page for site navigation and saving, including:
• Clear Changes: reverts information on page back to last saved version.
• Save: saves current information on page.
• Save and Lock: protects data from being accidentally overwritten by locking out further changes on page.
• Previous Page: navigates browser page to previous page in outline.
• TOC: navigates browser page to the main table of contents page.
• Next Page: navigates browser page to next page in outline.Figure 1.1 below shows the file structure of the PM, including the hierarchy of IRB study, parent device, and children devices. See Appendix 7 for more detailed descriptions of the data stored in each file and to learn how to duplicate data from one section of the PM to another (for more efficient data entry of similar information for more than one child device). It should be noted that most of the PM data is stored under the child device level.
Figure 1.1: File Saving Hierarchy Structure for the Protocol Manager.
2. Advance Preparation
2.1 Advance Preparation Using the Protocol Manager
Before collecting any data in the field with the MUA-Lab, the researcher has the option of taking advantage of the Protocol Manager (PM) to develop and organize the details surrounding a particular research protocol. The PM is an integral part of MUA-Lab when it is used as a comprehensive accessibility tool. First, it helps manage a research study because it is organized by the IRB number associated with a medical instrumentation study, and it helps coordinate, implement and document the data associated with the study. Secondly, it provides a structured way to screen for subjects and to determine if any accommodations are needed for their participation. Finally, it provides structured methods to conduct universal design analyses of medical instrumentation and pre- and post-activity scoring instruments that complement the task-based analysis tools.
The advance preparation component of the PM is discussed within this section, including all of the PM sections that are completed prior to the human subject data collection session. Each page is intended to be filled out in the order it appears within the table of contents.
- Section I: Problem Statement. This form is used to identify the IRB study and other high level information about the study to be conducted. The IRB approval number, title Primary Investigator (PI), and access problem to be investigated are requested. The "Check" buttons on this page are used to verify that the unique identifiers entered for the study (i.e., IRB and shortened Parent codes) are not already being used in another study.
- Section II: Advance Preparation. This form cannot be completed prior to completing Section I (Problem Statement). This page details the medical devices to be evaluated in the selected IRB study and the tasks to be performed by subjects. By default, a child device with the same name as the parent device is generated. Users need to create a unique identifier for each child device if more than one child device under a parent class is tested.
- Section IIA: Understand Instrumentation Usage. This form documents practical aspects of the medical device(s) under study, such as the medical facilities to be used for testing, the manufacturer’s intended and expected uses, an estimate of the intended and actual conditions of use at the facility(s), and range of product uses. This page asks for the name of the children instruments if more than one type of the parent instrument will be tested. For example, a parent label could be EXAMTABL and children labels could be EXAMTABL1 and EXAMTABL2.
- Section IIB: Universal Design Analysis (patient and provider perspectives for each child device). These sections are motivated by the Principles of Universal Design, and include questions to identify the: sensory, cognitive, and physical usability (e.g., ease of use for a patient/provider who is hard of hearing, deaf, blind, ease of understanding how to use a device, ease of use for a person who is very tall or short, has large or small hands, can only use one hand); assistive technology accommodation (e.g., ease of use for a person using a cane/crutches/walker, manual/powered wheelchair); error tolerance (e.g., device safety from damage, user safety from injury, device tolerance of mistakes); and equitable use (e.g., whether every user finds at least one way to use it without stigma).
- Section IIC: General Requirements for Test Subject Performance and Data Collection. This form documents the desired type of test participants to test the child instrument (e.g., quantity, ability characteristics, experience level), tasks and number of repetitions to be conducted, and data collection tools needed for the research sessions. This form also documents if the usability testing video will be reviewed with subjects after testing to obtain feedback on their experiences with the device.
- Section IID: Conduct Pilot Tests. This form documents the pilot testing to be completed prior to bringing actual subjects in to test the devices, in order to ensure smooth testing on the actual testing day. Pilot testing helps researchers fine tune details such as camera placement, understanding how to administer the subject assessment scales, and final selection of the pre- and post-activity questions.
- Section III: Pre-Activity Subject Interview(s)(patient and provider). These forms are used to help recruit subjects for testing. They are typically completed over the phone, and they are used to document responses from potential subjects. There are extra sections at the end of the forms to add additional questions, so it is necessary to review the form and modify it before beginning subject recruitment.
- Section IIIA: Pre-Activity Patient Interview Forms. This questionnaire is used to collect pre-screening information from patient subjects participating in the study. It is used to document demographic data (e.g., gender, race, education), disabilities (e.g. vision, hearing, paralysis), functional difficulties (e.g., reaching, grasping, unintentional tremor), previous experience with the type of device being tested, and assistive technology use (e.g., cane, walker, wheelchair).
- Section IIIB: Functional Assessment-Scale and Sub-Scale Selection. This form is used to add and define functional scales (e.g., Fugl-Meyer, VFQ-25) that will be used to assess subjects in the study. If an additional scale is selected, at least one sub-scale must be selected with the additional scale chosen. This page is completed once for patient subjects and once for provider subjects; once the information is saved and a subject record is created, the form cannot be modified.
- Section IIIC: Functional Assessment-Patient. This page documents the patient subject’s scores of the Fugl-Meyer, VFQ-25, and any additional scales that are defined by the researcher in Section IIIB.
- Section IIID: Pre-Activity Provider Interview Form. This questionnaire is used to collect background information from provider subjects participating in the study. It is used to document demographic data (e.g., gender, race, education), disabilities (e.g. vision, hearing, paralysis), functional difficulties (e.g., reaching, grasping, unintentional tremor), previous experience with this type of device, provider experience level treating patients with specific conditions (e.g. vision impairment, hearing impairment, arthritis) and assistive technology use (e.g., cane, walker, wheelchair).
- Section IIIE: Functional Assessment-Provider. This page documents the provider subject’s scores of the Fugl-Meyer, VFQ-25, and any additional scales defined by the researcher in Section IIIB.
- Section V: Post-Activity Subject Questions-Gateway. This section is completed before subjects arrive for testing, in order to define the post-activity interview questions that subjects will be asked after they use each device. The form is completed separately for patient and provider subjects. This form is used to select or unselect predetermined questions to be included in the post-activity survey. Additional questions can be added to this form in addition to the questions created in Section IIB (Universal Design Analysis) that automatically appear in the post-activity forms. Once the questions are selected and this form is saved, questions in the post-activity interview forms will be locked.
All of the above data are entered directly into the PM, using the software version on either the web (http://rerc-ami.org/D1Three/UserLogin.aspx) or the local computer. The user must first have a username and password, which are allocated and managed by the RERC-AMI (Contact Dr. Jack Winters). If an Internet connection is available, the PM can be accessed directly on the Internet, in which case the data collected during the research session can be stored directly online. Otherwise, the information is stored locally and the MUA-Lab computer acts as the server until the data is uploaded to the network database.
Figure 2.1: Suitcase Layout and Key Components of the MUA-Lab
2.2 Preparation for Multimedia Data Acquisition
Figure 2.1 displays the MUA-Lab carrying case with each hardware component labeled. All hardware components that can be selected for inclusion in the MUA-Lab are listed in Table 1 below (see Appendix 1 for photographs of each component). In special cases, alternative cameras, camera stands, or specialized sensors may be needed. After doing a component check, battery charges also should be checked.
Hardware Components
Description
Quantity
Quad Processor
Up to 4 RCA Inputs to 1 Composite Video Output
1
Vanguard Pan/Zoom/Tilt Camera
Color Wireless or Tethered Video Camera
2-3
X10 XCam2 Camera
Color Wireless Video Camera
2
X10 XCam2 WideEye Camera
Wide Angle Wireless Video Camera
2
X10 Wireless Video Receivers
2.4 GHz Wireless Video Receiver
3
Wireless Microphone Transmitter
Wireless Lapel Microphone
2
Wireless Microphone Receiver
Discrete Two-channel VHF Receiver
1
Omnidirectional Boundary Microphone
RadioShack brand Boundary Microphone
1
Manfrotto Micro Tripod 714SHB
Compact Tripod ( Height Range : 12.7"-47.7")
1
Manfrotto Mini Tripod 714B
Tripod ( Height Range : 16"-64.1")
1
XCam2 Tabletop Tripod
Classic and/or Da Vinci Models
1
Super Clamp and Articulated Arm
Clamping Arm with 3 Degrees of Freedom
1
3. Hardware Components and Assembly
The hardware components of the MUA-Lab and instructions for their use are described below. For more detailed specifications of the system components, including model numbers and manufacturer information, refer to Appendices 1-5.
3.1 Suitcase and Components
All of the MUA-Lab hardware components fit within a standard carry-on suitcase (approximately 9"x14"x22"), as shown in Figure 2.1, and the laptop is carried in a separate case that can be stored in the larger suitcase, if desired. The suitcase is protected with hard plastic shielding and contains a customized foam insert to secure the hardware components during travel. All of the hardware has specific locations within the suitcase that are labeled for easy identification. Several pockets within the case (within the top opening side) house the cables and remote controls. A zipper feature on the suitcase expands the top section of the suitcase to increase the depth by approximately 3" to accommodate extra equipment and the lightweight backdrop, if needed. A laminated copy of the Quick Start, System Diagram and Pocket Inventory are included in the front pocket of the suitcase to help set up the hardware in the field, and there is also a link to each of these documents within the PM.
3.2 Color Quad Processor
Because the SVDA software currently supports only one video input for data collection, the Grand Magic Guard II color quad processor is used to compile multiple video inputs into one output (for input into the laptop). The quad processor supports input from up to four separate video cameras (connected with standard RCA video cables) and one real-time composite video is outputted for collection with SVDA (with an RCA to USB adapter cable).1
The quad processor must be powered by an electrical outlet and an AC-DC adapter that plugs into the “DC IN” port on the back of the unit. There is also a "VIDEO OUT" channel located on the back of the unit that should be connected to the RCA-to-USB converter and then into the USB port of the computer. RCA connection cables from up to four video cameras can be inserted into the ports on the side of the quad processor labeled "VIDEO IN1" through "VIDEO IN4". The power switch on the side of the unit should be turned on and off with each use, and the "NTSC/PAL" toggle switch should be set to "NTSC" for normal data collection.
Several display modes are available with the quad processor, depending on the research requirements and the number of cameras in use, including modes to view a single video feed, two video feeds via Picture in Picture (PIP), or up to four video feeds with a quadrant display. Either the remote control or the buttons on the front of the quad processor can be used to switch between the different modes. More advanced settings can be used to display the time, date and/or separate channel names (see Appendix 5).
3.3 Vanguard Pan/Tilt/Zoom Cameras
The Vanguard Pan/Tilt/Zoom camera can be used either wirelessly (with the video receiver plugged into the quad processor) or tethered with a standard RCA video cable (plugged directly from the camera into the quad processor). An AC-DC adapter and power supply is required for the camera to operate, which is plugged into the back of the camera and a standard electrical outlet. A remote control is used to adjust the camera settings and to pan, tilt and zoom. Left, right, up, and down buttons control the panning and tilting positions of the camera, and a center button moves the camera back to its centered home starting position. (It is suggested that the Vanguard camera be realigned with the center button before turning the power off and stowing it in the suitcase.) There are also "Zoom In" and "Zoom Out" buttons, an "Iris" button to adjust the amount of light that enters the lens, and "Auto Focus" and "Manual Focus" buttons for adjusting the focus automatically and manually.
3.4 XCam2 and WideEye Wireless Video Cameras
The XCam2 and WideEye cameras have the same basic components but different lenses, with 60° and 120° field of views, respectively. These wireless cameras have a manual focus option, which is adjusted by turning the rim around the lens either clockwise or counterclockwise. The cameras can be powered wirelessly with 4 AA batteries in the supplied battery pack (attached to the bottom of the cameras), or with an AC-DC adapter and power supply (see Appendix 4 for manufacturer supplied tech sheet). Several hours of video can be collected with fully charged batteries, but it is important to make sure that the batteries are fully charged before each use. Each wireless camera and its corresponding receiver need to be tuned to the same frequency for successful use. The camera frequency is adjusted with the switch on the top of the camera (under the black oval insert). Only channels A and D are labeled, and channels B and C are located between these extremes. To achieve the best signal quality, the wireless camera and receiver pair should be placed as close as possible with the dot on the camera antenna facing the squares on the receiver antenna.
3.5 Wireless Video Receivers
If multiple video signals are being transmitted wirelessly, a separate video receiver must be used for each camera. Each video receiver requires an AC-DC adapter and electrical supply to operate and there is a power switch on the side of the receiver and a red LED on the front to indicate when the power is on. The appropriate number of receivers should be connected to the four available channels of the quad processor (plugged into the "VIDEO IN1" through "VIDEO IN4" ports) using standard RCA video cables.
Each camera and receiver pair must be tuned to the same channel, which is different from all other camera/receiver channels being used. The channel switch (A, B, C or D) is located on the bottom of the receiver and the camera switch locations are dependent on the model. The Vanguard Pan/Tilt/Zoom camera has a channel switch on the bottom, and both models of the XCam2 wireless cameras have switches on the top of the unit (under the black rubber insert).
The receivers can detect a signal from a camera that is located up to 100 feet away, although the highest quality signal is obtained when the receiver is placed near the camera. Once the camera and receiver are placed in their desired locations within the experimental environment, the antenna pairs should be adjusted to face each other. The side of the camera antenna with the dot should face the receiver antenna with the four squares and the positions can be adjusted until the optimal picture quality is achieved.
3.6 Wireless Microphone Transmitters and Receiver
A discrete two-channel wireless microphone system is included in the MUA-Lab to enable audio collection, if desired (see Appendix 4 for manufacturer supplied tech sheet). Each of the microphone transmitters and the microphone receiver require a 9V battery to operate. The microphone may be clipped directly onto a subject and/or a researcher, which is helpful in noisy environments. For the best performance when using both wireless transmitters at once, a distance of at least ten feet should be maintained between the transmitters and receiver. The microphone receiver should be plugged into the microphone port of the computer and it is also recommended that the receiver antennas be positioned first straight up, and then angled out slightly so the angle is never more than 45 degrees from vertical.
Each microphone transmitter has a power/frequency switch on the top of the unit, which is used to turn the power "on" and "off" as well as to select an operating frequency for the transmitter. When the microphone transmitter is switched to "F1" or "F2," a red LED will illuminate, indicating that the battery is good. The receiver power must be switched on for either one or both channels, depending on the number of microphones in use. The microphone system operates in the 169-172 MHz bandwidth, where interference is minimal, and either of two transmission frequencies can be selected (F1: 169.445 MHz or F2: 170.245 MHz). To check the quality of the audio signal, a pair of headphones can be attached to the laptop or the laptop can be un-muted so a sound check can be performed.
To check the amount of interference within the research environment before collecting data:
- Make sure the microphone transmitters are powered off.
- Turn on both of the microphone receiver switches (F1 & F2).
- Both LED’s should turn red. If either or both of them turn green then there is RF interference in the area, which may affect the quality and performance of the microphone system.
3.7 Boundary Microphone
A boundary microphone is available to enable audio collection within a room without having to attach a microphone transmitter to subjects. The omni-directional microphone can pick up audio in the hemisphere above and in front of the mesh area, but not below or behind it. Therefore, to get the best quality audio, the microphone should be placed as close as possible to the audio source with the front of the microphone facing the audio source. The microphone plugs directly into the microphone jack of the laptop. To check the quality of the audio signal being collected with the boundary microphone, a pair of headphones can be attached to the laptop or the laptop can be un-muted to perform a sound check.
Items to note about the boundary microphone:
- A battery is required to power the microphone, and it should be powered off after each use.
- Avoid placing the microphone on soft surfaces (e.g., carpet) because some sound may be absorbed and the quality of the recorded signal will be degraded.
- Attempt to leave at least 1 foot of clear space around the microphone.
3.8 Camera Stands
Several camera stands can be included within the MUA-Lab, and all of the cameras have the necessary screws to secure the cameras to the stands. Up to 3 camera stands can be included in the carrying case, although several of the tripods have bags so they can easily be carried separately. The height range for each camera included in the MUA-Lab is listed in Table 2 below.
Table 2. Camera Stand Height Range
Camera Stand Model
Height Range
Micro Tripod
12.7’-47.7"
Mini Tripod
16"-64.1"
Tabletop Tripod
7.5"
4. Technical Data Collection on the Day of Testing
This section describes the technical data collection process that occurs during actual usability testing with subjects. There are normally two components of data collection: data collected with the Protocol Manager (PM), if used (e.g., universal design assessment of device(s), subject questionnaires, recording of observations), and data collected using Synchronized Video Data Acquisition (SVDA) software (e.g., audio, video and possibly sensor data files).
4.1 Preparation for Data Acquisition Using the Protocol Manager
The optional Protocol Manager (PM) software is installed locally on the MUA-Lab laptop, and it is also available on the internet at http://rerc-ami.org/D1Three/UserLogin.aspx. Data are automatically stored within a folder structure (as XML files), and data are readily available for further review in the field. Normally the on-site researcher runs both the PM and SVDA software (see Section 4.2) on the same laptop computer, with the PM serving to structure the data collection processes during the research session. If an Internet connection is available, the PM can be accessed directly on the Internet, in which case the subject survey data collected during the research session is stored directly online. Otherwise, if the information is stored locally, the MUA-Lab computer acts as the server until the data are uploaded to the online server.
If the PM is used during the advance preparation phase (see Section 2.1), then it is available to the on-site researcher as a resource that can be used to help implement the sequence of tasks that are part of the testing protocol. The PM can be used to record on-site observations and document file names (see Section 4.5), and then after data collection, to collect post-activity interview data (see Section 4.6).
The following PM sections are completed on the day of testing, before or immediately after subjects use the device under investigation:
- Section IV: Activity Preparation and Documentation. These sections are completed on the day of testing with subjects present. Section IV pages serve as a checklist to verify that various aspects of the study are conducted in the same manner for each subject.
- Section IVA: Pre-Activity Preparation. This section should be completed prior to the subject’s appointment by the investigator. This page helps verify that the testing environment is prepared for the subject, including the equipment setup, software operation, supplies needed for the subject, etc.
- Section IVB: Activity Performance Observation. This section is used to introduce the subject to the testing environment. Any concerns of the subject should be noted here. The signed informed consent document is also noted here. The researcher is reminded to allow the subject to become familiar with the device under investigation and to note any subject comments or concerns. Then the testing protocol is begun using the protocol created in Section II. After data collection, all files should be carefully named and documented for future reference..
- Section IVC: Documentation and Monitoring of Data Collection and Storage. This page is used to review the data obtained and to ensure the video file quality and size are sufficient. Once the quality and size are verified, the file names should be listed in the text box.
4.2 Using SVDA to Collect Data
Synchronized Video Data Acquisition (SVDA, NexGen Ergonomics) software is used to simultaneously collect the video, audio and sensor data. It supports a wide range of compression algorithms (e.g. DivX; Microsoft Video 1). Several other software tools are available for subsequent data reduction and analysis, including Multimedia Video Task Analysis (MVTA®) for ergonomic task analyses and several video editing cards (i.e. Canopus DVStorm2 and Matrox RT.X100) used with Adobe Premiere for enhanced video editing capabilities.
The following steps are used to configure and use SVDA for data collection:
- Open SVDA after the desired cameras, sensors and microphones are set up (see Section 3). Make sure the software key is in the computer.
- SVDA is automatically set to "Preview Data" with "No Video". To change these settings, use the scroll menus at the bottom of the SVDA window labeled "Data Mode" and "Video Mode." To preview or record sensor or video data, click on the "Start" button to the left of the scroll menus.
- Select "Preview" to view the data and/or video streams without creating any files (when testing the camera placement(s) and signal quality).
- Select "Record" to collect/create data and/or video files (when researcher and subject(s) are ready to collect usability data).
- Select the "Video" menu and then "Change Settings" at the top of the SVDA window to change the video settings (i.e., compression mode, compression type algorithm, video size, storage path)
- If an error occurs, such as "access violation at address….", click "ok" and exit SVDA, unplug the USB video connection, plug it back in and make sure a proper connection is established, and then restart SVDA.
- The following recommended settings should be used for normal collection with the MUA-Lab:
- Select "compress. mode": "on the fly". With "on the fly" compression, the video/data preview window only refreshes once every few seconds, but this does not reflect or affect the quality of the data collected.
- Note: Selecting "no" leaves the video in raw .avi format (approx. 600 MB/min). Selecting "after capture" causes the video to be captured initially within a raw .avi format, and then SVDA uses computational resources to encode the video to the selected format after data collection is ended. The process of encoding "after capture" can take up to 3-4 times as long as capturing the video. Thus, a 30-second video file can take up to 2 minutes to encode. Also, when using "after capture" encoding, SVDA temporarily writes a raw .avi file to the hard drive (600MB/min).
- To capture audio, check the "capture" box under the "Audio source" menu on the right side of the screen. Select "Microphone" from the "audio input" menu, and select the appropriate "format" (8000Hz, 16-bit Mono recommended for normal collection).
- Select the appropriate compression algorithm from the "video compressor" menu, which will be used to compress the video and/or audio files. "DivX Pro(tm) 5.2.0 Codec" (mpeg4) is recommended for normal collection. This will produce excellent quality video using a more aggressive compression. (See Table 3 below)
- Note: the displayed codec list is automatically generated from SVDA by determining the video codecs and associated drivers available on the computer. To add more codecs, install the codecs and associated drivers and then restart SVDA.
Table 3. Codec Settings and Results
Codec
Average Dropped Frames/sec
- Select the appropriate compression type (i.e., video, audio, or audio+video) using the menu next to the compress. mode. When collecting audio and video, compress both the audio and video data by selecting "audio+video", otherwise select "video".
- Adjust the "video size" if desired (640x480 recommended for normal collection).
- Insert a "storage path" name to save files in a location other than the default (D:\MVTA).
- Note: file names cannot be changed until data collection is stopped. Typical file names have the following format: "data040106_110176_538.***", where the file extensions (indicated with ***) are either "bdf" for data files or "avi" for movie files.
4.3 Troubleshooting with the MUA-Lab
- If there is an error displayed within SVDA:
- check the USB video input connection and make sure all hardware is powered and connected
- restart SVDA and/or the computer
- If there is significant interference with the wireless cameras:
- check the battery power
- make sure the camera/receiver pair is tuned to the same channel
- relocate one or all of the receivers so they are as far away from each other as possible
- realign the camera/receiver antenna pair(s) so they are as close together as possible
- If the video feed(s) do not display properly:
- Make sure the power is to all hardware devices (cameras, quad processor, and microphone) is switched to the "on" position.
- Power the quad processor "off" and then back "on". Check the RCA video cable connections and rotate them in the port, if necessary.
- Shut down SVDA and/or the computer after checking the USB video input connection and making sure all of the hardware is properly connected and powered.
- For troubles with the boundary microphone:
- Make sure the power switch is "on" and the battery has charge. Replace if necessary.
4.4 File Naming Protocol
A standard format has been established for naming and storing the files produced during a research session and the following definitions and format are used in naming the raw data files:
Definitions:
- Equipment identifier: Unique alpha-numeric (no more than 8 characters) to identify the equipment model (child) being tested.
- Subject type identifier: Label to identify the type of subject involved in testing.
- PAT : Healthcare Patient subject who uses or on whom the equipment is used.
- PRV : Healthcare Provider subject who uses the equipment.
- Subject numeric identifier: Unique numeric code (i.e. 1000, 2000) for anonymous subject identification.
- Session: Each time period during which a specific subject tests a specific piece of equipment.
- Task: Each activity the subject performs on or with the equipment is a separate task. Subjects may perform multiple tasks on a single piece of equipment.
- Examples:
- For an exercise study: Take baseline vital signs, get onto exercise bike, use exercise bike, record vital signs, get off of bike, measure vital signs, and report vital signs.
- For a positioning study: Get onto dental chair, position as needed to receive dental services, and get off of dental chair.
- Trial: Each time a subject performs a task on or with a device(s) is a trial. Subjects may perform multiple trials of a single task.
Raw data file-naming format (for when the researcher is in the field):
- Equipment identifier (8 letters/digits per device)2
- Subject type identifier (3 letters: e.g., "PAT" for patient or "PRV" for provider)3
- Subject numeric identifier (4 digits)
- Session identifier (2 digits)
- Task identifier (1 letter)4 (optional)
- Trial identifier (2 digits)5 (optional)
Each of the identifiers (except for the PAT/PRV and subject identifier codes) should be separated with an underscore (_), while multiple subject and equipment identifiers within the same category should be separated with a dash (-).
Examples:
- EKGM4530_PAT1001-PRV1002_ 01_A_01 for a simple session involving a patient and provider 3, one device, one task and one trial.
- ERBL1593-MSBR8901_PAT1001-PRV1002_ 01_Z_99 for a session involving a patient and provider 3, several devices 2, several tasks 4 and several trials 5.
Reduced data file-naming protocol (for post-processing analysis):
When a video file is edited in an analysis procedure, all subject identifiers, equipment identifiers and task identifiers that are not included within the analysis should be removed from the file extension. This means the same video clip may be stored in more than one location (under the child), depending on the analyses and editing that are done for a given usability analysis.
Examples:
- A raw data file with the name EKG4530_PAT1001-PRV1002_ 01_A_01 may be reduced to EKG4530_PAT1001_ 01_A_01 if the analysis is only related to PAT1001.
- ERB1593-MSB890_PAT1001-PRV1002_ 01_Z_99 may be reduced to ERB1593_01_PAT1001_ A-B_01-02 if the subsequent analysis is only related to PAT1001 using the ERB1593 for tasks A and B and Trials 1 and 2.
4.5 Post-Activity Questionnaire in the Protocol Manager
After a subject attempts to conduct the desired sequence of tasks, the researcher has the option of using the PM to conduct a structured interview. The post-activity questionnaire complements video-based data collection of subject performance by systematically assessing the subject’s opinions of the accessibility and usability of the device(s). The following PM sections are completed after subjects use the medical device under investigation:
- Section IVD: Review Video. This section is used to guide the researcher in reviewing the usability video data with subjects, if this is an appropriate step in the protocol. Researchers may use this tool to better understand the thoughts and actions of subjects at specific time instances within the video (e.g., when a subject appears to have difficulty moving to a particular position but explains they are not having difficulty). The subject can narrate the video and the investigator can clarify the subject’s reasoning behind specific actions throughout the video clips. A text box is provided for any necessary documentation.
- Section VA: Post Activity Patient Interview Form. This form is used to document patient subjects’ opinions on using the medical device under investigation. The questions are pre-selected in Section V (Post-Activity Subject Questions-Gateway) prior to subjects coming in for testing. The post-activity survey consists of questions that cover the following areas: sensory, cognitive, and physical usability, error tolerance, safety/comfort, and AT accommodation. Many of the questions within the post-activity questionnaire are similar to the universal design questions (in Section IIB of the PM; see Section 2.1 above), with an emphasis placed on the subjects’ impressions of their experiences during the testing session. The core set of questions are designed to apply to any type of medical device, and the researcher can also add up to 8 customized instrumentation-specific questions. Open-ended comments are also recorded at the end of each area (e.g., sensory usability, cognitive usability).
- Section VB: Post Activity Provider Interview Form. This section is the same as for Section VA (Post Activity Patient Interview Form), except it is targeted to provider subjects. The questions are pre-selected in Section V, prior to subjects coming in for testing.
- Section VC: Comparison of Instruments. This form is used to document subjects’ comparative preferences if two or more child instruments are tested for a parent device. Comparative rating and ranking questions are included in the form, along with text boxes to record open-ended responses.
5. Technical Data Analysis
5.1 Using the PM for Survey Data Compilation and Comparison
The PM can be used to automatically compile the survey data collected during testing. The following pages are included to help researchers quickly organize their data in multiple formats for comparison:
- Section VI: Post-Activity Data Analysis. This section provides a comparison of the subject interviews by summarizing all of the pre- and post-activity data.
- Section VIA: Pre-Activity Patient Interview Summary. This page provides a comprehensive summary of all data obtained from patient subjects during the pre-activity interviews in Section IIIA.
- Section VIB: Functional Assessment-Patient Summary. This page provides a comprehensive summary of all data obtained from patient subjects during the functional assessment scale documentation in Section IIIC.
- Section VIC: Pre-Activity Provider Interview Summary. This page provides a comprehensive summary of all data obtained from provider subjects during the pre-activity interviews in Section IIID.
- Section VID: Functional Assessment-Provider Summary. This page provides a comprehensive summary of all data obtained from provider subjects during the functional assessment scale documentation in Section IIIE.
- Section VIE: Post-Activity Interview Summary: by Instrument. This page summarizes the post-activity interview questionnaires (Section VA and VB) from all patient and provider subjects according to the instrument selected.
- Section VIF: Post-Activity Interview Summary: by Subject. This page summarizes the post-activity interview questionnaires (Section VA and VB) from each instrument for the selected patient or provider subject.
- Section VIG: Comparison Summary: by Instrument. This page summarizes the instrument comparison survey completed in Section VC for all test subjects per instrument selected.
- Section VIH: Activity Performance Video Analysis. This page includes a text box for any notes/documentation of the video analysis throughout the experiment.
5.2 Adobe Premiere-Based Tools for Video Editing
Digital video editing cards offer extra power when editing video files created with SVDA/MVTA. These cards are available only in PCI format and therefore can only be used in a computer system that has an extra full-size PCI slot. This would usually restrict these cards to only working in a desktop system with a tower case but there are expansion cases that can be connected to a laptop that can hold 1 or 2 full-size PCI cards (e.g., http://www.mobl.com/expansion/pci/2slot/). One major drawback with this option is that they add considerable bulk and weight to the portable system.
Editing the MUA-Lab video files may require extra features not currently offered in MVTA, such as blurring a subject’s face, rearranging the timing and sequence of events, or adding extra audio or digital comments. These can all be accomplished using Adobe Premiere (AP) version 6.5 with a recommended digital video editing card. The following cards are known to provide the additional editing needs that MUA-Lab users may need or want:
- Matrox RT.X100 (http://www.matrox.com/video/products/rtx100xtreme/home.cfm)
- Canopus DVStorm2 (http://www.canopus.us/US/products/dvstorm_2/pm_dvstorm_2.asp)
AP is built so the cards can be installed and then it automatically utilizes the processing power of the added cards for editing video files. Therefore, the time it takes AP to "render" the movie files is decreased. Rendering refers to the process of making digital changes to the original video file. Since video files usually contain a lot of information, on the order of hundreds of megabytes to several gigabytes, using the computer's CPU and memory alone could mean waiting up to several hours for the new video file to be created. These digital video editing cards offer a tremendous boost to productivity in video editing by increasing the processing power. Their main chipsets are specifically built to handle video editing, instead of the more general operations that the CPU is built for. They also provide many additional features that are not found in AP, although not all of these functions are useful to the MUA-Lab.
Several tutorials are available online to help guide the user through some standard video editing processes.
Note: the learning curve of AP is about 3-10 hours (depending on the user) and people with vision impairments may find the many small buttons of AP unusable.
5.3 Using Dr. DivX for Compressing Video Files into DivX Format (mpeg4)
Anytime Adobe Premiere is used to edit a video the video must be recompressed using Dr. DivX. Also, if a video file is not compressed during or after collection with SVDA, it is recommended that the video be compressed before storing it on a computer due to size and storage constraints.
To compress video files using Dr. DivX software:
- Open Dr. DivX, located in the "Start" menu under the folder "DivX."
- Choose to open a "Video File" and open the video file to compress. After Dr. DivX analyzes the video, a window entitled "Select Audio Input" will appear. Select the option "Track in video input" and click "Next". The next window that opens is labeled "Choose Output." On the left is the "Certification Level", which is automatically checked. Uncheck this option now.
- "Encode the DivX Video to:." will appear. Select "Make a High quality file." and then select "Next". The next window should be entitled "Encode Video." The output filename can be changed here as well as the destination by clicking the "Select" button.
- The output line reads "DivX: 1000kbs." Change this output rate to 500 kbs by clicking on the "Modify Settings" button. An additional window entitled "Preview" will come up. Ignore this for now.
- Note: if it is desired to only include certain parts of the movie in the final output, this is where to select the start points (i.e., "Mark In") and stop points (i.e., "Mark Out"). Several smaller portions from any point within the video can be used to make a final one, therefore any down-time within a video file can be removed with this tool.
- Go to the "Basic Settings" window. If the "Resize" tab is checked it should be unchecked now (so the original size of the movie is not changed). Now select the "Advanced Settings" button. In the top left corner of the "Advanced Settings" window there should be a slider bar with an input box entitled "Average Bitrate". Use either of the input tools to change the value from 1000 to 500. Leave all the other settings the same.
- If all of the setting changes seem okay, select the "Encode" button located at the bottom right of the window to make the encoded (compressed) movie file.
- Note: Encoding video files takes all of the available system resources so it is impossible to do anything else with the computer until it is finished encoding.
- When it is done encoding, play the video to make sure it is of high quality. Then, either click "Next" to convert another video or quit Dr. DivX.
5.4 Using MVTA for Event-Based Ergonomic Analysis
Multimedia Video Task Analysis (MVTA, NexGen Ergonomics) is used for data and task analysis procedures, specifically interactive time and motion analyses of video recorded activities by researchers. In general, MVTA is used to identify events with terminal break points during a timed activity for usability analyses. Video and sensor data collection is synchronized so it can all be viewed on the same timeline during video playback, and it is possible to replay video files at any speed (i.e. real-time, slow motion, fast motion or frame by frame) in both the forward and reverse directions. Replaying an event in a continuous loop or displaying an arbitrary event or point in time are other features that can also be controlled. MVTA can also be used to produce conventional time study reports and the frequency of occurrence of any particular event as well, which may be helpful in usability analyses.
The main program window appears when MVTA is started, and it is necessary to choose between two analysis types: Task Analysis or Data Analysis. The Task Analysis option is used to view and analyze video data and the Data Analysis option is to view and analyze sensor data.
Note: for a more detailed discussion about the basic functions of the MVTA software, please refer to the MVTA User’s Manual.
A standard protocol and template has been created for conducting medical device usability analyses with MVTA. The following is an outline of the definitions and protocol developed for the RERC-AMI.
Some definitions for clarity:
- FILE: an MVTA document for a single subject (e.g., either patient or healthcare provider). It is important to decide in advance which individual is being observed.
- RECORD: a collection of window-events that are grouped together on a timeline according to an overall theme, such as a type of barrier to use (see section III below).
- WINDOW-EVENT: an event identifier (e.g., mild, moderate, extreme, or null; see section III below). The duration of a window-event is defined by breakpoints at the beginning and end of the event.
- BREAKPOINT: a graphic marker used to tag the beginning or end of a window-event.
The default set of MVTA RECORDS and EVENTS for all usability analyses :
- Default RECORDS and their definitions:
- Orienting/positioning body or device barrier – consider: dynamic support needs, such as at setup/beginning and end of device use, e.g., transferring, body balance or stability, physical obstruction, movement requirements, reaching, strength requirements, etc.
- Body support barrier – consider: static support needs for body or extremities without which there is loss of stability or fatigue, e.g., seat, back, leg, arm, head support.
- Physical interaction/manipulation/operation of controls barrier – consider: physical interactions with controls (e.g., switches, levers), reaching, handling, strength, dexterity, motor control, physical obstructions to hands (or other appropriate body part), etc., during use.
- Sensory barrier with communication or display – consider: device exceeds sensory capabilities for vision, hearing, touch, etc. (e.g., sight lines, letter size, sound volume, ambient noise, tactile features).
- Cognitive barrier – consider: misunderstanding device, misinterpreting visual cues, memory demands, cuing, language.
- User error – consider: misuse from manufacturer’s intended manner of use.
- Unsafe activity – consider: activity that may put subject or other person at risk of injury. Note: this is a very important record and special attention should be paid to accurate identification and classification.
- Environmental barrier with device – consider: architectural elements, or auxiliary furniture, or equipment other than device.
- Unable to use AT effectively with device – consider: device impedes effective use of assistive technology(ies) (e.g., wheelchair, cane, walker).
- Assistance from another person required with device – must directly affect subject’s normal, intended, expected use of device; may be physical (does not include device use tasks normally performed by someone else) or verbal (does not including subject prompting needed for task performance).
- Exemplary positive device feature(s) – consider: device features that enable or facilitate use (does not include environmental features).
- Flag for review – consider: need for further review or discussion.
- Context-awareness comment(s) – consider: subject comments that may be worthwhile to note.
Note: No barrier should be marked if a subject uses an AT (e.g., glasses, prosthesis, wheelchair) and he or she is successful in using the device.
- Default EVENTS and their definitions:
- Mild – a very minor barrier to device use or inconvenience. (Some observers do not use this classification.)
- Moderate – a substantial barrier that makes device use difficult but still possible.
- Extreme – a critical barrier that makes intended device use impossible.
Custom MVTA RECORDS and EVENTS can also be added for more specific data analyses. For example:
- Examples of custom RECORDS:
- Active device interaction (consider: device features that the subject actively engages for use)
- Pinch or grip force greater than 10 N6
- Shoulders or arms supporting body weight
- Contact pressure on hands or arms
- Examples of custom EVENTS:
- Wrist range of motion (ROM) – Moderate7
- Wrist ROM – Extreme
- Reaching AND Grasping – Moderate8
- Reaching AND Grasping – Extreme
- Active device interaction (consider: device features that the subject actively engages for use)
Each window-event created in MVTA should have a researcher comment associated with it, which captures the researcher’s insights, observations and comments about the window-event marked.
Creating window-event annotations in MVTA:
A custom annotation of up to 255 characters should be added to each window-event marked in MVTA to give event identifications more meaning, to make it easier to review and understand data, and share to data among researchers. The annotation is displayed for the duration of the window-event, as long as the RECORD of the window-event is highlighted.
- To view an existing annotation:
- Go to the MVTA "Event" menu and select "Annotation." The annotation toolbar should appear at the bottom of the MVTA workspace.
- Highlight the RECORD containing the window-event annotation desired to view.
- To add a new annotation:
- If the annotation toolbar is not at the bottom of the MVTA workspace, go to the MVTA "Event" menu and select "Annotation."
- Highlight the RECORD that contains the window-event to annotate. Make sure the window-event is fully defined with the beginning and end events marked (e.g., with mild, moderate, extreme, or null events) for the window-event.
- Move the time curser to be within the window-event of interest.
- Click in the annotation textbox, and type in the desired annotation.
- Press the "Insert Annotation" button and make sure the text inserted turns from black to red. If the text does not turn red, the annotation was not inserted correctly.
Acknowledgment
This work is supported by the Rehabilitation Engineering Research Center on Accessible Medical Instrumentation, funded by the National Institute on Disability and Rehabilitation Research, U.S. Department of Education Grant #H133E020729. All opinions are those of the authors.
Footnotes:
1 The unit is a purely Plug & Display hardware component, so no software is required to control the quad processor. The RCA to USB cable requires a driver, which can be obtained from x10.com. [back to text]
2 If more than one piece of medical equipment is used at the same time during data collection, all of the equipment identifiers should be included in the file name, separated with a dash. For example: …_ERB-MSB_... [back to text]
3 If data is being collected on more than one subject (i.e. simultaneous patient and provider interaction with a device), then all of the PAT/PRV labels and corresponding subject codes should be included in the file name. For example: PAT1001-PRV1002_… [back to text]
4 If the subject performs more than one task with the device and the researcher does not want to stop the video between tasks, the letter "Z" should be used to represent the inclusion of all tasks within the video file. [back to text]
5 If the subject performs more than one trial with a device and the researcher does not want to stop the video between trials, the number "99" should be used to represent the inclusion of all trials within the video file. [back to text]
6 Custom RECORDS can be added as custom EVENTS if they can be categorized within a default RECORD. For example, "Pinch or grip force greater than 10N" could become an EVENT under the "Physical interaction/manipulation/operation of controls barrier" RECORD, and "Shoulders or arms supporting body weight" could become an EVENT under the "Body support barrier" RECORD. [back to text]
7 We can always assume a custom window-event is an instance of the default window-event. So if custom EVENTS are used in place of the default EVENTS the default information still exists, as well as more detailed information for those who are interested. [back to text]
8 "AND" EVENTS can be used when there is more than one barrier (EVENT) occurring simultaneously. [back to text]
Appendix 1. Detailed Hardware Diagrams
Figure A1.1: Suitcase Layout and Key Components of the MUA-Lab
The MUA-Lab carrying case is shown with each hardware component clearly labeled. The carrying case is approximately 9"x14"x22" (within most airline carry-on regulations) and can accommodate all of the hardware components required for usability analysis. The suitcase is protected with hard plastic shielding and contains a customized foam insert to permit safe and secure travel for the MUA-Lab. All of the hardware components have specific locations within the suitcase that are clearly labeled. There are also several pockets (on the top side that opens) that house the cables and remote controls available for use. The case has an expansion feature so the top section of the suitcase can increase in depth by about 3" for extra equipment, if desired.
Figure A1.2: Color Quad Processor
The Grand Magic Guard II color quad processor is used to capture several video streams and compile them into one output because SVDA currently supports only one video input. The quad processor can receive input from up to four separate video cameras (with standard RCA video cables) and it can output one real-time composite video for input into SVDA (with an RCA to USB adapter cable). The unit is a purely Plug & Display hardware, so no software is required for use, although an AC/DC adapter and power source are required.
Note: in order for the quad processor to work properly with SVDA, a USB Video Capture Adapter and its associated driver are required. Prior to the first use of the MUA-Lab USB adapter, it is necessary to download the driver from the x10 website at http://www.x10.com/support/support_soft1.htm.
Figure A1.3: Vanguard Pan/Zoom/Tilt Camera (Front/Left and Back/Right)
Figure A1.4: XCam2 and WideEye Wireless Cameras
Figure A1.5: Wireless Video Receiver
|
Figure A1.6: Microphones: (a) Wireless Transmitters and Receiver & (b) Boundary Microphone
|
Figure A1.7: Camera Stands: Micro and Mini tripods
The Micro and Mini tripods have connectors to allow you to preset an adjustable tension so the camera is adequately supported once it is oriented in the desired position. To adjust the tension of the ballhead, turn the knob on the bottom of the center column. A red lever lock (located at the top of the legs) is used to adjust the height of the center column and both tripods have telescoping legs with quick-action locks for fast set-up and breakdown. There are 3 levers on each tripod leg so the leg lengths can be adjusted and locked. If a floor shot or low level field of view is desired, the center column of the tripod can be inverted by removing, inverting and reinserting the center column into the track so that the camera points towards the floor.
|
Figure A1.8: Articulating Arm and Clamp (a) Pieces/Left and (b) Assembly/Right
The 3-DOF articulating arm has an adjustable clamp mechanism that can secure the arm to virtually any object within the research environment including poles, posts, tripod legs and beams. There are 3 pieces that make up the mechanism, which must be disassembled for travel in the MUA-Lab carrying case. A wedge insert is also included for clamping the arm onto flat surfaces and it is secured to the clamp jaw beneath the adjuster.
Appendix 2. Detailed Table of Hardware Components
Appendix 3. Wiring Diagram for Hardware Setup
Appendix 4. Selected Hardware Component Tech Sheets
Appendix 5. Advanced Hardware Settings
Advanced Settings: Color Quad Processor
Description of the buttons (on unit and remote control):
• VIDEO 1: Display VIDEO IN 1 input only.
• VIDEO 2: Display VIDEO IN 2 input only.
• VIDEO 3: Display VIDEO IN 3 input only.
• VIDEO 4: Display VIDEO IN 4 input only.
• QUAD/+: Display VIDEO IN 1-4 inputs in a quadrant display and parameter increase button for on screen display menu (except in PIP mode).
• PIP/-: Display Picture in Picture (PIP) mode with user’s choice of any two VIDEO IN 1-4 inputs/parameter decrease button for on screen display menu (except in PIP mode).
• ENTER: Parameter setting and right direction.
• OSD: Displays the on screen display and left direction.Note:
1. The QUAD/+, PIP/-, ←/OSD and Enter/→ keys are all multiple function keys that operate the "on screen display menu".
2. Under the PIP mode, the ↑ (up), ↓ (down), ← (left) and → (right) buttons are directional buttons only.When the quad processor is turned on, the channel numbers and a date/time label are displayed by default. To turn these labels off, use the following commands:
1. Select the ◄/OSD-Quad button to activate the System Setup Menu: Channel Name, Date/Time, Display Mode, Auto Switch
2. Scroll Up/▲ or Down/▼ to highlight Display Mode
3. Select Enter/►
4. Scroll Up/▲ or Down/▼ to adjust Channel Name and Date/Time and use Enter/►to switch between on/off
5. Scroll to Exit and press Enter/►when done
Advanced Settings: Vanguard Pan/Zoom/Tilt CameraAdvanced Settings: Vanguard Pan/Zoom/Tilt Camera
Stored Positions: The Vanguard can store up to nine locations of specific vertical/horizontal positions and zoom settings.
To store a position:
- Press and release C1.
- Press and hold the 'Setup' button on the remote control until the C1 button lights green.
- Move the camera to the position you want to store and then press the 'Auto Focus' button to set the focus for that position.
- Press the number button (1 through 9) on the remote control to store the position under that button number.
- Repeat steps 2-3 for each position you would like to store.
- When you are finished, press the 'Setup' button to save the positions you entered.
Note: you can store new positions over previous positions if you follow the directions above. Just store the new position using a number button that you programmed before.
To select a position:
- Press the desired number button on the remote control to move the camera to that position.
- If you press the ‘Sweep’ button the camera will automatically switch through all of the positions you have stored.
- Press any of the movement buttons on the remote control to end the sweep function.
Focus controls: You can control the focus of the camera manually, in addition to the auto focus feature. Just press the focus up/down buttons to adjust the focus and improve the picture after auto focus or to adjust the focus to a particular object in the field of view.
Iris controls: You can adjust the amount of light that enters the lens of the camera with the iris control up/down buttons. The camera automatically adjusts the iris when it focuses so it has the right amount of light for your subject, but this may need to be adjusted. If you want to brighten the picture press the 'Iris up' button and if you want to limit the amount of light in the picture press the 'Iris down' button.
To program the camera(s) so one remote control can be used to control several cameras:
Each camera needs to be programmed with a unique number (i.e., C1, C2, C3, or C4).
- Set the mode switch on bottom of camera to program.
- Press the desired camera number on the remote control (e.g., C2) to set the camera number as desired.
- Press the desired camera number on the remote control again (e.g., C2) if you do not wish to have the camera number displayed within the collected video.
- Set the mode switch back to transmit.
- Repeat steps 1-4 to program additional cameras.
To invert the image: The Vanguard can be easily attached to any tripod available. In some situations the camera may need to be mounted upside down. In this case, the picture should be inverted so the proper orientation is displayed.
- Press and release the C1 button (or whichever channel the camera is set to).
- Press and hold the Setup button on the remote until the green C1 button lights.
- Press the Iris Up button to flip the picture.
- Press the Setup button again to save this setting.
The following commands should be used to flip the image when the camera is placed upside-down:
Appendix 6. Using Adobe Premier (AP) v6.5 for Video Editing
Digital video editing cards offer extra power when editing video files created with SVDA/MVTA. These cards are available only in PCI format and therefore can only be used in a computer system that has an extra full-size PCI slot. This would usually restrict these cards to only working in a desktop system with a tower case but there are expansion cases that can be connected to a laptop that can hold 1 or 2 full-size PCI cards (e.g., http://www.mobl.com/expansion/pci/2slot/). One major drawback with this option is that they add considerable bulk and weight to the portable lab system.
Editing MUA-Lab video files may require extra features not offered in MVTA, such as blurring subjects' faces, rearranging the timing and sequence of events, or adding extra audio or digital comments. These can all be accomplished using Adobe Premiere (AP) version 6.5 along with a recommended digital video editing card. The following cards are known to provide the additional editing needs that MUA-Lab users may need or want:
- Matrox RT.X100 (http://www.matrox.com/video/products/rtx100xtreme/home.cfm)
- Canopus DVStorm2 (http://www.canopus.us/US/products/dvstorm_2/pm_dvstorm_2.asp)
AP is built so the cards can be installed and then it automatically utilizes the processing power of the added cards for editing video files. Therefore, the time it takes AP to "render" the movie files is decreased. Rendering refers to the process of making digital changes to the original video file. Since video files usually contain a lot of information (on the order of hundreds of megabytes to several gigabytes), using the computer’s CPU and memory alone could mean waiting up to several hours for the new video file to be created. These digital video editing cards offer a tremendous boost to productivity in video editing by increasing the processing power. Their main chipsets are specifically built to handle video editing, instead of the more general operations that the CPU is built for. They also provide many additional features that are not found in AP, although not all of these functions are useful to the MUA-Lab.
Notes about AP:
- The learning curve of AP is about 3-10 hours, depending on the user.
- People with vision disabilities may find the many small buttons of AP unusable.
Any publicly disseminated video data needs to have subjects' identifiable features removed.
Adobe Premier 6.5- Video Editing (Blur a moving face)
Figure A6.1: Layout of AP Editing Window
Note:
- These instructions are to be followed per quadrant of the video file.
- Save the Adobe file often, as the program tends to crash.
Step 1: Open Adobe Premier 6.5 and select appropriate file settings. In the Load Projects Settings window, under Available Presets make sure "Standard 32 kHz" is highlighted under the Canopus DV-NTSC drop down menu and click
(This should be the default setting.)
For Steps 2-3, see Figure A6.1 for reference.
Step 2: Import Video File for Editing:
- Go to File and click Import. Then click File… Locate video to be blurred and double left click on that file to import it. (This file now appears in the Project window.)
- Rest the mouse over the imported file so a hand appears. Then click and hold the left mouse button.
- Drag the imported file to the Timeline window and release it onto the Video 1A (or Video1) track.
Step 3: Copy Video File for Editing:
- In the Timeline window, right click on the file in the Video 1A track and left click Copy.
- Right click on the Video 2 track and left click Paste.
Step 4: Locate the Video tab and select the Stylize pull down menu (See Figure A6.2).
Figure A6.2: AP Video Tab
Step 5: Create a Mosaic Mask to generate the blurring effect on the video. In the Stylize menu, select Mosaic and drag on top of the file in the Video 2 track (See Figure A6.2).
Step 6: Define the Mosaic Density by changing the number of pixels in the pixelated image. Locate the Effect Controls tab (Video 2 track must be selected). Click on the underlined number of adjacent Horizontal (See Figure A6.3).
Figure A6.3: AP Mosaic Density Adjustment
Step 7: A new window will appear. Change 10 to 35 and click
. Repeat for Vertical (See Figure A6.3).
Step 8: Create the circle/ellipse pattern for the image in the quadrant to be blurred. Go to File and click New. Then click Title. The Adobe Title Designer window will appear (See Figure A6.4).
Figure A6.4: AP Title Designer Window
Step 9: Be sure the box to the left of Show Video is checked. Select the ellipse button
and move the cursor in the quadrant to be blurred.
Step 10: Click and hold the left mouse button. Drag the mouse until a circle/ellipse is adequate to completely cover the image being blurred.
Step 11: Click on the arrow button
. Select the circle/ellipse and move it to the desired location. If unsure of the location, the circle/ellipse can be repositioned later.
Step 12: Locate the Object Style box. In the Fill pull down menu, select the grey box
to the right of "Color". The Color Picker window will appear.
Step 13: Choose pure white by changing the numbers to the right of Red, Green and Blue to 255 and click
Step 14: Save Title File
- Go to File and click Save as. Name the title file with the same video file name and add the quadrant number. Example: Upper left quadrant = 1.
- Pick Location to Save File. In the Save in: drop down menu, select the preferred location of the file once it is exported.
Note: Because the title files define the make up of the final project file, keep all the title files in one location allowing for easy access if changes are necessary.
- Click Save.
Step 15: Close the Adobe Title Designer window after the title file is saved.
Step 16: The title file will appear in the Project window. Click and hold the left mouse button on the file and drag it to the Video 3 track.
Note: If more video tracks are needed, go to Timeline in the Standard Tool Bar and click Add Video Track.
Step 17: Select the file in the Video 2 track.
Step 18: Create transparencies so the previously created mosaic mask only applies to the circle/ellipse and leaves the remaining parts of the video transparent to the mask. In the Effect Controls tab, click on Setup to the right of Transparency (See Figure A6.5). The Transparency Settings window will appear.
Figure A6.5: AP Effect Controls Tab
Step 19: In the Key Type pull down menu, select "Track Matte" and click
Note: At this point, the video clip with the blurred circle/ellipse should be visible in the approximate location desired.
Step 20: Locate the Video tab and select the Distort pull down menu.
Step 21: In the Distort menu, select Transform Filter and drag on top of the file in the Video 3 track. This enables movement of the circle/ellipse (See Figure A6.6).
Figure A6.6: AP Distort Menu in the Video Tab
Step 22: Click the triangle pull down menu button to the left of the Video 3 track so it expands and the arrow points down.
Step 23: Click the diamond button in the bottom left corner. A grey box between two arrows will appear to the right; be sure it is checked (See Figure A6.7).
Figure A6.7: AP Triangle Pull Down Menu
Step 24: Begin Moving Blurred Image
- If the blurred circle/ellipse is not initially in the desired location, locate the Effect Controls tab and click the grey box to the right of Position. A coordinate circle will appear in the middle of the Monitor window (See Figure A6.8).
- Click in the coordinate circle the direction in which the circle/ellipse needs to move. The coordinate circle represents the centroid of the circle/ellipse so that the movement of the coordinate circle is relative to that of the circle/ellipse.
- Continue clicking in the coordinate circle, in the preferred direction, until the blurred circle/ellipse is in the desired location.
Figure A6.8: AP Monitor Window
Step 25: Continue Blurring Remainder of Quadrant
- Press and hold the Alt key (located on the keyboard to the left of the Space Bar). Then click the Video Navigator button (located in the Timeline window above the video tracks) to scroll through the video with the blurred circle/image (See Figure A6.1).
- Scroll through the video until the blurred circle/ellipse no longer covers the desired image. To reposition, be sure they grey box to the left of the video track is still checked (refer to Figure A6.7) and repeat Step 24. A white diamond will appear in the Video 3 track. Continue until the end of the video.
Step 26: Click File in the Standard Tool Bar and select Save.
Step 27: Pick Location to Save File. In the Save in: drop down menu, select the preferred location of your file once it is saved.
Step 28: Click Save. The file will now be saved to the selected location.
To Blur Remaining Quadrants of the Video: (above instructions are for one quadrant)
Step 29: Click Timeline in the Standard Tool Bar and select Add Video Track. Repeat
Step 30: Now Video 4 and Video 5 tracks are snown (or 6 and 7, etc.).
Step 31: Drag the imported video file from the Project window to the new Video 4 track. Refer back to step 2ii above, noting the change in video track numbers.
Step 32: Repeat Steps 4-32 until all quadrants have been blurred.
To Export Finished Blurred Video Clip:
Step 33: Click File in the Standard Tool Bar and select Export Timeline. Then click Movie... Name the blurred video the same as the video file.
Step 34: Pick a Location to Save File. In the Save in: drop down menu, select the preferred location of your file once it is exported.
Step 35: Click Save. The file will now be exported to the selected location; it may take a few minutes.
Helpful Tips
Remember: always save often! This program is very powerful and may crash in the middle of a work in progress.
When the blurred image is not necessary: If the blurred circle/ellipse is not needed during a particular segment of the video, it is possible to cut it out of that section. Use the Double Razor Blade button in the Timeline window and cut the section out of both the copied video track and the mosaic track for the particular quadrant of interest (i.e., cut the section from Video 2 and Video 3).
When a blurred image moves on its own: Towards the end of the video, the blurred circle/ellipse appears to move back to its starting position. To avoid this, extend the blurred file beyond the end of the video file. Once Step 25 is complete, be sure to save the final position of the circle/ellipse by checking the grey box to the left of the video (See Figure A6.7). Then pull the blurred file back so that it lines up with the end of the video file.
Appendix 7. Protocol Manager Backend Instructions
File Structure for MUA-Lab PM
Several back-end files are required for the MUA-Lab Protocol Manager (PM) to function correctly. The following gives a detailed description of each file as well as example file listings at the end of this Appendix. This document applies to PM Versions 2.0 and 3.0 and to some extent to 1.0, but because Version 1.0 is no longer being used it is not mentioned in this document.
To copy records for patients or providers, it is first necessary to understand the file structure of the PM so that the appropriate files are selected, copied, and pasted into the appropriate locations. For this process, it is also necessary to use a File Transfer Protocol (FTP) program for copying files onto a local computer, and then once modifications are made the files from the local computer can be moved back to the appropriate location(s) on the RERC-AMI server. To find a free FTP program to download from the internet, search the internet to find software to download or use FTP Commander Freeware (available at http://www.vista.ru/2inter.htm). Programs such as Dreamweaver also support FTP, as well as Fetch for the Macintosh platform.
The folder and file structure for the PM is shown below in Figure A7.1. A boxed item with yellow background is a folder, and open text is a file in the diagram shown below.
Note that the IRB level appears under the D1 version and "Fillerup" folders:
D1Three folder / Fillerup folder / <IRB Number> folder.
or
D1Two folder / Fillerup folder / <IRB Number> folder.
Figure A7.1: Protocol Manager File Structure
There are two file categories in the PM structure. The file extension for all files is .config. In the following discussion when a section name is mentioned, it means a section name from the Table of Contents (TOC) of the PM. The files are:
- Common files
Common files are common to all children and exist at the parent level. There are three common files at each parent level: _LOCK, _FMA and _SECX (currently section 5B but earlier named as section 10 in version 1.0). See below for _LOCK, _SECX and _FMA file listings, respectively. Depending on what data has already been filled into the PM, these files are created in the parent level folder. The parent level folder also contains several children. The essential file that exists automatically in every parent folder is the _LOCK file (see below for a listing) and the essential folder that exists at every parent is the default child whose name is the same as its immediate parent. It means when a parent folder is created, a child by the same name as the parent is created under that parent, by default. - Specific Files
Specific files exist under each child. They are: _ONE, _TWO, _THREE, _FOUR and _2B (section 2B). Each file is described here in detail, and it should be noted that data for ALL SUBJECTS under the child device are stored in the files listed below. That is, each device folder contains a _ONE.config file, _2B.config file, etc. for all the subjects associated with that device.- _ONE.config
This file contains several nodes. Please refer to Appendix for details. It contains TOC sections 1, 2A, 2C and 2D. 2B alone is not in this file but is separately done with _2B file at parent level. In a nutshell it contains the following of the TOC.- 1 - Problem Statement
- 2A - Advance Preparation - Understand all aspects of instrument usage.
- 2C - Advance Preparation - General requirements for test subject performance
- 2D - Advance Preparation - Conduct pilot tests
- _2B.config
This file contains everything for section 2B of TOC, including:- 2B-1 - Advance preparation – Universal design analysis (patient)
- 2B-2 - Advance preparation – Universal design analysis (provider)
- _TWO.config
This file contains sections 3A and 3C of TOC. In summary each record is for either a patient or provider. Since the questionnaire is big, this file tends to be larger as the number of patients/providers increases.- 3A - Pre-activity patient interview form
- 3C - Pre-activity provider interview form (Note: this is 3B in Version 2.0)
- _FMA.config (Version 3.0 of D1PM only)
This contains Fugl_Meyer scores recorded and they correspond to sections 3B and 3D as below. This file is also used for FMA summary pages later listed in the TOC.- 3B - Functional assessment – Patient
- 3D - Functional assessment – Provider
- _THREE.config
This file contains TOC sections 4A, 4B and 4C in one file:- 4A - Preactivity preparation
- 4B - Activity performance observation
- 4C - Documentation and monitoring of data collection and storage.
- _FOUR.config
This contains section 5A only with the following description.- 5A - Post-activity subject interview form
- _ONE.config
Duplication of Data
Once a child is created and some records are added, the same data can be duplicated for another child without re-entering data.
If you are creating a new parent, under an IRB, do the following:
- Make sure you are not logged into the PM.
- Create a new, valid parent folder. Under that parent folder, create a default child folder (with the same name as the parent).
- Copy the "_LOCK.config" file into the parent level (see figure above).
If you are creating a new child, under a parent, do the following:
- Make sure you are not logged into the PM.
- First choose which sections of the TOC you need to duplicate.
- Find the corresponding file on the server that contains these TOC sections.
- Copy that file(s) into local machine (your computer) via FTP from RERC website.
- Make changes to your copy of the file(s) on your computer.
- Create a new child folder on the web server under the parent.
- Open the newly created child folder (on the RERC server).
- Copy the edited file(s) from your computer to the new child folder on the server.
If you are copying subject files of the pre-activity interview from one device to another, use the following method:
- Make sure you are not logged into the PM.
- Copy to your local computer (using FTP) the "_TWO.config" file from the device folder that contains the subject data you want to duplicate.
- Rename as "old" the "_TWO.config" file in its original location on the server so the original file is not overwritten. Rename to "_TWO_old_your-name-or-initials-here.config." Example: "_TWO_old_Melissa.config." (Note that all file names may not contain any other characters, such as numerals.)
- Copy the " _TWO.config" file from your local computer into the other device folder(s) on the server that you want to contain the subject data.
- Restart the PM and your new data should appear.
Very Important Note:
Always make sure you are not logged into the PM when making any changes. Please try this a few times without making any changes so you get comfortable with this process before making changes. Also, to prevent the unintentional loss of data, always rename old files on RERC web server with the following format: "One_old_yourname.config". Then, if things go wrong you can always rename the old files back to originals. If original files are not renamed then changes are made , the original files will be lost forever. So please be careful!!!