The Experts below are selected from a list of 1401 Experts worldwide ranked by ideXlab platform
Paul Green - One of the best experts on this subject based on the ideXlab platform.
-
using standards to improve the replicability and applicability of Driver Interface research
Automotive User Interfaces and Interactive Vehicular Applications, 2012Co-Authors: Paul GreenAbstract:This paper describes how referring to and using test methods and conditions specified in recognized standards and guidelines from the International Organization for Standardization (ISO), the Society of Automotive Engineers (SAE), U. S. Department of Transportation (US DOT), the International Telecommunications Union (ITU), and other organizations can improve the replicability and applicability of Driver Interface research. In particular, this paper examines all 25 papers presented at the 2011 AutomotiveUI (Auto-UI) Conference. Identified for each paper were (1) the method used, (2) the dependent measures, (3) if the dependent measures were adequately defined, (4) the relevant standards, and (5) if the relevant standards were cited. Of the 9 papers involving driving or simulated driving, only the experiments using the ISO lane-change test (3 papers) would obviously be publicly replicable because the scenarios were otherwise described too generally (e.g., "highway"). Furthermore, to a lesser extent, many papers did not define the dependent measures used, so what was measured was sometimes uncertain (e.g., gap or headway). A solution would be to cite the definitions of measures in SAE Recommended Practice J2944 (e.g., lane departure, option A; time to collision, option B). Finally, only 2 of the 25 papers completely cited relevant industry standards, resulting in a weak connection between the research presented and application (though for some papers, there were no relevant standards). To strengthen that connection, the call for papers for future Auto-UI conferences must require submissions to cite relevant standards in the keywords and references section where appropriate, and their inclusion must be among the review criteria. To aid future authors, lists of relevant ISO, US DOT, and other standards and guidelines are provided in this paper. As the authors of Auto-UI papers present similar materials at other conferences, the recommendations given here are appropriate for other conferences as well.
-
AutomotiveUI - Using standards to improve the replicability and applicability of Driver Interface research
Proceedings of the 4th International Conference on Automotive User Interfaces and Interactive Vehicular Applications - AutomotiveUI '12, 2012Co-Authors: Paul GreenAbstract:This paper describes how referring to and using test methods and conditions specified in recognized standards and guidelines from the International Organization for Standardization (ISO), the Society of Automotive Engineers (SAE), U. S. Department of Transportation (US DOT), the International Telecommunications Union (ITU), and other organizations can improve the replicability and applicability of Driver Interface research. In particular, this paper examines all 25 papers presented at the 2011 AutomotiveUI (Auto-UI) Conference. Identified for each paper were (1) the method used, (2) the dependent measures, (3) if the dependent measures were adequately defined, (4) the relevant standards, and (5) if the relevant standards were cited. Of the 9 papers involving driving or simulated driving, only the experiments using the ISO lane-change test (3 papers) would obviously be publicly replicable because the scenarios were otherwise described too generally (e.g., "highway"). Furthermore, to a lesser extent, many papers did not define the dependent measures used, so what was measured was sometimes uncertain (e.g., gap or headway). A solution would be to cite the definitions of measures in SAE Recommended Practice J2944 (e.g., lane departure, option A; time to collision, option B). Finally, only 2 of the 25 papers completely cited relevant industry standards, resulting in a weak connection between the research presented and application (though for some papers, there were no relevant standards). To strengthen that connection, the call for papers for future Auto-UI conferences must require submissions to cite relevant standards in the keywords and references section where appropriate, and their inclusion must be among the review criteria. To aid future authors, lists of relevant ISO, US DOT, and other standards and guidelines are provided in this paper. As the authors of Auto-UI papers present similar materials at other conferences, the recommendations given here are appropriate for other conferences as well.
-
Driver Interface hmi standards to minimize Driver distraction overload
2008Co-Authors: Paul GreenAbstract:This paper describes (1) the telematics distraction/overload problem, (2) what distraction and overload are and how they differ, (3) the standards and guidelines that apply to the design and evaluation of Driver Interfaces/human-machine Interfaces (HMI) for telematics (and their strengths and weaknesses), and (4) what standards and research are needed to support the development of Driver Interfaces. Most of the paper is a detailed discussion of evaluation standards, in particular SAE Recommended Practices J2364 (Task Time and Occlusion Tests) and J2365 (Task Time Estimation), ISO Standards 16673 (Occlusion Test) and 26022 (Lane-Change Test), and the AAM Driver Focus Guideline.
-
Driver Interface/HMI Standards to Minimize Driver Distraction/Overload
2008Co-Authors: Paul GreenAbstract:This paper describes (1) the telematics distraction/overload problem, (2) what distraction and overload are and how they differ, (3) the standards and guidelines that apply to the design and evaluation of Driver Interfaces/human-machine Interfaces (HMI) for telematics (and their strengths and weaknesses), and (4) what standards and research are needed to support the development of Driver Interfaces. Most of the paper is a detailed discussion of evaluation standards, in particular SAE Recommended Practices J2364 (Task Time and Occlusion Tests) and J2365 (Task Time Estimation), ISO Standards 16673 (Occlusion Test) and 26022 (Lane-Change Test), and the AAM Driver Focus Guideline.
-
estimating compliance with the 15 second rule for Driver Interface usability and safety
Proceedings of the Human Factors and Ergonomics Society Annual Meeting, 1999Co-Authors: Paul GreenAbstract:This paper describes SAE J2365 (Recommended Practice for Calculating the Time to Complete In-Vehicle Navigation and Route Guidance Tasks), a draft procedure to estimate if the requirements of SAE J2364 (Navigation Function Access) are met. Application of these practices will enhance the safety, ease of use, and customer convenience of Driver Interfaces. SAE J2364 specifies that Drivers should not be allowed to perform navigation-system tasks in a moving vehicle that take more than 15 seconds to complete when measured staticly. Tasks are defined to start when the Driver's hands begin to move from the steering wheel and end when feedback from the final-switch actuation is processed.The 11-step calculation procedure of J2365 involves determining exactly how each task (e.g., destination entry) is carried out, developing a pseudo-code description of the goals and methods used, determining the associated elemental tasks, and adding up the task times. Elemental times [reaching for a device, keying (cursor, lette...
R.j. Richards - One of the best experts on this subject based on the ideXlab platform.
-
IEEE Real Time Technology and Applications Symposium - Uniform Driver Interface (UDI) reference implementation and determinism
Proceedings. Eighth IEEE Real-Time and Embedded Technology and Applications Symposium, 2002Co-Authors: R.m. Barned, R.j. RichardsAbstract:This paper briefly discusses the technology and standardization activities that are in progress in Project UDI (Uniform Driver Interface) and INCITS (InterNational Committee for Information Technology Standards) Technical Committee R1, Real-time Computing Systems. Project UDI has an open source reference implementation that runs in several operating systems. The design of this implementation is discussed and real time issues identified. The focus of this paper is to discuss the changes that can be made to the Project UDI reference implementation to develop a deterministic UDI reference implementation suitable for real-time needs. These changes are fairly significant, but affect the operating system only, allowing the same UDI Drivers to be used in the deterministic implementation as in the time-sharing implementations. The effects of these changes are evaluated in terms of the benefits to, or impacts on, different categories of users. Some of these changes are suitable for real-time safety critical systems; others make sense for other types of realtime systems. The types of issues discussed include allocation of data buffers and control structures, interrupt processing, scheduling, multiprocessors, I/O processors, etc. UDI also introduces a fundamental concept of execution "regions." Regions allow I/O Drivers or protocol modules to live in different protection domains. These regions may in fact be on different processors. There are real-time trade-offs to be made in transitioning between regions. These trade-offs are discussed. Finally the paper discusses the status of the real-time standardization activity, the standardization decisions that have been made and the reasons for these decisions.
-
Uniform Driver Interface (UDI) reference implementation and determinism
Proceedings. Eighth IEEE Real-Time and Embedded Technology and Applications Symposium, 2002Co-Authors: R.m. Barned, R.j. RichardsAbstract:This paper briefly discusses the technology and standardization activities that are in progress in Project UDI (Uniform Driver Interface) and INCITS (InterNational Committee for Information Technology Standards) Technical Committee R1, Real-time Computing Systems. Project UDI has an open source reference implementation that runs in several operating systems. The design of this implementation is discussed and real time issues identified. The focus of this paper is to discuss the changes that can be made to the Project UDI reference implementation to develop a deterministic UDI reference implementation suitable for real-time needs. These changes are fairly significant, but affect the operating system only, allowing the same UDI Drivers to be used in the deterministic implementation as in the time-sharing implementations. The effects of these changes are evaluated in terms of the benefits to, or impacts on, different categories of users. Some of these changes are suitable for real-time safety critical systems; others make sense for other types of realtime systems. The types of issues discussed include allocation of data buffers and control structures, interrupt processing, scheduling, multiprocessors, I/O processors, etc. UDI also introduces a fundamental concept of execution "regions." Regions allow I/O Drivers or protocol modules to live in different protection domains. These regions may in fact be on different processors. There are real-time trade-offs to be made in transitioning between regions. These trade-offs are discussed. Finally the paper discusses the status of the real-time standardization activity, the standardization decisions that have been made and the reasons for these decisions.
R.m. Barned - One of the best experts on this subject based on the ideXlab platform.
-
IEEE Real Time Technology and Applications Symposium - Uniform Driver Interface (UDI) reference implementation and determinism
Proceedings. Eighth IEEE Real-Time and Embedded Technology and Applications Symposium, 2002Co-Authors: R.m. Barned, R.j. RichardsAbstract:This paper briefly discusses the technology and standardization activities that are in progress in Project UDI (Uniform Driver Interface) and INCITS (InterNational Committee for Information Technology Standards) Technical Committee R1, Real-time Computing Systems. Project UDI has an open source reference implementation that runs in several operating systems. The design of this implementation is discussed and real time issues identified. The focus of this paper is to discuss the changes that can be made to the Project UDI reference implementation to develop a deterministic UDI reference implementation suitable for real-time needs. These changes are fairly significant, but affect the operating system only, allowing the same UDI Drivers to be used in the deterministic implementation as in the time-sharing implementations. The effects of these changes are evaluated in terms of the benefits to, or impacts on, different categories of users. Some of these changes are suitable for real-time safety critical systems; others make sense for other types of realtime systems. The types of issues discussed include allocation of data buffers and control structures, interrupt processing, scheduling, multiprocessors, I/O processors, etc. UDI also introduces a fundamental concept of execution "regions." Regions allow I/O Drivers or protocol modules to live in different protection domains. These regions may in fact be on different processors. There are real-time trade-offs to be made in transitioning between regions. These trade-offs are discussed. Finally the paper discusses the status of the real-time standardization activity, the standardization decisions that have been made and the reasons for these decisions.
-
Uniform Driver Interface (UDI) reference implementation and determinism
Proceedings. Eighth IEEE Real-Time and Embedded Technology and Applications Symposium, 2002Co-Authors: R.m. Barned, R.j. RichardsAbstract:This paper briefly discusses the technology and standardization activities that are in progress in Project UDI (Uniform Driver Interface) and INCITS (InterNational Committee for Information Technology Standards) Technical Committee R1, Real-time Computing Systems. Project UDI has an open source reference implementation that runs in several operating systems. The design of this implementation is discussed and real time issues identified. The focus of this paper is to discuss the changes that can be made to the Project UDI reference implementation to develop a deterministic UDI reference implementation suitable for real-time needs. These changes are fairly significant, but affect the operating system only, allowing the same UDI Drivers to be used in the deterministic implementation as in the time-sharing implementations. The effects of these changes are evaluated in terms of the benefits to, or impacts on, different categories of users. Some of these changes are suitable for real-time safety critical systems; others make sense for other types of realtime systems. The types of issues discussed include allocation of data buffers and control structures, interrupt processing, scheduling, multiprocessors, I/O processors, etc. UDI also introduces a fundamental concept of execution "regions." Regions allow I/O Drivers or protocol modules to live in different protection domains. These regions may in fact be on different processors. There are real-time trade-offs to be made in transitioning between regions. These trade-offs are discussed. Finally the paper discusses the status of the real-time standardization activity, the standardization decisions that have been made and the reasons for these decisions.
Jeffrey H. Everson - One of the best experts on this subject based on the ideXlab platform.
-
RUN-OFF-ROAD COLLISION AVOIDANCE USING IVHS COUNTERMEASURES
2020Co-Authors: Dean Pomerleau, Todd Jochem, Charles E. Thorpe, P.h. Batavia, Doug Pape, Jeff Hadden, Nancy Mcmillan, Nathan J. Brown, Jeffrey H. EversonAbstract:In this report, the authors present performance guidelines for the design and development of road departure warning systems for improving vehicle safety by eliminating or mitigating road departure crashes through Driver notification or warning. The guidelines are for two classes of road departure warning systems: Lane Drift Warning Systems (LDWS) and Curve Speed Warning Systems (CSWS). All aspects of system performance are addressed, including sensing requirements, warning algorithm requirements, Driver Interface requirements, test procedures, and estimation of associated benefits. The guidelines are intended to be used as tools by manufactures and developers of road departure warning systems for: 1) standardizing system requirements; 2) standardizing Driver Interface and control across systems developed by different manufacturers; and, 3) standardizing test procedures to verify proper system operation.
-
RUN-OFF-ROAD COLLISION AVOIDANCE USING IVHS COUNTERMEASURES TASK 6 SUPPLEMENTAL REPORT, COMPUTER SIMULATION STUDIES OF COUNTERMEASURE SYSTEM EFFECTIVENESS
1999Co-Authors: Dean Pomerleau, Jeffrey H. EversonAbstract:In this report, performance guidelines for the design and development of two classes of road departure warning systems. The systems are Lane Drift Warning Systems (LDWS) and Curve Speed Warning Systems (CSWS). The LDWS warns in the event of an unintentional drift out of the travel lane. The CSWS warns if the vehicle is approaching a curve too quickly for current conditions. System performance is addressed for scanning requirements, warning algorithm requirements, Driver Interface requirements, test procedures, and estimation of associated benefits. The intent of the guidelines are that they be used by manufacturers and developers as a tool for: 1) standardizing system requirements; 2) standardizing Driver Interface and control; and, 3) standardizing test procedures for verifying proper system operation.
S.m. Bellovin - One of the best experts on this subject based on the ideXlab platform.
-
NDSS - A "bump in the stack" encryptor for MS-DOS systems
Proceedings of Internet Society Symposium on Network and Distributed Systems Security, 1996Co-Authors: David Wagner, S.m. BellovinAbstract:Most implementations of IP security are deeply entwined in the source of the protocol stack. However, such source code is not readily available for MS-DOS systems. We implemented a version using the packet Driver Interface. Our module sits between the generic Ethernet Driver and the hardware Driver; it emulates each to the other. Most of the code is straightforward; in a few places, though, we were forced to compensate for inadequate Interface definitions.
-
A "bump in the stack" encryptor for MS-DOS systems
Proceedings of Internet Society Symposium on Network and Distributed Systems Security, 1996Co-Authors: D.a. Wagner, S.m. BellovinAbstract:Most implementations of IP security are deeply entwined in the source of the protocol stack. However, such source code is not readily available for MS-DOS systems. We implemented a version using the packet Driver Interface. Our module sits between the generic Ethernet Driver and the hardware Driver; it emulates each to the other. Most of the code is straightforward; in a few places, though, we were forced to compensate for inadequate Interface definitions.
