News                             Talks                             Teaching

Open Topics

Currently Running Topics

  • You don't find your topic here? Get in contact with me to discuss your own idea!

If you are interested in a topic which is not listed here please do not hesitate to contact me.

Master's Thesis:

Nowadays, constrains of vehicle development projects continuously tend to be more restrictive, shortening development and testing time, while requesting higher specifications. The development of vehicle steering and handling is strongly based on subjective assessments (SA), done by expert drivers on physical vehicles. This is a time consuming and costly procedure, which could be more effective by e.g. shortening testing and data processing time. But also by increasing the quality of the gathered SA data. Previous studies have identified that it would be convenient to reduce drivers’ rate spread. A potential way of achieving these goals might be by improving SA methods, some examples could be: 
  • assuring that all drivers understand properly the SA questions and how they should be tested, 
  • helping drivers not to forget testing any of the given questions,
  • facilitating drivers to run the same manoeuvres and to keep the required speed and/or lateral accelerations,
  • suggesting drivers which test to be done in which test track, or even in which sector of the track,
  • supporting drivers with objective test data information,
  • presenting drivers with reference information about other tested vehicles,
  • assisting the rating process with a continuous rating scale complemented with visual information,
  • enhancing drivers’ SA documentation.

All this support functions could be implemented in an electronic SA tool. Thus, it is envisioned that test drivers will be supported with a subjective assessment table computer App reducing cost, time and effort. But these positive effects still need to be proved.

This research thesis aims to answer to the aforementioned research question, in order to support the development of the procedures for subjective assessment of vehicle dynamics. The thesis should address:
  • Identifying how vehicle dynamic SA procedures can be supported by modern computer tablets capacities.
  • Programming a computer tablet HMI App based on that. 
  • Develop and run a vehicle dynamic test in order to compare the efficiency of the traditional testing method versus the enhanced method, with the new assessment tool; as well as to evaluate the acceptance of the new tool and method within the test drivers group.
  • Evaluate the result, identify the advantages and disadvantages arisen with the new method and suggest improvements and future work.
  • Documentation of the results in a thesis report and make a mid-project and a final presentation. 

Research question: Could the effectiveness of vehicle dynamics subjective evaluations be improved, shortening test time and rising gathered data quality, by means of a computer tablet assessment tool?

Master's Thesis:

Automated driving is a very popular topic nowadays within vehicle engineering. However, automated driving is only a part of the task at hand before a human driver or operator interaction can be reduced to a minimum during a transport mission. When a construction truck shall become fully automated there are a lot of activities that need to be automated in addition to automated driving. For example, automatically tipping the load, in such a manner that the tipper’s angle rate is controlled such that the flow of transported material is as desired during tipping. Another issue is that the tipper becomes empty and no material is left inside the tipper. Safety of tipping, a manual driver estimates will it be safe to tip my load in this position? Now the automated functionality needs to consider slope and bank angle under the vehicle, and the change of center of gravity during tipping.

Another consideration is that the tipping activity needs to be coordinated with the automated driving. For example, when putting new gravel on a road, a certain road segment needs to get an even flow rate of transported material which matches the longitudinal velocity of the vehicle. Other considerations are that the automated functions must be better, faster, and safer than a human operator. To manage this, a layered software architecture is proposed. It is important to understand and resolve the dependability between activity management and driving activity. Who is responsible for vehicle stability? Is it the driving functionality which already knows in detail the vehicle configuration that also is responsible for not tilt or roll over during tipping? Who is controlling suspension level height during tipping? In order to answer those questions, the existing software architecture will have to be extended by artifacts discovered or created in the course of the thesis.

Tipping is just one example of an activity. All types of loading and unloading a truck are considered activities. Other equipment may be mounted on the truck, performing activities either when standing still or while driving. So in short, all tasks that are not directly connected to the driving itself are considered activities.

1)  Review literature for how similar layered architectures have solved dependability within same layer. Propose how activity management should be designed when some superstructures are not built by the OEM and how it could be if all devices were integrated by the OEM

2) Implementation of software for activity management. Demonstration on an 8x4 FMX which will be automatically driven at Hällered Testing construction site, where it will unload and load into and from a silo.

Master's Thesis/Bachelor's Thesis:

This project aims for evaluating a quality means in open source project: Code review/gatekeeper. Such an approach would involve another programmer before a code change is included in the main project code base. One could think that successfully applied code review/involving gatekeepers would result in less bugs found in code contributed from developers, who are involved only for a short period so far and who are not yet that familiar with all aspects of the entire code base. The reason is that developers, who are more experienced and more familiar with the entire project, can better estimate the consequences and side effects, if such contributed code would be included.

On the example of open source projects like from the Apache Foundation, different metrics shall be defined and applied to address the following research questions:

1) What is the characteristics of the source code part, where bugs are found and fixed, in terms of code complexity, code age, and the like?
2) How can a code contributor be classified in terms of project experience?
3) Are there correlations between project experience and bug localization?