<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.73134.2</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Research Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Driving event recognition using machine learning and smartphones</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 2; peer review: 2 approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>bin Jamal Mohd Lokman</surname>
                        <given-names>Eilham Hakimie</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Goh</surname>
                        <given-names>Vik Tor</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-4573-9493</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Yap</surname>
                        <given-names>Timothy Tzen Vun</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Ng</surname>
                        <given-names>Hu</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-9895-9978</uri>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Faculty of Engineering, Multimedia University, Cyberjaya, Selangor, 63100, Malaysia</aff>
                <aff id="a2">
                    <label>2</label>Faculty of Computing and Informatics, Multimedia University, Cyberjaya, Selangor, 63100, Malaysia</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:vtgoh@mmu.edu.my">vtgoh@mmu.edu.my</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>19</day>
                <month>12</month>
                <year>2022</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2022</year>
            </pub-date>
            <volume>11</volume>
            <elocation-id>57</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>15</day>
                    <month>12</month>
                    <year>2022</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2022 bin Jamal Mohd Lokman EH et al.</copyright-statement>
                <copyright-year>2022</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/11-57/pdf"/>
            <abstract>
                <p>
                    <bold>Background:</bold> The lack of real-time monitoring is one of the reasons for the lack of awareness among drivers of their dangerous driving behavior. This work aims to develop a driver profiling system where a smartphone&#x2019;s built-in sensors are used alongside machine learning algorithms to classify different driving behaviors.</p>
                <p>
                    <bold>Methods:</bold> We attempt to determine the optimal combination of smartphone sensors such as accelerometer, gyroscope, and GPS in order to develop an accurate machine learning algorithm capable of identifying different driving events (e.g. turning, accelerating, or braking).</p>
                <p>
                    <bold>Results:</bold> In our preliminary studies, we encountered some difficulties in obtaining consistent driving events, which had the potential to add &#x201c;noise&#x201d; to the observations, thus reducing the accuracy of the classification. However, after some pre-processing, which included manual elimination of extraneous and erroneous events, and with the use of the Convolutional Neural Networks (CNN), we have been able to distinguish different driving events with an accuracy of about 95%.</p>
                <p>
                    <bold>Conclusions:</bold> Based on the results of preliminary studies, we have determined that the proposed approach is effective in classifying different driving events, which in turn will allow us to determine driver&#x2019;s driving behavior.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Machine learning</kwd>
                <kwd>driver profiling</kwd>
                <kwd>smartphone</kwd>
                <kwd>convolutional neural networks</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1" xlink:href="http://dx.doi.org/10.13039/501100003093">
                    <funding-source>Ministry of Higher Education, Malaysia</funding-source>
                    <award-id>FRGS/1/2020/TK02/MMU/02/1</award-id>
                </award-group>
                <funding-statement>The researchers sincerely appreciate and express gratitude for financial support from the Ministry of Higher Education, Malaysia, under the Fundamental Research Grant Scheme with grant number FRGS/1/2020/TK02/MMU/02/1.</funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
        <notes>
            <sec sec-type="version-changes">
                <label>Revised</label>
                <title>Amendments from Version 1</title>
                <p>Corrections have been made for grammatical and typological errors as highlighted by the reviewers. Some additional information about the experimental setup has also been included in the "Data collection" section.&#x00a0;Figure 3 and the title were also revised.</p>
            </sec>
        </notes>
    </front>
    <body>
        <sec sec-type="intro">
            <title>Introduction</title>
            <p>Driver behavior strongly influences road safety
                <sup>
                    <xref ref-type="bibr" rid="ref-1">1</xref>
                </sup> and is currently the main contributor to traffic fatalities. Although many recorded incidents are caused by human errors, researchers suggest that drivers who exhibit a more aggressive driving style are more likely to be engaged in an accident on the road
                <sup>
                    <xref ref-type="bibr" rid="ref-2">2</xref>
                </sup>. In 2018, a total of 548,598 cases of road accidents have been recorded in Malaysia with 6,284 of them resulting in fatalities
                <sup>
                    <xref ref-type="bibr" rid="ref-3">3</xref>
                </sup>. To add to that, the Malaysian Institute of Road Safety Research Institute (MIROS) predicts that the number of fatalities will continue to increase up to 10,716 by the end of 2020
                <sup>
                    <xref ref-type="bibr" rid="ref-4">4</xref>
                </sup>. Driver profiling attempts to understand and monitor the driver&#x2019;s behaviour in real-time, leveraging safer and more responsible driving.</p>
            <p>Driving style profiling is the process of collecting driving data (e.g., acceleration, braking, speed, turning rate, location) then applying them to classification models in order to generate a score to determine whether their driving style is safe or unsafe. Driver profiling has gained an increased in demand particularly in the insurance field and rental fleets. For example, AXA FlexiDrive rewards their customers with up to a 20% discount off their insurance premiums if they display good driving behaviour
                <sup>
                    <xref ref-type="bibr" rid="ref-5">5</xref>
                </sup>. In the rental car industry, rental companies turn to RentalMatics, an IoT solution to track rental fleets in real time
                <sup>
                    <xref ref-type="bibr" rid="ref-6">6</xref>
                </sup>. A telematics unit (also called black box) is fitted into a car to gather the relevant data needed to monitor and track the vehicle&#x2019;s location and behaviour
                <sup>
                    <xref ref-type="bibr" rid="ref-7">7</xref>
                </sup>.</p>
            <p>Today&#x2019;s smartphone is embedded with advanced motion sensors which is suitable for data collection. Smartphones have access to a suite of advanced sensors including accelerometer, gyroscope, magnetometer, gravity sensors and GPS. Previous works like
                <sup>
                    <xref ref-type="bibr" rid="ref-8">8</xref>&#x2013;
                    <xref ref-type="bibr" rid="ref-11">11</xref>
                </sup> proved that if smartphones are properly calibrated, they could be viable alternatives to the conventional telematics unit for monitoring driver behaviour.</p>
            <p>This research aims to create a viable system to gather data through a mobile device and apply machine learning algorithms to classify different types of driving events. The research will explore the data gathering phase, where a smartphone will be used as a data collection device to replace the telematics device. Initial calibration of the motion sensors will be applied to ensure the most accurate reading of data for any vehicle. Machine learning algorithms will then be trained and tested to ensure the accuracy in determining different driving events such as careful, normal, careless, and dangerous.</p>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <p>This project was divided into two main parts; the first part was the data collection part which is to develop an intuitive smartphone application with the correct combination of sensors to gather raw data on basic vehicular movements and the second part is applying machine learning to train and classify different driving patterns.</p>
            <sec>
                <title>Data collection</title>
                <p>Data collection utilized the smartphone&#x2019;s sensors including accelerometer, gyroscope, and GPS. A Samsung Galaxy S10 was utilized and placed on the center dashboard using a phone mount. The accelerometer&#x2019;s readings (
                    <italic toggle="yes">x</italic>, 
                    <italic toggle="yes">y</italic> and 
                    <italic toggle="yes">z</italic> axes) relative to the phone position were recorded every 100ms for the duration of the data collection. The gyroscope sensor was used to measure the vehicle&#x2019;s rate of rotation while the GPS was used to calculate the speed of the vehicle. 
                    <xref ref-type="fig" rid="f1">Figure 1</xref> shows the user interface of the smartphone app. The app recorded several driving events such as:</p>
                <list list-type="bullet">
                    <list-item>
                        <p>Right turns (90&#x00b0;)</p>
                    </list-item>
                    <list-item>
                        <p>Left turns (90&#x00b0;)</p>
                    </list-item>
                    <list-item>
                        <p>Acceleration</p>
                    </list-item>
                    <list-item>
                        <p>Braking</p>
                    </list-item>
                </list>
                <p>The driving events were attempted at a constant speed of 30km/h. For each driving event, 30 sets of readings were collected in total.</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>Figure 1. </label>
                    <caption>
                        <title>Screenshot of App.</title>
                        <p>The figure shows the user interface of the data gathering app where readings from the smartphone&#x2019;s accelerometer and gyroscope are updated in real-time.</p>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142216/8e02b555-c3ba-43c4-8d13-766864b50ab0_figure1.gif"/>
                </fig>
            </sec>
            <sec>
                <title>Data classification</title>
                <p>The classification technique employed to assess the implementation of this approach was the 1-Dimensional Convolutional Neural Network (CNN) and the CNN model was built using Tensorflow and Keras. Prior to fitting the machine learning model with data, the data was pre-processed beforehand to overcome problems such as unbalanced data or redundant data which could cause overfitting of the model.</p>
                <p>Pre-processing began by balancing the data to ensure that the data points for all driving events are equal to prevent skewing of results. Data standardization was also implemented before model fitting. This step is vital to ensure that the model can handle lower valued numbers as the data from the sensors has fluctuations which would cause the result to be inaccurate and require more processing to compensate. Data standardization &#x2018;minimizes&#x2019; the amplitude of the data into a form that is much easier to handle by the computer. Frame preparation was done during the pre-processing stage where the frame size was selected to be four seconds and the hop size was chosen to have an overlap of 24 data points. A total of 240 frames were created to accommodate the sample size. The sample data was then split into 80% for training set and 20% testing set.</p>
                <p>After pre-processing, the CNN layer was built. The neural network layer was built through trial and error to ensure the outcome produces a good-fit model graph. An initial 1-dimensional CNN layer called &#x2018;Conv1D&#x2019; was created. The layer develops a convolutional kernel that convolves with the layer input over a single dimensional space to produce a tensor of outputs. Following the initial layer, an activation layer called the Rectified Linear Unit (ReLU) was applied as it is the ideal activation layer for Multilayer Perceptron (MLP) and CNN. ReLU is an activation function that utilizes simple arithmetic that will output the value directly if it is more than 0.0, and will output 0.0 if the input is less than 0.0
                    <sup>
                        <xref ref-type="bibr" rid="ref-12">12</xref>
                    </sup>. After that, a pooling layer by the name of &#x2018;MaxPool1D&#x2019; was applied to reduce the number of feature maps by taking the maximum value over a certain pool size. This layer is recommended in CNN models as it reduces variance and minimizes computations
                    <sup>
                        <xref ref-type="bibr" rid="ref-13">13</xref>
                    </sup>. A &#x2018;Dropout&#x2019; layer is then applied which operates by setting the outgoing edges of each node to zero to minimize overfitting
                    <sup>
                        <xref ref-type="bibr" rid="ref-14">14</xref>
                    </sup>. A &#x2018;Dense&#x2019; layer is applied to allow the neurons in the &#x2018;Dense&#x2019; layer to receive input from neurons of the previous layer
                    <sup>
                        <xref ref-type="bibr" rid="ref-15">15</xref>
                    </sup>. Finally, a &#x2018;Softmax&#x2019; layer is applied to convert the output into a probability distribution. 
                    <xref ref-type="fig" rid="f2">Figure 2</xref> visualizes the 1-dimension CNN used for this research.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>Figure 2. </label>
                    <caption>
                        <title>1-D Convolution Neural Network.</title>
                        <p>The illustration above shows the various layers used to develop the machine learning model. The various layers include Conv1D layers, Rectified Linear Unit (ReLU) Activation function, Pooling layers, Dropout, and Dense layers.</p>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142216/8e02b555-c3ba-43c4-8d13-766864b50ab0_figure2.gif"/>
                </fig>
            </sec>
        </sec>
        <sec sec-type="results | discussion">
            <title>Results and discussion</title>
            <p>The readings from the smartphone&#x2019;s accelerometer for the various driving events are shown in 
                <xref ref-type="fig" rid="f3">Figure 3</xref>. Due to the vibrations of the vehicle during idling and during movements, a few spikes in the amplitude can be seen. The spikes in the accelerometer readings during idling could also be caused by the vehicle engine running.</p>
            <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                <label>Figure 3. </label>
                <caption>
                    <title>Accelerometer readings.</title>
                    <p>(
                        <bold>a</bold>) The 
                        <italic toggle="yes">x</italic>-axis of the accelerometer form peaks at each Right turn. (
                        <bold>b</bold>) The Left turn creates an opposite pattern from Right turns as each turning point forms successive valleys upon the 
                        <italic toggle="yes">x</italic>-axis. (
                        <bold>c</bold>) Accelerate event creates valleys on the 
                        <italic toggle="yes">z</italic>-axis of the accelerometer. (
                        <bold>d</bold>) The Brake event indicates an opposite pattern where peaks are formed on the 
                        <italic toggle="yes">z</italic>-axis of the accelerometer at each braking point.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142216/8e02b555-c3ba-43c4-8d13-766864b50ab0_figure3.gif"/>
            </fig>
            <p>The different types of driving events that were demonstrated could be easily distinguished between each other. In 
                <xref ref-type="fig" rid="f3">Figure 3(a)</xref>, the accelerometer readings for the 
                <italic toggle="yes">x</italic>-axis displays multiple peaks successively. Each peak in the graph translates to a right turn where the highest point of each peak translates to the highest force during each turn.</p>
            <p>On the other hand, the readings for left turn events show the opposite result where in 
                <xref ref-type="fig" rid="f3">Figure 3(b)</xref>, the accelerometer readings for the 
                <italic toggle="yes">x</italic>-axis displays multiple valleys successively. Each valley translates to a single left turn in real life. However, 
                <xref ref-type="fig" rid="f3">Figures 3(a) and 3(b)</xref> display a close resemblance in the 
                <italic toggle="yes">y</italic> and 
                <italic toggle="yes">z</italic>-axis during the early phase of the recording, where the 
                <italic toggle="yes">y</italic> and 
                <italic toggle="yes">z</italic>-axis show multiple peaks followed by multiple valleys. This could possibly be caused by the vibrations coming out from the engine of the car moving from a stationary position.</p>
            <p>In 
                <xref ref-type="fig" rid="f3">Figure 3(c)</xref>, the accelerometer values show readings for the vehicle during acceleration. A series of valleys are formed in the 
                <italic toggle="yes">z</italic>-axis where each valley translates to an acceleration event being performed. The intensity of the valley is not very pronounced as the throttle was gradually applied to ensure smooth acceleration. If the accelerator was pressed more aggressively, we predict the 
                <italic toggle="yes">z</italic>-axis value of the accelerometer to be more pronounced. 
                <xref ref-type="fig" rid="f3">Figure 3(d)</xref> shows the accelerometer readings for the vehicle under braking events. The output is the opposite of acceleration event, as the 
                <italic toggle="yes">z</italic>-axis of the accelerometer form peaks at each point of braking. Each peak is much more visually defined as the brakes were applied much more aggressively to fully stop the car from 30km/h. In both 
                <xref ref-type="fig" rid="f3">Figure 3(c) and 3(d)</xref>, the 
                <italic toggle="yes">x</italic> and 
                <italic toggle="yes">y</italic>-axis produced a few peaks followed by valleys. This could be caused by the inertia acting on the vehicle or the engine vibrations in each driving event.</p>
            <p>As observed from the accelerometer plots, each driving event could be distinguished from the other as each event has its specific features. For left and right turns there is a distinct difference in their 
                <italic toggle="yes">x</italic>-axes while acceleration and braking events can be distinguished in the 
                <italic toggle="yes">z</italic>-axis. The difference in features for each driving event could be highly advantageous as we could train machine learning algorithms to identify their specific features and automatically categorize each of the driving events.</p>
            <p>The machine learning experiment was carried out in two phases, the training phase and the test phase. 80% of the total sample data was used to train the 1-CNN model and 20% of the sample data was used to test the accuracy of the trained model. After numerous experiments, it is discovered that the most optimal epoch value is 100 combined with a batch size of 32 which produced a model accuracy of 95.83%. 
                <xref ref-type="fig" rid="f4">Figure 4</xref> shows the test results of the machine learning model
                <sup>
                    <xref ref-type="bibr" rid="ref-16">16</xref>
                </sup>.</p>
            <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                <label>Figure 4. </label>
                <caption>
                    <title>Model Evaluation.</title>
                    <p>The figure visualizes the evaluation results for the model when classifying the testing set where an accuracy of 95.83% was obtained.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142216/8e02b555-c3ba-43c4-8d13-766864b50ab0_figure4.gif"/>
            </fig>
            <p>The Model Loss Curve in 
                <xref ref-type="fig" rid="f5">Figure 5</xref> shows that the training loss decreases as the epoch value increases. Upon reaching epoch value 80, the training loss stops decreasing and stabilizes. Similarly, the validation loss decreases as the epoch value increases but stabilizes at around 80 epochs. It can be observed that the validation loss and training loss have a very minimal gap between them which states that the model is a good fit model. Continued training of this model will likely cause the model to be overfitted.</p>
            <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                <label>Figure 5. </label>
                <caption>
                    <title>Learning Curves.</title>
                    <p>The figure depicts the learning curves for Model Accuracy and Model Loss where each graph has a curve for Training and Validation performances.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142216/8e02b555-c3ba-43c4-8d13-766864b50ab0_figure5.gif"/>
            </fig>
            <p>
                <xref ref-type="fig" rid="f6">Figure 6</xref> visualizes that the model predicted 46 out of 48 events correctly. The two events that were wrongly predicted was an Accelerate event which was supposed to be a Left turn event and a Braking event which was supposed to be an Accelerate event. A probable reason as to why the model predicted these events wrongly is because of the high variance of data because of the difficulty in maintaining consistency in simulating the driving events. Additional pre-processing of data could also improve the accuracy of the model as it removes redundant data and noise. Increasing the epoch value could also further improve the accuracy but caution must be kept in mind to make sure that the model is not overfitted.</p>
            <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                <label>Figure 6. </label>
                <caption>
                    <title>Confusion Matrix.</title>
                    <p>The figure shows the Confusion Matrix where the prediction results are summarized to show the performance of the model.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142216/8e02b555-c3ba-43c4-8d13-766864b50ab0_figure6.gif"/>
            </fig>
            <p>Additional work could be done to improve the quality of data samples. For example, investing on a phone mount that does not wobble too much under engine vibrations. The data gathering framework could also be improved to ensure that only the relevant data samples are collected and not redundant data. For the application side, the sampling rate could also be tweaked to ensure that redundant accelerometer and gyroscope readings are not recorded.</p>
        </sec>
        <sec sec-type="conclusions">
            <title>Conclusion</title>
            <p>Smartphone sensors have improved massively over the years and prove to be a viable option when used as a data gathering apparatus to monitor driver behavior. In turn, the collected data could then be processed using machine learning algorithms to classify different driving events with high reliability. For this research we have applied the concept of Convolutional Neural Networks which works effectively in classifying different driving events with an accuracy of 95.83%.</p>
            <p>For our future work, we will continue to collect data for different driving events such as aggressive driving and careless driving. Additionally, we will feed the collected data into the machine learning model to allow it to classify an even more diverse palette of driving events. Next, we will consider adding a calibration feature to our data gathering application to allow accurate data collection without mounting the phone to a phone mount which will further improve the user experience. As there are many machine learning models suitable for classifying time-series sensor data, we will experiment with different types of machine learning models to find out which will provide the best accuracy. Finally, we will deploy the machine learning model onto a smartphone to allow real-time classification of driving style. With these steps planned, it could potentially enhance the impact of this research in terms of traffic safety which was the main goal of this paper.</p>
        </sec>
    </body>
    <back>
        <sec sec-type="data-availability">
            <title>Data availability</title>
            <p>Harvard Dataverse: Driving Events, 
                <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.7910/DVN/F5JZHF">https://doi.org/10.7910/DVN/F5JZHF</ext-link>
                <sup>
                    <xref ref-type="bibr" rid="ref-16">16</xref>
                </sup>.</p>
            <p>This project contains the following underlying data:</p>
            <p>- driving_events.db (Raw data from sensors)</p>
            <p>Data are available under the terms of the 
                <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/publicdomain/zero/1.0/">Creative Commons Zero "No rights reserved" data waiver</ext-link> (CC0 1.0 Public domain dedication).</p>
        </sec>
        <ref-list>
            <ref id="ref-1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Abojaradeh</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Jrew</surname>
                            <given-names>B</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Al-Ababsah</surname>
                            <given-names>H</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The Effect of Driver Behavior on Freeway Traffic Flow.</article-title>
                    <source>

                        <italic toggle="yes">Civ Environ Res.</italic>
</source>
                    <year>2014</year>;<volume>6</volume>(<issue>1</issue>):<fpage>39</fpage>&#x2013;<lpage>54</lpage>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/publication/282808329_The_Effect_of_Driver_Behavior_Mistakes_on_Traffic_Safety">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Roslin</surname>
                            <given-names>EN</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Azmy</surname>
                            <given-names>NSA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ghulam</surname>
                            <given-names>AM</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Factors of the &#x2018;aggressive driving&#x2019; behaviour amongst Malaysian drivers.</article-title>
                    <source>

                        <italic toggle="yes">Int J Eng Adv Technol.</italic>
</source>
                    <year>2019</year>;<volume>8</volume>(<issue>6</issue>):<fpage>3359</fpage>&#x2013;<lpage>3366</lpage>.
                    <pub-id pub-id-type="doi">10.35940/ijeat.F9503.088619</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <collab>D. of Statistics</collab>:
                    <article-title>Department of Statistics Malaysia.</article-title>Press Release,<year>2015</year>.</mixed-citation>
            </ref>
            <ref id="ref-4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Rohayu</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>Predicting Malaysian Road Fatalities for Year 2020</article-title>.<year>2020</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.researchgate.net/publication/283299518_Predicting_Malaysian_Road_Fatalities_for_Year_2020">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <article-title>What You Need To Know About Telematics Motor Insurance.</article-title>AXA Malaysia, (accessed Dec. 14, 2020).
                    <ext-link ext-link-type="uri" xlink:href="https://www.axa.com.my/What-You-Need-To-Know-About-Telematics-Motor-Insurance">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <article-title>Telematics For Rental Fleets: Shaping the Mobility Industry.</article-title>RentalMatics, (accessed Dec. 14, 2020).
                    <ext-link ext-link-type="uri" xlink:href="https://rentalmatics.com/telematics-for-rental-fleets-shaping-the-mobility-industry/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <article-title>Telematics Explained - What is Telematics?</article-title>(accessed Dec. 14, 2020).
                    <ext-link ext-link-type="uri" xlink:href="https://www.verizonconnect.com/resources/article/what-is-telematics/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>J&#x00fa;nior</surname>
                            <given-names>JF</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Carvalho</surname>
                            <given-names>E</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ferreira</surname>
                            <given-names>BV</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Driver behavior profiling: An investigation with different smartphone sensors and machine learning.</article-title>
                    <source>

                        <italic toggle="yes">PLoS One.</italic>
</source>
                    <year>2017</year>;<volume>12</volume>(<issue>4</issue>):<fpage>e0174959</fpage>.
                    <pub-id pub-id-type="pmid">28394925</pub-id>
                    <pub-id pub-id-type="doi">10.1371/journal.pone.0174959</pub-id>
                    <pub-id pub-id-type="pmcid">5386255</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Fazeen</surname>
                            <given-names>M</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Gozick</surname>
                            <given-names>B</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Dantu</surname>
                            <given-names>R</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Safe Driving Using Mobile Phones.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans Intell Transp Syst.</italic>
</source>
                    <year>2012</year>;<volume>13</volume>(<issue>3</issue>):<fpage>1462</fpage>&#x2013;<lpage>1468</lpage>.
                    <pub-id pub-id-type="doi">10.1109/TITS.2012.2187640</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Castignani</surname>
                            <given-names>G</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Derrmann</surname>
                            <given-names>T</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Frank</surname>
                            <given-names>R</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Driver behavior profiling using smartphones: A low-cost platform for driver monitoring.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Intell Transp Syst Mag.</italic>
</source>
                    <year>2015</year>;<volume>7</volume>(<issue>1</issue>):<fpage>91</fpage>&#x2013;<lpage>102</lpage>.
                    <pub-id pub-id-type="doi">10.1109/MITS.2014.2328673</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Johnson</surname>
                            <given-names>DA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Trivedi</surname>
                            <given-names>MM</given-names>
                        </name>
</person-group>:
                    <article-title>Driving style recognition using a smartphone as a sensor platform.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Conf Intell Transp Syst Proceedings ITSC.</italic>
</source>
                    <year>2011</year>;<fpage>1609</fpage>&#x2013;<lpage>1615</lpage>.
                    <pub-id pub-id-type="doi">10.1109/ITSC.2011.6083078</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <article-title>A Gentle Introduction to the Rectified Linear Unit (ReLU).</article-title>(accessed Jun. 22, 2021).
                    <ext-link ext-link-type="uri" xlink:href="https://machinelearningmastery.com/rectified-linear-activation-function-for-deep-learning-neural-networks/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-13">
                <label>13</label>
                <mixed-citation publication-type="journal">
                    <article-title>tf.keras.layers.MaxPool1D.</article-title>TensorFlow Core v2.5.0., (accessed Jun. 22, 2021).
                    <ext-link ext-link-type="uri" xlink:href="https://www.tensorflow.org/api_docs/python/tf/keras/layers/MaxPool1D">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <article-title>Dropout Neural Network Layer In Keras Explained.</article-title>by Cory Maklin | Towards Data Science, (accessed Jun. 22, 2021).
                    <ext-link ext-link-type="uri" xlink:href="https://towardsdatascience.com/machine-learning-part-20-dropout-keras-layers-explained-8c9f6dc4c9ab">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <article-title>Keras Dense Layer Explained for Beginners.</article-title>MLK - Machine Learning Knowledge, (accessed Jun. 22, 2021).
                    <ext-link ext-link-type="uri" xlink:href="https://machinelearningknowledge.ai/keras-dense-layer-explained-for-beginners/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Goh</surname>
                            <given-names>VT</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lokman</surname>
                            <given-names>JM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hakimie</surname>
                            <given-names>E</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Driving Events.</article-title>Harvard Dataverse,<year>2021</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.doi.org/10.7910/DVN/F5JZHF">http://www.doi.org/10.7910/DVN/F5JZHF</ext-link>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report158423">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.142216.r158423</article-id>
            <title-group>
                <article-title>Reviewer response for version 2</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Z'aba</surname>
                        <given-names>Muhammad Reza</given-names>
                    </name>
                    <xref ref-type="aff" rid="r158423a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r158423a1">
                    <label>1</label>Mimos Berhad, Kuala Lumpur, Federal Territory of Kuala Lumpur, Malaysia</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>17</day>
                <month>4</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Z'aba MR</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport158423" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.73134.2"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>Authors have sufficiently made amendments to previous comments.</p>
            <p>Is the work clearly and accurately presented and does it cite the current literature?</p>
            <p>Partly</p>
            <p>If applicable, is the statistical analysis and its interpretation appropriate?</p>
            <p>Not applicable</p>
            <p>Are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Partly</p>
            <p>Is the study design appropriate and is the work technically sound?</p>
            <p>Partly</p>
            <p>Are the conclusions drawn adequately supported by the results?</p>
            <p>Partly</p>
            <p>Are sufficient details of methods and analysis provided to allow replication by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Information security, cryptography</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report158424">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.142216.r158424</article-id>
            <title-group>
                <article-title>Reviewer response for version 2</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>KSM Kader Ibrahim</surname>
                        <given-names>Babul Salam</given-names>
                    </name>
                    <xref ref-type="aff" rid="r158424a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-7339-427X</uri>
                </contrib>
                <aff id="r158424a1">
                    <label>1</label>Faculty of Engineering, Environment and Computing, Coventry University, Coventry, UK</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>11</day>
                <month>1</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 KSM Kader Ibrahim BS</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport158424" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.73134.2"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>I am&#x00a0;satisfied&#x00a0;with the&#x00a0;author's&#x00a0;responses to my questions/issues&#x00a0;raised&#x00a0;in my initial review. Thanks</p>
            <p>Is the work clearly and accurately presented and does it cite the current literature?</p>
            <p>Yes</p>
            <p>If applicable, is the statistical analysis and its interpretation appropriate?</p>
            <p>Yes</p>
            <p>Are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Is the study design appropriate and is the work technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions drawn adequately supported by the results?</p>
            <p>Yes</p>
            <p>Are sufficient details of methods and analysis provided to allow replication by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Sensors, Modelling and Control</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report143359">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.76760.r143359</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>KSM Kader Ibrahim</surname>
                        <given-names>Babul Salam</given-names>
                    </name>
                    <xref ref-type="aff" rid="r143359a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-7339-427X</uri>
                </contrib>
                <aff id="r143359a1">
                    <label>1</label>Faculty of Engineering, Environment and Computing, Coventry University, Coventry, UK</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>8</day>
                <month>7</month>
                <year>2022</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2022 KSM Kader Ibrahim BS</copyright-statement>
                <copyright-year>2022</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport143359" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.73134.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This paper discusses the attempt to use the smartphone sensors such as accelerometer, gyroscope, and GPS in order to develop an accurate machine learning algorithm capable of identifying different driving events (e.g. turning, accelerating, or braking). The convolutional neural network (CNN) has been applied to classify these different events.</p>
            <p> &#x00a0; 
                <list list-type="bullet">
                    <list-item>
                        <p>The title should be corrected as the work recognises the driving events, not the driving style.</p>
                    </list-item>
                    <list-item>
                        <p>The methodology should be improved by explaining and showing where the smartphone is mounted on the screen or on the dashboard. The illustration may help the reader.</p>
                    </list-item>
                    <list-item>
                        <p>Mounting on the dashboard is not a good option as there are vibrations due to the car&#x2019;s engine. This should be avoided.</p>
                    </list-item>
                    <list-item>
                        <p>The labels in Figure 3 are not very clear.</p>
                    </list-item>
                </list> &#x00a0;&#x00a0;</p>
            <p> Please proofread the document before submission. There are too many grammatical mistakes&#x00a0;and need to be addressed as follows-</p>
            <p> </p>
            <p> Replace</p>
            <p> Conclusions: Based on the results of preliminary studies, we have determined that the proposed approach is effective in classifying different driving events, which in turn will allow us to determine driver&#x2019;s driving behavior.</p>
            <p> with</p>
            <p> Conclusions: Based on the results of preliminary studies, we have determined that 
                <bold>the</bold> proposed approach is effective in classifying different driving events, which in turn will allow us to determine driver&#x2019;s driving behavior.</p>
            <p> </p>
            <p> Replace</p>
            <p> Driver profiling attempts to understand and monitor the driver&#x2019;s behaviour in real-time, leveraging a safer and more responsible driving.</p>
            <p> with</p>
            <p> Driver profiling attempts to understand and monitor the driver&#x2019;s behaviour in real-time, leveraging safer and more responsible driving.&#x00a0;</p>
            <p> </p>
            <p> Replace</p>
            <p> The app recorded several driving event such as:&#x00a0;</p>
            <p> with</p>
            <p> The app recorded several driving 
                <bold>events</bold> such as:</p>
            <p> </p>
            <p> Replace</p>
            <p> Prior to fitting the machine learning model with data, the data was pre-processed beforehand to overcome problems such as unbalanced data or redundant data which could cause overfitting of model.</p>
            <p> with</p>
            <p> Prior to fitting the machine learning model with data, the data was pre-processed beforehand to overcome problems such as unbalanced data or redundant data which could cause overfitting of 
                <bold>the</bold> model.</p>
            <p> </p>
            <p> Replace</p>
            <p> The neural network layer was built following multiple trial and errors to ensure the outcome produces a good-fit model graph.</p>
            <p> with</p>
            <p> The neural network layer was built following multiple 
                <bold>trials </bold>and errors to ensure the outcome produces a good-fit model graph.</p>
            <p> </p>
            <p> Replace</p>
            <p> Figure 3. Accelerometer readings. (a) The x-axis of the accelerometer form peaks at each Right turning. (b) Left turn creates an opposite pattern from Right turns as each turning point forms successive valleys upon the x-axis. (c) Accelerate event creates valleys on the z-axis of the accelerometer. (d) Brake event indicates an opposite pattern where peaks are formed on the z-axis of the accelerometer at each braking point.</p>
            <p> with</p>
            <p> Figure 3. Accelerometer readings. (a) The x-axis of the accelerometer form peaks at each Right 
                <bold>turn</bold>. (b) 
                <bold>The</bold> Left turn creates an opposite pattern from Right turns as each turning point forms successive valleys upon the x-axis. (c) Accelerate event creates valleys on the z-axis of the accelerometer. (d) 
                <bold>The</bold> brake event indicates an opposite pattern where peaks are formed on the z-axis of the accelerometer at each braking point.</p>
            <p> </p>
            <p> Replace</p>
            <p> Figure 3(a) and 3(b) display a close resemblance in the y and z-axis during the early phase of the recording, where the y and z-axis shows multiple peaks followed by multiple valleys.</p>
            <p> with</p>
            <p> 
                <bold>Figures </bold>3(a) and 3(b) display a close resemblance in the y and z-axis during the early phase of the recording, where the y and z-axis 
                <bold>show </bold>multiple peaks followed by multiple valleys.</p>
            <p> </p>
            <p> Replace</p>
            <p> </p>
            <p> As observed from the accelerometer plots, each driving event could be distinguished from each other as each event has their specific features.</p>
            <p> with</p>
            <p> As observed from the accelerometer plots, each driving event could be distinguished from 
                <bold>the other</bold> as each event has
                <bold> its</bold> their specific features.</p>
            <p> </p>
            <p> Replace</p>
            <p> The machine learning experiment was carried in two phases, the training phase, and test phase</p>
            <p> with</p>
            <p> The machine learning experiment was carried
                <bold> out </bold>in two phases, 
                <bold>the</bold> training phase and 
                <bold>the</bold> test phase</p>
            <p> </p>
            <p> Replace</p>
            <p> A probable reason as to why the model predicted these events wrongly is because of high variance of data because of the difficulty in maintaining consistency in simulating the driving events.</p>
            <p> with</p>
            <p> A probable reason why the model predicted these events wrongly is because of
                <bold> the</bold> high variance of data because of the difficulty in maintaining consistency in simulating the driving events.</p>
            <p> </p>
            <p> Replace</p>
            <p> It can be observed that the validation loss and training loss has very minimal gap between them which states that the model is a good fit model</p>
            <p> with</p>
            <p> It can be observed that the validation loss and training loss have
                <bold> a</bold> very minimal gap between them which states that the model is a good fit model</p>
            <p> </p>
            <p> Replace</p>
            <p> Figure 6 visualizes that out of the model predicted 46 out of 48 events correctly.&#x00a0;</p>
            <p> with</p>
            <p> Figure 6 visualizes that the model predicted 46 out of 48 events correctly.&#x00a0;</p>
            <p> </p>
            <p> Replace</p>
            <p> Next, we will consider adding a calibration feature into our data gathering application to allow accurate data collection without mounting the phone to a phone mount which will further improve user experience.&#x00a0;</p>
            <p> with</p>
            <p> Next, we will consider adding a calibration feature to our data gathering application to allow accurate data collection without mounting the phone to a phone mount which will further improve 
                <bold>the</bold> user experience.</p>
            <p>Is the work clearly and accurately presented and does it cite the current literature?</p>
            <p>Yes</p>
            <p>If applicable, is the statistical analysis and its interpretation appropriate?</p>
            <p>Yes</p>
            <p>Are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Yes</p>
            <p>Is the study design appropriate and is the work technically sound?</p>
            <p>Yes</p>
            <p>Are the conclusions drawn adequately supported by the results?</p>
            <p>Yes</p>
            <p>Are sufficient details of methods and analysis provided to allow replication by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Sensors, Modelling and Control</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
        <sub-article article-type="response" id="comment9130-143359">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Goh</surname>
                            <given-names>Vik Tor</given-names>
                        </name>
                        <aff>Multimedia University, Malaysia</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>14</day>
                    <month>12</month>
                    <year>2022</year>
                </pub-date>
            </front-stub>
            <body>
                <p>The title will be revised to &#x201c;Driving Event recognition using machine learning and smartphones&#x201d; to better reflect the content of the paper. However, this is subject to the approval of F1000&#x2019;s editors.</p>
                <p> </p>
                <p> The smartphone was placed on the center dashboard via a phone mount. The paper has been revised to include this information for better clarity.</p>
                <p> </p>
                <p> We have already tested different position such as left side of the dashboard, right side of the dashboard, and even on the center console below the radio but came to a conclusion that the center of the dashboard was the best option for this car.</p>
                <p> </p>
                <p> The labels in Figure 3 have been enhanced for better clarity.</p>
                <p> </p>
                <p> All suggested amendments have been done. The rest of the document has also been proofread to the best of our ability to minimise grammatical and typological errors. Thank you very much for highlighting the errors.</p>
            </body>
        </sub-article>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report122549">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.76760.r122549</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Z'aba</surname>
                        <given-names>Muhammad Reza</given-names>
                    </name>
                    <xref ref-type="aff" rid="r122549a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r122549a1">
                    <label>1</label>Mimos Berhad, Kuala Lumpur, Federal Territory of Kuala Lumpur, Malaysia</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>28</day>
                <month>2</month>
                <year>2022</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2022 Z'aba MR</copyright-statement>
                <copyright-year>2022</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport122549" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.73134.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>The article describes an attempt to use mobile phone as an apparatus to collect data regarding certain driving events such as turning, accelerating or braking. Then, convolutional neural network (CNN) is applied to classify these different events. The authors claim that CNN managed to classify the events with a high accuracy (95.83%).</p>
            <p> </p>
            <p> I think the title is a bit misleading. The title mentions about 
                <bold>driving&#x00a0;style recognition</bold>. However, what the work recognises was the driving 
                <bold>events</bold> such as turning, accelerating or braking. When "style" was mentioned, I was thinking something along the lines of "careless driving" or "careful driving". In essence, I believe the work has yet to recognise the driving&#x00a0;
                <bold>style</bold>, only the driving&#x00a0;
                <bold>events</bold>. It is good if the authors can categorise several driving&#x00a0;
                <bold>styles</bold>&#x00a0;according to a set of driving&#x00a0;
                <bold>events</bold>.</p>
            <p> </p>
            <p> The authors mention that in order to improve data collection, it is proposed to use a phone mount in order to eliminate inaccurate readings due to engine vibrations. I think the authors should do this and include the results in the article since I think a phone mount is not that expensive and is widely available. The results can then perhaps be compared with the data collected without using the phone mount. This is to see how much accuracy can be gained.</p>
            <p> </p>
            <p> The authors also did not state the model of the smartphone used in the work. It is also good if different smartphone models are used in order to make a comparison.</p>
            <p>Is the work clearly and accurately presented and does it cite the current literature?</p>
            <p>Partly</p>
            <p>If applicable, is the statistical analysis and its interpretation appropriate?</p>
            <p>Not applicable</p>
            <p>Are all the source data underlying the results available to ensure full reproducibility?</p>
            <p>Partly</p>
            <p>Is the study design appropriate and is the work technically sound?</p>
            <p>Partly</p>
            <p>Are the conclusions drawn adequately supported by the results?</p>
            <p>Partly</p>
            <p>Are sufficient details of methods and analysis provided to allow replication by others?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Information security, cryptography</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
        <sub-article article-type="response" id="comment9129-122549">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Goh</surname>
                            <given-names>Vik Tor</given-names>
                        </name>
                        <aff>Multimedia University, Malaysia</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>14</day>
                    <month>12</month>
                    <year>2022</year>
                </pub-date>
            </front-stub>
            <body>
                <p>The title will be revised to &#x201c;Driving 
                    <bold>event</bold> recognition using machine learning and smartphones&#x201d; to better reflect the content of the paper. However, this is subject to the approval of F1000&#x2019;s editors.</p>
                <p> </p>
                <p> A phone mount was indeed used to collect data in the current experimental setup. The mount was semi-rigid as this provided a good transfer of energy/vibration from the vehicle as well as some dampening against minor vibrations. It functioned as intended but also introduced some unwanted wobble due to its semi-rigid build. As such, in our future experiments, we will investigate using other models of mounts with different build quality.</p>
                <p> </p>
                <p> The experiments used a Samsung Galaxy S10 as the data collector. The paper has been revised to include some additional information about the data collection setup. A comparison of different smartphone models was not in the scope of the current phase but will be considered in our future experiments.</p>
            </body>
        </sub-article>
    </sub-article>
</article>
