SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Zlocki Adrian) "

Sökning: WFRF:(Zlocki Adrian)

  • Resultat 1-10 av 11
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Bakri, Taoufik, et al. (författare)
  • Requirements for the Evaluation Framework.
  • 2011
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • interactIVe has the objective to develop new integrated Advanced Driver Assistance Systems (ADAS). In order to evaluate these ADAS, an evaluation framework is required. Therefore, a horizontal subproject called “Evaluation and Legal Aspects” is part of interactIVe, with the main objective to provide this framework and give support to the vertical subprojects in their evaluation work. The purpose of this deliverable is to define the relevant aspects for the development of the common and centralized evaluation framework. The goal is not to have the final document for evaluating the systems and functions, but to define and establish available methods and tools. Based on the defined Use Cases and the description of the developed interactIVe functions,research questions are formulated and included in this deliverable 7.1. Based on these research questions, corresponding hypothesis will be included in Deliverable 7.2. Evaluation has been divided in three main categories: • Technical Assessment, with the objective to evaluate the performance of the developed functions of interactIVe and to collect information and data for safety impact assessment. • User-Related Assessment has the goal to evaluate the functions from the user perspective, and also to provide further input to the safety impact assessment. • Impact Assessment will estimate how and how much the functions influence traffic safety. The challenge when dealing with the above-mentioned assessments is the fact that every system (SECONDS, INCA and EMIC) includes various functions. These different functions can be assessed individually or being part of the complete system, so interactions between them have to be taken into account. Moreover, the availability of tools and prototype vehicles has to be assured. The outcome of this deliverable is a list of methods, tools and research questions.
  •  
2.
  • Barnard, Yvonne, et al. (författare)
  • Data management and data sharing in field operational tests
  • 2016
  • Ingår i: Intelligent Transportation Systems: From Good Practices to Standards. - : CRC Press. - 9781498721875 ; , s. 59-72
  • Bokkapitel (övrigt vetenskapligt/konstnärligt)abstract
    • In this chapter it will be discussed how data from Field Operational Tests of Intelligent Transport Systems can be managed and shared. The Field Operational Tests, where hundreds of users get to experience the latest systems, aim to assess the impacts that would result from a wide-scale implementation. Evaluation principles of Field Operational Tests will be explained, and a closer look will be taken at the data that is collected for carrying out the assessments. The widely used FESTA methodology for designing and conducting Field Operational Tests and Naturalistic Driving Studies already provides several recommendations for managing data. This methodology will be discussed and illustrated by examples of its use in European projects. As field test projects set out to collect a huge set of data, the projects themselves do not usually have the scope or the resources to analyze the data from every perspective. Therefore re-use of the collected data also by other projects with different research questions has the potential to generate a wealth of new knowledge about what is happening in the interactions between drivers, vehicles and the infrastructure. Data sharing is the focus of a European support action, FOT-Net Data. The support action is working, with international collaboration, to form a data sharing framework, a data catalogue, and provide detailed recommendations for sharing and re-use. Outcomes from this activity will be discussed. Ways of sharing different types of data will be described, including the necessary steps to be taken to open up the data.
  •  
3.
  •  
4.
  • Bruzelius, Fredrik, et al. (författare)
  • Test report
  • 2010
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • This report is the document summarising the testing experience and knowledge gained from the physical testing activities within the eVALUE project. The document contains brief introductions to the testing scenarios as well as short summaries of conclusions. Appended to this document are the testing reports that have been compiled during the different test sessions. Physical testing at test tracks all across Europe has been the main input in the development of scenarios and test procedures. This document describes the development tests that have been performed during 2010, based on a first draft set of testing protocols. The experience from the performed tests has been used as an important input to the revision of the testing protocols, i.e. the formal documents that describe how a test should be performed and evaluated. These protocols are documented in the separate Deliverable 3.2.
  •  
5.
  • Fahrenkrog, Felix, et al. (författare)
  • Impact Assessment of Developed Applications – Overall interactIVe Assessment
  • 2013
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • interactIVe introduces active intervention safety systems in order to increase traffic safety. The interactIVe functions are – depending on their purpose – able to brake and steer autonomously. Furthermore, the driver is continuously supported by interactIVe assistance systems which warn the driver in potentially dangerous situations. Seven demonstrator vehicles – six passenger cars of different vehicle classes and one truck - are built up in interactIVe to develop, test, and evaluate the next generation of safety systems. The three vertical subprojects in interactIVe SECONDS, INCA and EMIC have developed 11 different functions with a wide range of target areas. The developed advanced driver assistance systems (ADAS) comprise the following systems: • SP4 “SECONDS” dealing with functions, which support the driver continuously in the driving process. These functions should not only support the driver in dangerous situations, but help the driver to avoid them. • SP5 “INCA” dealing with functions, which combine longitudinal and lateral control of the vehicle in order to prevent imminent accidents. The INCA functions’ focus is not only on the collision avoidance in rear-end conflicts, but also on other types of conflicts, such as blind-spot and road departure situations. • SP6 “EMIC” deals with critical pre-crash applications, where collision mitigation can be realised at a reasonable cost. In order to evaluate the ADAS developed, an evaluation framework is required. Therefore, the subproject “Evaluation and Legal Aspects” is part of the interactIVe project, which has as main objective to provide this framework and to support the vertical subprojects in their evaluation work. The evaluation of the interactIVe functions has been divided into three main categories: • Technical Assessment to evaluate the performance of the developed functions and collect information and data for safety impact assessment. • User-Related Assessment to assess the functions from the user perspective, and also to provide further input to the safety impact assessment. • Impact Assessment to estimate how and how much the functions influence traffic safety. In this deliverable, the results of the evaluation in interactIVe are presented.
  •  
6.
  • Jacobson, Jan, et al. (författare)
  • Final testing protocols
  • 2011
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • This report is the final document summarizing the inspection and testing protocols of the eVALUE project. It describes principles, inspection protocols and testing protocols for performance testing of ICT-based safety systems. The inspection protocols (published earlier in D2.2) and the testing protocols introduced in D3.1 are replaced by the ones in D3.2. The older versions are obsolete and should be disregarded. The inspection protocols cover the definition of the test vehicle, HMI aspects, environmental conditions, and functional safety. The inspection protocols are used to prepare for the physical tests as well as evaluating the performance of the vehicle. The testing protocols address longitudinal, lateral, and stability-oriented traffic scenarios. The longitudinal scenarios include a pedestrian crossing the road in front of the vehicle, or the situation where a driver approaches a stationary queue of cars. Involuntarily lane departures and cars in the blind spot during a lane change are situations covered by the lateral scenarios. Exiting a highway, avoiding an obstacle, and braking on a partially ice-covered road surface are examples of traffic scenarios related to stability.
  •  
7.
  • Larsson, Pontus, et al. (författare)
  • Test and evaluation plans
  • 2012
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • interactIVe introduces safety systems that autonomously brake and steer. The driver is continuously supported by interactIVe assistance systems. They warn the driver in potentially dangerous situations. The systems do not only react to driving situations, but are also able to actively intervene in order to protect occupants and vulnerable road users. The objective of interactIVe is to develop new integrated Advanced Driver Assistance Systems (ADAS) for safer and more efficient driving. Seven demonstrator vehicles – six passenger cars of different vehicle classes and one truck is being built up within this project to develop, test, and evaluate the next generation of safety systems. The evaluation of the interactIVe functions has been divided in three main categories: • Technical Assessment to evaluate the performance of the developed functions and collect information and data for safety impact assessment. • User-Related Assessment to assess the functions from the user perspective, and also to provide further input to the safety impact assessment. Impact Assessment to estimate how and how much the functions influence traffic safety. When dealing with the above-mentioned assessments, the challenge is the fact that every Vertical Sub Project (VSP) SECONDS, INCA and EMIC, includes various functions and address different kind of situations where some are just supportive for normal driving and some intervenes in emergency situations. These different functions can be assessed individually or being part of a complete system, so interactions between them have to be taken into account. Moreover, the availability of tools and prototype vehicles has to be assured. The evaluation framework, which is described in more detail in D7.2, is built on the results and experiences from previous European projects, especially from the PReVAL project. Starting from the research questions, which have been described in D7.1, hypotheses were defined in D7.2. The research questions and hypotheses have been updated through feedback from the VSPs. The next step is the definition of the indicators and the development of the test and validation plans. In order to evaluate the developed ADAS, an evaluation framework is required. Therefore, a horizontal subproject called “Evaluation and Legal Aspects” is part of interactIVe which main objective is to provide this framework and give support to the vertical subprojects in their evaluation work. The purpose of this deliverable is to present the test and validation plans for the specific functions and outline the assessment of the test procedures which includes studying the feasibility of conducting test scenarios, setting up and running tests and obtaining data on the indicators. It also includes a methodology for safety impact assessment and an overview of the tools and equipment that will be used during the process. The tests will reveal how the functions work according to function description, requirements and also how the functions are accepted and received from a user perspective by accepting or rejecting the proposed hypotheses and obtained answers for the research questions about the definition of relevant aspects to develop Advanced Driver Assistance Systems (ADAS).
  •  
8.
  • Lesemann, Micha, et al. (författare)
  • Final report
  • 2011
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • This report sums up the activities performed during the complete duration of the project from January 2008 until December 2010. Following the motivation for testing and evaluation of active safety functions, the technical development within the project is described. This includes the derivation of relevant traffic scenarios, a collection of potential test approaches as well as the proposed testing protocols and a collection of experiences made during the application of the protocols. Besides the results of the project, open issues and weaknesses in connection with future research need are discussed herein. Furthermore, links to existing initiatives and projects in the same domain are described. An important part is also the documentation of a critical debate about the results of the project that was held during the final demonstration event. Representatives of all relevant stakeholders including the automotive industry, governing and legislative institutions as well as research and academia discussed and commented the achievements, thus giving important input for future research and other initiatives.
  •  
9.
  • Rösener, Christian, et al. (författare)
  • A Comprehensive Evaluation Approach for Highly Automated Driving
  • 2017
  • Ingår i: Enhanced Safety of Vehicles. ; , s. 1-13
  • Konferensbidrag (refereegranskat)abstract
    • Since the last decade, development efforts by academia and industry for automated driving functions have increased significantly. Also, the European research project AdaptIVe is looking into this topic. Due to the large operation spaces and various complex situations that are covered by these functions, efforts for evaluation increase also significantly. Within AdaptIVe, a comprehensive evaluation approach for automated driving functions ranging from SAE level 2-4 has been developed [1]. The approach splits the evaluation into technical, user-related, in-traffic and impact assessment addressing safety and environmental effects of automated driving. For each evaluation type appropriate test tools and methods are selected e.g. field test for technical assessment, trials on test track and in real traffic for the user-related assessments and simulations for the in-traffic and impact assessment. Next to the assessment type also the characteristics of the function must be considered when deciding for specific test tools. Hence, besides to the level of automation [8] the automated driving functions are classified into continuous and event-based operating functions. Whereas event-based operating functions are only operating for a short period in time (e.g. automated parking), continuous operating functions are, once they are active, operating for longer time periods (e.g. highway automation). Based on the classification the aspects to be evaluated and test methods are selected for all assessment types. The developed methodology has been applied to several automated driving functions developed within AdaptIVe. As an example, for the technical assessment of continuous operating functions it has been assessed whether the driving behavior of the developed functions is similar to human driving behavior and therefore not disturbing human traffic. In the user-related assessment, issues related to driver behavior, understanding of automation, trust, mental workload, resuming control, vigilance, usability and acceptance has been looked at. In this paper the key aspects of the AdaptIVe evaluation methodology for technical, user-related, in-traffic and impact assessment are presented as well as the key results of the application of this methodology on the within AdaptIVe developed automated driving functions.
  •  
10.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 11

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy