<?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.157582.1</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>Using machine learning based stereo camera clothing boundary recognition control system for dressing assistance support robot</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 2 not approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>ZHAO</surname>
                        <given-names>HANQING</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/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-1835-5566</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Nambo</surname>
                        <given-names>Hidetaka</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Graduate School of Natural Science and Technology Electrical Engineering and Computer Science, Kanazawa University, kanazawa, ishikawa, Japan</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:nambo@blitz.ec.t.kanazawa-u.ac.jp">nambo@blitz.ec.t.kanazawa-u.ac.jp</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>17</day>
                <month>4</month>
                <year>2025</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2025</year>
            </pub-date>
            <volume>14</volume>
            <elocation-id>447</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>3</day>
                    <month>3</month>
                    <year>2025</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 ZHAO H and Nambo H</copyright-statement>
                <copyright-year>2025</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>
                <license>
                    <license-p>The author(s) is/are employees of the US Government and therefore domestic copyright protection in USA does not apply to this work. The work may be protected under the copyright laws of other jurisdictions when used in those jurisdictions.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/14-447/pdf"/>
            <abstract>
                <p>Life support robots that can be fully autonomous clothing wear-support robotic identification control systems are challenging. Robotic-assisted dressing solutions have the potential to provide tremendous support to the elderly, patients with mobility impairments, and their caregivers. In this study, we propose an IoT control system that automatically identifies clothing wearing position boundaries and recognizes actual spatial height information using a stereo camera with computer vision. The location information of the clothes boundary was recognized use the semantic segmentation model and machine learning method. Then, using the depth measurement of the stereo camera, the spatial height position of the actual clothing boundary was calculated using the depth information. Finally, the auxiliary position movement control of the clothes-wearing support robot was carried out using the IoT method. We experimentally verified that the recognition control system can successfully achieve the recognition and control of the auxiliary position movement of the device. We performed practical experiments for the evaluation. The recognition accuracy and control accuracy in multiple situations and environmental conditions were 77.35% and 97.21%.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Assistive Robotics</kwd>
                <kwd>Computational Intelligence (Neural</kwd>
                <kwd>Fuzzy</kwd>
                <kwd>Learning</kwd>
                <kwd>etc)</kwd>
                <kwd>Robot Vision and Monitoring</kwd>
                <kwd>Vision-based Control</kwd>
                <kwd>Human-Robot Interaction</kwd>
            </kwd-group>
            <funding-group>
                <funding-statement>The author(s) declared that no grants were involved in supporting this work.</funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec1" sec-type="intro">
            <title>1. Introduction</title>
            <p>This study proposes an IoT control system that automatically identifies the position of clothing boundaries and calculates the actual spatial height distance information using a stereo camera. It is used in toilet environments where the elderly or patients have hand muscle weakness or difficulty moving their hands without the assistance of a nurse or caregiver. Pant dressing assistance system with autonomous recognition and adjustment of assisted position using a vision recognition system. The traditional boundary line recognition method has the problem of difficult recognition in complex scenes and different clothing. Moreover, in the traditional method of recognizing the actual spatial location distance, sensors in addition to the camera are required for composite computational analysis. To address this problem. Responding to different recognition scenes and recognizing multiple types of clothes. We adopted deep learning and machine learning methods for clothing boundary recognition. We utilized semantic segmentation-related algorithms for clothes boundary line identification as preliminary data processing. Eventually, the actual spatial position information of the clothing boundary line can be calculated from the multiple fusion information obtained from the stereo camera, and the position information can be fed back to the control system.</p>
            <p>Recently, depth cameras have been used in robotics, autonomous driving, and other fields. For example, object size is measured using a single camera.
                <sup>
                    <xref ref-type="bibr" rid="ref4">4</xref>
                </sup> The stereo camera object size measurement algorithm uses the Euclidean algorithm.
                <sup>
                    <xref ref-type="bibr" rid="ref5">5</xref>
                </sup> Furthermore, a single camera was used to acquire the video to calculate the length, width, and height of the object using a mathematical model.
                <sup>
                    <xref ref-type="bibr" rid="ref3">3</xref>
                </sup> Vision applications for robot dressing assistance.
                <sup>
                    <xref ref-type="bibr" rid="ref9">9</xref>,
                    <xref ref-type="bibr" rid="ref10">10</xref>
                </sup> Point cloud information or fused data with other sensing information
                <sup>
                    <xref ref-type="bibr" rid="ref11">11</xref>
                </sup> is used to obtain location information for dressing assistance. Using depth map information for top-dressing assistance.
                <sup>
                    <xref ref-type="bibr" rid="ref13">13</xref>
                </sup> This study proposed a robot-assisted dressing system. Based on stereo camera depth sensing and a deep learning algorithm, the size and position of the auxiliary position two-point measurements of the actual spatial coordinates were calculated. Utilizing IoT communication to an auxiliary device for clothing auxiliary position selection and auxiliary robot movement control. Dressing assistance through multiple fusion technologies.</p>
            <p>
                <xref ref-type="fig" rid="f1">
Figure 1</xref> shows the 3D simulation image, and 
                <xref ref-type="fig" rid="f2">
Figure 2</xref> shows the actual toilet clothing dressing support robot. The toilet clothing dressing support robot is a branch of life support robot. It is a robot that solves the aging problem and provides assistance in living for the elderly. For example, in the toilet, hand muscle weakness, or hand immobility, Dressing Assistance will provide great convenience. There are five main areas of life support robots: mobility, food, toilets, bathing, and caregiving support. Life Support Robot has five main areas: mobility, food, toilet, bathing, and caregiving support. These five types of support are not only geared toward the elderly and patients, but can also reduce the workload of medical workers.</p>
            <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                <label>
Figure 1. </label>
                <caption>
                    <title>3D Simulation of Bathroom clothes dress support robot.</title>
                </caption>
                <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure1.gif"/>
            </fig>
            <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                <label>
Figure 2. </label>
                <caption>
                    <title>Bathroom clothes dress support robot.</title>
                </caption>
                <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure2.gif"/>
            </fig>
            <p>In recent years, deep learning models for the recognition and extraction of object edge contours(e.g., HED
                <sup>
                    <xref ref-type="bibr" rid="ref17">17</xref>
                </sup> and RankED
                <sup>
                    <xref ref-type="bibr" rid="ref18">18</xref>
                </sup>) have made significant progress. However, the identification and extraction of boundaries in specific areas has many challenges. For example, CASENet
                <sup>
                    <xref ref-type="bibr" rid="ref15">15</xref>
                </sup> and RINDNet
                <sup>
                    <xref ref-type="bibr" rid="ref16">16</xref>
                </sup> are semantic segmentation edge boundary recognitions of objects. However, semantic segmentation edge boundary recognition has difficulties such as difficult training, low accuracy and inability to be applied with a designated part of the edge boundary recognition. In this study, we propose a multi-stage approach with good accuracy that is applicable to complex scenarios and capable of identifying recognition solutions for specific boundaries in specific regions. Semantic segmentation and SVM models are used in machine learning for specific boundary recognition. There are also many challenges in selecting a semantic segmentation model, for example, because the image recognition in this task is real-time image data and requires stability and high accuracy. In popular models, we present evaluations. The final selection was the PSPnet model with high semantic segmentation accuracy; however, the model with high semantic segmentation accuracy does not have good real-time processing capability. If a model with high a real-time recognition capability is chosen, the recognition accuracy of the model is reduced. To ensure recognition accuracy, we did not choose a model with a high real-time recognition. Subsequently, the SVM algorithm was used for boundary computation using semantic segmentation results. This greatly increases the cost of computational time; therefore, before calculating using the SVM algorithm, we used the data dimensionality reduction process to improve the calculation speed. Improved real-time recognition performance.</p>
            <p>Second, it is related to distance sensors. In this study, we did not use traditional ultrasonic ranging or laser ranging sensors. Instead, a depth camera combined with an image algorithm was used to obtain the actual distance. This can be combined with semantic segmentation and SVM to obtain specific boundaries to compute the actual distance in space between pixel points in an image. This makes it easier to perform fused data processing than to use data information from traditional ranging sensors. A depth camera cannot directly acquire the actual spatial distance between the two points of an image pixel. In previous studies, the real spatial distances between image pixel points were rarely considered. Therefore, we propose a simple design scheme for ranging between pixel points based on the principle of depth measurement using a depth camera. In the design of the measurement calculation method, the obtained image information and the actual required information results are not in the same calculation coordinate system. Consequently, transformations between multiple planar coordinate systems are used in the design. For example, a depth map can be obtained using a binocular camera and then converted into a 3d point cloud map. This study aimed to develop a highly self-regulated recognition control system for intermediate care dressing support in a washroom scene. In the next section, we describe the proposed solution.</p>
        </sec>
        <sec id="sec2" sec-type="methods">
            <title>2. Method</title>
            <sec id="sec3">
                <title>2.1 Specific auxiliary boundary recognition algorithm</title>
                <p>In our previous study we used three models Fcns8, SegNet, and DeconvNet for semantic segmentation of clothes boundary recognition.
                    <sup>
                        <xref ref-type="bibr" rid="ref1">1</xref>
                    </sup> In this study, we used the PspNet model for semantic segmentation of clothes. In a prior study, there were four categories: jacket, pants, hands, and background. We added a 5th category of shoes. 
                    <xref ref-type="fig" rid="f4">
Figure 4</xref> shows a flow chart of the image processing in the third part of 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref>. 
                    <xref ref-type="fig" rid="f5">
Figure 5</xref> shows the recognition categories in the semantic segmentation part of this study. This approach is a multi-stage training and processing method. The clothing boundary identification and control system must be based on a real-time situation for identification and control. In terms of model selection, PspNet has a good correct rate of semantic segmentation among many models. However, PspNet does not exhibit a high real-time recognition rate in real time semantic segmentation models. However, in this task, more focus was placed on the recognition rate of semantic segmentation such as clothes. Therefore, PspNet was selected as the model for this task. 
                    <xref ref-type="fig" rid="f6">
Figure 6</xref>. shows a comparison of the speed and recognition rate of the models for real-time semantic segmentation in our used model.
                    <sup>
                        <xref ref-type="bibr" rid="ref14">14</xref>
                    </sup>
                </p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>
Figure 3. </label>
                    <caption>
                        <title>Clothing boundary recognition control system flow chart.</title>
                    </caption>
                    <graphic id="gr3" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure3.gif"/>
                </fig>
                <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                    <label>
Figure 4. </label>
                    <caption>
                        <title>The third part of the processing flow of image boundary recognition.</title>
                    </caption>
                    <graphic id="gr4" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure4.gif"/>
                </fig>
                <fig fig-type="figure" id="f5" orientation="portrait" position="float">
                    <label>
Figure 5. </label>
                    <caption>
                        <title>Semantic segmentation category.</title>
                    </caption>
                    <graphic id="gr5" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure5.gif"/>
                </fig>
                <fig fig-type="figure" id="f6" orientation="portrait" position="float">
                    <label>
Figure 6. </label>
                    <caption>
                        <title>Comparison of correct and real-time recognition rates of semantic segmentation models.</title>
                    </caption>
                    <graphic id="gr6" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure6.gif"/>
                </fig>
                <p>
                    <xref ref-type="fig" rid="f3">
Figure 3</xref> show a flowchart of the stereo camera-based clothing recognition control system. The gray area on the right side of 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref> shows the detailed processing flow of clothing and boundary recognition for the boundary recognition model. The boundary recognition model in the gray part of 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref> is a clothing boundary recognition method that uses semantic segmentation for deep learning and machine learning SVM.
                    <sup>
                        <xref ref-type="bibr" rid="ref1">1</xref>
                    </sup> We used a 2-stage processing for clothes boundary recognition. First, the semantic segmentation of clothes is recognized using a deep model. Subsequently, using the semantic segmentation results, binary classification of the jacket and pant semantic segmentation results was performed. The clothing boundary recognition model in 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref> is divided into three parts (the gray part on the right side of 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref>).</p>
                <p>The first part is the input layer, which is used as the input for the non-trained dataset and data labeling. The training set did not have any special preprocessing and was in the same form as the semantic segmentation data.</p>
                <p>The second part was the semantic segmentation model network, in which this case we used the PspNet model.
                    <sup>
                        <xref ref-type="bibr" rid="ref6">6</xref>
                    </sup> The model is used to extract image features and categorize each pixel in the final output layer. Finally, we used the softmax output function as the output layer. The final result is the classification probability of each pixel in the W*H.</p>
                <p>The third part extracts the feature information of jackets and pants based on the results of semantic segmentation. Then, the traditional Canny edge detection algorithm was used to obtain the edge line features of the jackets and pants. The edge line features extraction process can reduce the dimensionality of the data. On the other hand, edge contour boundary extraction can also reduce data noise and reduce training data. In the prediction of semantic segmentation, the prediction position error was latent. This increases the cost of training time and affects the accuracy of SVM algorithm classification training. Therefore, using the Canny algorithm to extract edge boundaries is beneficial for training accuracy and improving training speed. Furthermore, using the Canny algorithm did not change the features of the original data. Because the image results of semantic segmentation is multidimensional data W*H*3, semantic segmentation results through the Canny filter, and feature extraction can be performed to obtain one-dimensional data W*H of contour features and reduce the amount of data. Without contour feature extraction, the semantic segmentation results are directly used as one-dimensional binary classification data for the SVM computation. Owing to the large amount of data, this results in low computational efficiency. To improve the computational speed, we considered the processing of the Canny filter on the image result of semantic segmentation as a process of data dimensionality reduction.</p>
                <p>Finally, the SVM algorithm was used for boundary identification between jackets and pants. However, the edge boundary data for jackets and pants can be transformed into two different clustered datasets, as shown in 
                    <xref ref-type="fig" rid="f4">
Figure 4</xref>. Because they have unique data attributes, there is not much intersection; however, the data are close. Therefore, the SVM binary classification algorithm is applicable. The SVM algorithm is categorized into linear and nonlinear classification. We choose linear classification method. SVM algorithm is a common classification algorithm that generates linear classification planes from binary or one-to-many results.
                    <disp-formula id="e1">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>0</mml:mn>
                            </mml:msub>
                            <mml:msub>
                                <mml:mi>y</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>+</mml:mo>
                            <mml:msub>
                                <mml:mi>w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>+</mml:mo>
                            <mml:mi>b</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mn>0</mml:mn>
                        </mml:math>

                        <label>(1)</label>
</disp-formula>

                    <disp-formula id="e2">

                        <mml:math display="block">
                            <mml:msub>
                                <mml:mi>y</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mrow>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:msub>
                                        <mml:mi>w</mml:mi>
                                        <mml:mn>1</mml:mn>
                                    </mml:msub>
                                    <mml:msub>
                                        <mml:mi>x</mml:mi>
                                        <mml:mn>1</mml:mn>
                                    </mml:msub>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:mi>b</mml:mi>
                                </mml:mrow>
                                <mml:msub>
                                    <mml:mi>w</mml:mi>
                                    <mml:mn>0</mml:mn>
                                </mml:msub>
                            </mml:mfrac>
                        </mml:math>

                        <label>(2)</label>
</disp-formula>Based on the SVM algorithm and data characteristics. Training of the SVM algorithm was used to obtain the boundary information of the auxiliary position. 
                    <xref ref-type="disp-formula" rid="e1">
Equation 1</xref> is the trained SVM hyperplane formula: 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="normal">w</mml:mi>
                                <mml:mn>0</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula> is the weight value of the y-coordinate, 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="normal">w</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula> is the weight value of the x-coordinate, and b is the bias value of the SVM hyperplane.</p>
                <p>
                    <xref ref-type="disp-formula" rid="e2">
Equation 2</xref> is a deformed derivation of 
                    <xref ref-type="disp-formula" rid="e1">
Equation 1</xref> for obtaining the value of the SVM hyperplane 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="normal">y</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula>. The value of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="normal">x</mml:mi>
                                <mml:mn>1</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula> is determined based on the predicted image W pixel width.</p>
                <p>The coordinates of the hyperplane boundary can be obtained using 
                    <xref ref-type="disp-formula" rid="e1 e2">
Equations 1 and 2</xref> as follows: The SVM hyperplane boundary can be reconstructed to identify the specific clothing boundary. 
                    <xref ref-type="fig" rid="f4">
Figure 4</xref> shows the semantic segmentation results obtained using semantic segmentation and the contours of the semantic segmentation results obtained using the Canny algorithm. For example, the green jacket contour and red pant contour in 
                    <xref ref-type="fig" rid="f4">
Figure 4</xref> were used as the clustering data for the two categories. From the data transformations in 
                    <xref ref-type="fig" rid="f4">
Figure 4</xref>, we can see that there is a clear boundary between the green contour data and the red data, and that it has the characteristic of linear categorization under all conditions. Hence utilizing SVM for classification produces a linear classification hyperplane between the green and red data.</p>
            </sec>
            <sec id="sec4">
                <title>2.2 Stereo camera algorithm</title>
                <p>
                    <xref ref-type="fig" rid="f7">
Figure 7.1</xref> shows the principle of single-pixel point depth computation using stereo cameras L:left camera and R:right camera. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                            <mml:mo>&#x2212;</mml:mo>
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> is the disparity. f: focal length and T: center distance between the two cameras also called the base line. T and f are fixed values and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                            <mml:mo>&#x2212;</mml:mo>
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> disparity values are unknown variables. To obtain the disparity value, we must use 
                    <xref ref-type="disp-formula" rid="e6">
Equation 3</xref> to calculate the distance value Z between the object and camera.
                    <sup>
                        <xref ref-type="bibr" rid="ref2">2</xref>
                    </sup> Finally, a depth map was obtained. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                            <mml:mo>&#x2212;</mml:mo>
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> in 
                    <xref ref-type="disp-formula" rid="e6">
Equation 3</xref> is the disparity value. Calculating the disparity value between two images is obtained by calculating using stereo matching algorithm. The left camera image and the right camera image are used as inputs to obtain the disparity values by stereo matching algorithm. For example, SAD (Sum of absolute differences) image matching algorithm, SGBM global matching algorithm and other methods. disparity value 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mtext>disparity</mml:mtext>
                            <mml:mo>=</mml:mo>
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                            <mml:mo>&#x2212;</mml:mo>
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>. In order to find the distance between two specific pixels. Thus, it is necessary to obtain the specific values of xl and xr for the selected pixel points. The method of calculating xl and xr for selected pixel points is based on obtaining a depth map. In the later part we further describe how to compute to obtain xl and xr.</p>
                <fig fig-type="figure" id="f7" orientation="portrait" position="float">
                    <label>
Figure 7.1. </label>
                    <caption>
                        <title>Disparity calculation (upper left). 
                            <xref ref-type="fig" rid="f7">
Figure 7.2</xref> Measurement calculation of pixel coordinates in positive and negative fields (upper right). 
                            <xref ref-type="fig" rid="f7">
Figure 7.3</xref> Measurement calculation of pixel coordinates in positive fields (lower).</title>
                        <p/>
                    </caption>
                    <graphic id="gr7" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure7.gif"/>
                </fig>
                <p>
                    <xref ref-type="fig" rid="f7">
Figure 7.2</xref> shows the principle diagram for calculating the actual distance between two measurement points using stereo camera zed2. 
                    <xref ref-type="fig" rid="T1">Table 1</xref> shows the calculation of the actual length of a single pixel in the real space. Our proposed method for measuring the distance between two points is an extension method based on stereo camera depth 3measurement. 
                    <xref ref-type="fig" rid="f7">
Figure 7.2</xref> shows our proposed method to calculate the distance between two points based on the original single-point depth calculation.
                    <disp-formula id="e6">

                        <mml:math display="block">
                            <mml:mi>Z</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mrow>
                                    <mml:mi>f</mml:mi>
                                    <mml:mo>&#x00d7;</mml:mo>
                                    <mml:mi>T</mml:mi>
                                </mml:mrow>
                                <mml:mrow>
                                    <mml:msub>
                                        <mml:mi>x</mml:mi>
                                        <mml:mi>l</mml:mi>
                                    </mml:msub>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:msub>
                                        <mml:mi>x</mml:mi>
                                        <mml:mi>r</mml:mi>
                                    </mml:msub>
                                </mml:mrow>
                            </mml:mfrac>
                        </mml:math>

                        <label>(3)</label>
</disp-formula>
                </p>
                <table-wrap id="T1" orientation="portrait" position="float">
                    <label>
Table 1. </label>
                    <caption>
                        <title>Pseudocode for calculating the actual size of a single pixel.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Using a stereo camera to measure the actual size of a single pixel algorithm</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>Input:</bold> Measurement points depth: 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> of depth
                                    <break/>

                                    <bold>Output:</bold> 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi mathvariant="italic">ix</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula>: 
                                    <bold>The actual size of a single pixel in the measured depth</bold>
</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>1.Start:</bold> Obtain 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> of depth and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> depth of Point cloud map converted to pixel coordinates;</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>2.</bold> Calculate 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> of pixel coordinate value:
                                    <break/>

                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi>x</mml:mi>
                                                <mml:mrow>
                                                    <mml:mi>l</mml:mi>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mtext>or</mml:mtext>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mi mathvariant="normal">r</mml:mi>
                                                </mml:mrow>
                                            </mml:msup>
                                            <mml:mo>=</mml:mo>
                                            <mml:mrow>
                                                <mml:mo stretchy="true">(</mml:mo>
                                                <mml:msub>
                                                    <mml:mi>p</mml:mi>
                                                    <mml:mtext mathvariant="italic">pixel</mml:mtext>
                                                </mml:msub>
                                                <mml:mo>&#x2212;</mml:mo>
                                                <mml:msub>
                                                    <mml:mi>c</mml:mi>
                                                    <mml:mi>x</mml:mi>
                                                </mml:msub>
                                                <mml:mo stretchy="true">)</mml:mo>
                                            </mml:mrow>
                                            <mml:mi mathvariant="italic">dx</mml:mi>
                                        </mml:math>
</inline-formula>
</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>3.</bold> calculate 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi mathvariant="italic">ob</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msup>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi mathvariant="italic">ob</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msup>
                                        </mml:math>
</inline-formula>:
                                    <break/>

                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi mathvariant="italic">ob</mml:mi>
                                                <mml:mrow>
                                                    <mml:mi>l</mml:mi>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mi>r</mml:mi>
                                                </mml:mrow>
                                            </mml:msup>
                                            <mml:mo>=</mml:mo>
                                            <mml:msqrt>
                                                <mml:mrow>
                                                    <mml:msup>
                                                        <mml:mrow>
                                                            <mml:mo stretchy="true">(</mml:mo>
                                                            <mml:msup>
                                                                <mml:mi>x</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:mi>l</mml:mi>
                                                                    <mml:mspace width="0.25em"/>
                                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                                    <mml:mspace width="0.25em"/>
                                                                    <mml:mi>r</mml:mi>
                                                                </mml:mrow>
                                                            </mml:msup>
                                                            <mml:mo stretchy="true">)</mml:mo>
                                                        </mml:mrow>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msup>
                                                    <mml:mo>+</mml:mo>
                                                    <mml:msup>
                                                        <mml:mrow>
                                                            <mml:mo stretchy="true">(</mml:mo>
                                                            <mml:mi>f</mml:mi>
                                                            <mml:mo stretchy="true">)</mml:mo>
                                                        </mml:mrow>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msup>
                                                </mml:mrow>
                                            </mml:msqrt>
                                        </mml:math>
</inline-formula>
</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>4.</bold> calculate 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi>ob</mml:mi>
                                                <mml:msup>
                                                    <mml:mi mathvariant="normal">l</mml:mi>
                                                    <mml:mrow>
                                                        <mml:mo>&#x2032;</mml:mo>
                                                        <mml:mo>&#x2032;</mml:mo>
                                                    </mml:mrow>
                                                </mml:msup>
                                            </mml:msup>
                                        </mml:math>
</inline-formula>and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi>ob</mml:mi>
                                                <mml:mi mathvariant="normal">r</mml:mi>
                                            </mml:msup>
                                        </mml:math>
</inline-formula>:
                                    <break/>

                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi mathvariant="italic">ob</mml:mi>
                                                <mml:mrow>
                                                    <mml:msup>
                                                        <mml:mi>l</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mo>&#x2032;</mml:mo>
                                                            <mml:mo>&#x2032;</mml:mo>
                                                        </mml:mrow>
                                                    </mml:msup>
                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:msup>
                                                        <mml:mi>r</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mo>&#x2032;</mml:mo>
                                                            <mml:mo>&#x2032;</mml:mo>
                                                        </mml:mrow>
                                                    </mml:msup>
                                                </mml:mrow>
                                            </mml:msup>
                                            <mml:mo>=</mml:mo>
                                            <mml:mfrac>
                                                <mml:mrow>
                                                    <mml:mi>Z</mml:mi>
                                                    <mml:mo>&#x2217;</mml:mo>
                                                    <mml:msup>
                                                        <mml:mi mathvariant="italic">ob</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mi>l</mml:mi>
                                                            <mml:mspace width="0.25em"/>
                                                            <mml:mtext mathvariant="italic">or</mml:mtext>
                                                            <mml:mspace width="0.25em"/>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:mrow>
                                                    </mml:msup>
                                                </mml:mrow>
                                                <mml:mi>f</mml:mi>
                                            </mml:mfrac>
                                        </mml:math>
</inline-formula>
</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>5.</bold> calculate 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi>T</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msup>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi>T</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msup>
                                        </mml:math>
</inline-formula>:
                                    <break/>

                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msup>
                                                <mml:mi>T</mml:mi>
                                                <mml:mrow>
                                                    <mml:mi>l</mml:mi>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mi>r</mml:mi>
                                                </mml:mrow>
                                            </mml:msup>
                                            <mml:mo>=</mml:mo>
                                            <mml:msqrt>
                                                <mml:mrow>
                                                    <mml:msup>
                                                        <mml:mrow>
                                                            <mml:mo stretchy="true">(</mml:mo>
                                                            <mml:msup>
                                                                <mml:mi mathvariant="italic">ob</mml:mi>
                                                                <mml:mrow>
                                                                    <mml:msup>
                                                                        <mml:mi>l</mml:mi>
                                                                        <mml:mrow>
                                                                            <mml:mo>&#x2032;</mml:mo>
                                                                            <mml:mo>&#x2032;</mml:mo>
                                                                        </mml:mrow>
                                                                    </mml:msup>
                                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                                    <mml:mspace width="0.25em"/>
                                                                    <mml:msup>
                                                                        <mml:mi>r</mml:mi>
                                                                        <mml:mrow>
                                                                            <mml:mo>&#x2032;</mml:mo>
                                                                            <mml:mo>&#x2032;</mml:mo>
                                                                        </mml:mrow>
                                                                    </mml:msup>
                                                                </mml:mrow>
                                                            </mml:msup>
                                                            <mml:mo stretchy="true">)</mml:mo>
                                                        </mml:mrow>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msup>
                                                    <mml:mo>&#x2212;</mml:mo>
                                                    <mml:msup>
                                                        <mml:mi>Z</mml:mi>
                                                        <mml:mn>2</mml:mn>
                                                    </mml:msup>
                                                </mml:mrow>
                                            </mml:msqrt>
                                        </mml:math>
</inline-formula>
</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>6.</bold>
 calculate the actual distance between points 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>l</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula> and 
                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:msub>
                                                <mml:mi>P</mml:mi>
                                                <mml:mi>r</mml:mi>
                                            </mml:msub>
                                        </mml:math>
</inline-formula>: 
                                    <break/>

                                    <disp-formula id="e76">

                                        <mml:math display="block">
                                            <mml:mo stretchy="true">{</mml:mo>
                                            <mml:mtable>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:maligngroup/>
                                                        <mml:msup>
                                                            <mml:mi>T</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msup>
                                                        <mml:mo>+</mml:mo>
                                                        <mml:msup>
                                                            <mml:mi>T</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msup>
                                                        <mml:mo>,</mml:mo>
                                                        <mml:malignmark/>
                                                        <mml:msub>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msub>
                                                        <mml:mo>&lt;</mml:mo>
                                                        <mml:mn>0</mml:mn>
                                                        <mml:mspace width="0.25em"/>
                                                        <mml:mtext mathvariant="italic">and</mml:mtext>
                                                        <mml:mspace width="0.25em"/>
                                                        <mml:msub>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msub>
                                                        <mml:mo>&gt;</mml:mo>
                                                        <mml:mn>0</mml:mn>
                                                        <mml:mo>#</mml:mo>
                                                        <mml:mo>#</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:maligngroup/>
                                                        <mml:msup>
                                                            <mml:mi>T</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msup>
                                                        <mml:mo>&#x2212;</mml:mo>
                                                        <mml:msup>
                                                            <mml:mi>T</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msup>
                                                        <mml:mo>,</mml:mo>
                                                        <mml:malignmark/>
                                                        <mml:msub>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msub>
                                                        <mml:mo>&gt;</mml:mo>
                                                        <mml:mn>0</mml:mn>
                                                        <mml:mspace width="0.25em"/>
                                                        <mml:mtext mathvariant="italic">and</mml:mtext>
                                                        <mml:mspace width="0.25em"/>
                                                        <mml:msub>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msub>
                                                        <mml:mo>&gt;</mml:mo>
                                                        <mml:mn>0</mml:mn>
                                                        <mml:mo>#</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                                <mml:mtr>
                                                    <mml:mtd>
                                                        <mml:maligngroup/>
                                                        <mml:msup>
                                                            <mml:mi>T</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msup>
                                                        <mml:mo>&#x2212;</mml:mo>
                                                        <mml:msup>
                                                            <mml:mi>T</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msup>
                                                        <mml:mo>,</mml:mo>
                                                        <mml:malignmark/>
                                                        <mml:msub>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msub>
                                                        <mml:mo>&lt;</mml:mo>
                                                        <mml:mn>0</mml:mn>
                                                        <mml:mspace width="0.25em"/>
                                                        <mml:mtext mathvariant="italic">and</mml:mtext>
                                                        <mml:mspace width="0.25em"/>
                                                        <mml:msub>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msub>
                                                        <mml:mo>&lt;</mml:mo>
                                                        <mml:mn>0</mml:mn>
                                                        <mml:mo>#</mml:mo>
                                                    </mml:mtd>
                                                </mml:mtr>
                                            </mml:mtable>
                                        </mml:math>
</disp-formula>
</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>7. End:</bold> calculate single pixel size:
                                    <break/>

                                    <inline-formula>

                                        <mml:math display="inline">
                                            <mml:mi mathvariant="italic">pix</mml:mi>
                                            <mml:mo>=</mml:mo>
                                            <mml:mfrac>
                                                <mml:mi>L</mml:mi>
                                                <mml:mrow>
                                                    <mml:msub>
                                                        <mml:mi>D</mml:mi>
                                                        <mml:msup>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>r</mml:mi>
                                                        </mml:msup>
                                                    </mml:msub>
                                                    <mml:mo>&#x2212;</mml:mo>
                                                    <mml:msub>
                                                        <mml:mi>D</mml:mi>
                                                        <mml:msup>
                                                            <mml:mi>x</mml:mi>
                                                            <mml:mi>l</mml:mi>
                                                        </mml:msup>
                                                    </mml:msub>
                                                </mml:mrow>
                                            </mml:mfrac>
                                        </mml:math>
</inline-formula>
</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
                <p>In 
                    <xref ref-type="fig" rid="f7">
Figure 7.3</xref> and 
                    <xref ref-type="fig" rid="f8">
Figure 8</xref>, the parameters of the camera are f: focal length. R: rotation matrix. T: translation matrix. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>d</mml:mi>
                                <mml:mi>x</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>: Physical x-axis size of a single pixel of the light sensor in the camera. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>d</mml:mi>
                                <mml:mi>y</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>: Physical y-axis size of a single pixel of the light sensor in the camera. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>u</mml:mi>
                                <mml:mn>0</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula>: number of X-axis pixels that are the difference between the center pixel coordinate and the origin pixel coordinate of the image. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>v</mml:mi>
                                <mml:mn>0</mml:mn>
                            </mml:msub>
                        </mml:math>
</inline-formula>: the number of Y-axis pixels that represent the difference between the center pixel coordinate and origin pixel coordinate of the image. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>c</mml:mi>
                                <mml:mi>x</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>: intrinsic parameter value of the origin point. The intrinsic parameters of the camera were obtained using the camera calibration method.
                    <disp-formula id="e15">

                        <mml:math display="block">
                            <mml:msup>
                                <mml:mi>x</mml:mi>
                                <mml:mrow>
                                    <mml:mi>l</mml:mi>
                                    <mml:mspace width="0.25em"/>
                                    <mml:mtext>or</mml:mtext>
                                    <mml:mspace width="0.25em"/>
                                    <mml:mi mathvariant="normal">r</mml:mi>
                                </mml:mrow>
                            </mml:msup>
                            <mml:mo>=</mml:mo>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:msub>
                                    <mml:mi>p</mml:mi>
                                    <mml:mtext mathvariant="italic">pixel</mml:mtext>
                                </mml:msub>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:msub>
                                    <mml:mi>c</mml:mi>
                                    <mml:mi>x</mml:mi>
                                </mml:msub>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                            <mml:mi mathvariant="italic">dx</mml:mi>
                        </mml:math>

                        <label>(4)</label>
</disp-formula>

                    <disp-formula id="e16">

                        <mml:math display="block">
                            <mml:msup>
                                <mml:mi mathvariant="italic">ob</mml:mi>
                                <mml:mrow>
                                    <mml:mi>l</mml:mi>
                                    <mml:mspace width="0.25em"/>
                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                    <mml:mspace width="0.25em"/>
                                    <mml:mi>r</mml:mi>
                                </mml:mrow>
                            </mml:msup>
                            <mml:mo>=</mml:mo>
                            <mml:msqrt>
                                <mml:mrow>
                                    <mml:msup>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:msup>
                                                <mml:mi>x</mml:mi>
                                                <mml:mrow>
                                                    <mml:mi>l</mml:mi>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:mi>r</mml:mi>
                                                </mml:mrow>
                                            </mml:msup>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                        <mml:mn>2</mml:mn>
                                    </mml:msup>
                                    <mml:mo>+</mml:mo>
                                    <mml:msup>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:mi>f</mml:mi>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                        <mml:mn>2</mml:mn>
                                    </mml:msup>
                                </mml:mrow>
                            </mml:msqrt>
                        </mml:math>

                        <label>(5)</label>
</disp-formula>

                    <disp-formula id="e17">

                        <mml:math display="block">
                            <mml:msup>
                                <mml:mi mathvariant="italic">ob</mml:mi>
                                <mml:mrow>
                                    <mml:msup>
                                        <mml:mi>l</mml:mi>
                                        <mml:mrow>
                                            <mml:mo>&#x2032;</mml:mo>
                                            <mml:mo>&#x2032;</mml:mo>
                                        </mml:mrow>
                                    </mml:msup>
                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                    <mml:mspace width="0.25em"/>
                                    <mml:msup>
                                        <mml:mi>r</mml:mi>
                                        <mml:mrow>
                                            <mml:mo>&#x2032;</mml:mo>
                                            <mml:mo>&#x2032;</mml:mo>
                                        </mml:mrow>
                                    </mml:msup>
                                </mml:mrow>
                            </mml:msup>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mrow>
                                    <mml:mi>Z</mml:mi>
                                    <mml:mo>&#x2217;</mml:mo>
                                    <mml:msup>
                                        <mml:mi mathvariant="italic">ob</mml:mi>
                                        <mml:mrow>
                                            <mml:mi>l</mml:mi>
                                            <mml:mspace width="0.25em"/>
                                            <mml:mtext mathvariant="italic">or</mml:mtext>
                                            <mml:mspace width="0.25em"/>
                                            <mml:mi>r</mml:mi>
                                        </mml:mrow>
                                    </mml:msup>
                                </mml:mrow>
                                <mml:mi>f</mml:mi>
                            </mml:mfrac>
                        </mml:math>

                        <label>(6)</label>
</disp-formula>

                    <disp-formula id="e18">

                        <mml:math display="block">
                            <mml:msup>
                                <mml:mi>T</mml:mi>
                                <mml:mrow>
                                    <mml:mi>l</mml:mi>
                                    <mml:mspace width="0.25em"/>
                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                    <mml:mspace width="0.25em"/>
                                    <mml:mi>r</mml:mi>
                                </mml:mrow>
                            </mml:msup>
                            <mml:mo>=</mml:mo>
                            <mml:msqrt>
                                <mml:mrow>
                                    <mml:msup>
                                        <mml:mrow>
                                            <mml:mo stretchy="true">(</mml:mo>
                                            <mml:msup>
                                                <mml:mi mathvariant="italic">ob</mml:mi>
                                                <mml:mrow>
                                                    <mml:msup>
                                                        <mml:mi>l</mml:mi>
                                                        <mml:mo>"</mml:mo>
                                                    </mml:msup>
                                                    <mml:mtext mathvariant="italic">or</mml:mtext>
                                                    <mml:mspace width="0.25em"/>
                                                    <mml:msup>
                                                        <mml:mi>r</mml:mi>
                                                        <mml:mrow>
                                                            <mml:mo>&#x2032;</mml:mo>
                                                            <mml:mo>&#x2032;</mml:mo>
                                                        </mml:mrow>
                                                    </mml:msup>
                                                </mml:mrow>
                                            </mml:msup>
                                            <mml:mo stretchy="true">)</mml:mo>
                                        </mml:mrow>
                                        <mml:mn>2</mml:mn>
                                    </mml:msup>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:msup>
                                        <mml:mi>Z</mml:mi>
                                        <mml:mn>2</mml:mn>
                                    </mml:msup>
                                </mml:mrow>
                            </mml:msqrt>
                        </mml:math>

                        <label>(7)</label>
</disp-formula>

                    <disp-formula id="e19">

                        <mml:math display="block">
                            <mml:mi mathvariant="normal">L</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mrow>
                                <mml:mo stretchy="true">{</mml:mo>
                                <mml:msup>
                                    <mml:mi>T</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msup>
                                <mml:mo>+</mml:mo>
                                <mml:msup>
                                    <mml:mi>T</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msup>
                                <mml:mo>,</mml:mo>
                                <mml:msub>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msub>
                                <mml:mo>&lt;</mml:mo>
                                <mml:mn>0</mml:mn>
                                <mml:mspace width="0.25em"/>
                                <mml:mtext mathvariant="italic">and</mml:mtext>
                                <mml:mspace width="0.25em"/>
                                <mml:msub>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msub>
                                <mml:mo>&gt;</mml:mo>
                                <mml:mn>0</mml:mn>
                            </mml:mrow>
                        </mml:math>

                        <label>(8.1)</label>
</disp-formula>

                    <disp-formula id="e20">

                        <mml:math display="block">
                            <mml:mi mathvariant="normal">L</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mrow>
                                <mml:mo stretchy="true">{</mml:mo>
                                <mml:msup>
                                    <mml:mi>T</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msup>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:msup>
                                    <mml:mi>T</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msup>
                                <mml:mo>,</mml:mo>
                                <mml:msub>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msub>
                                <mml:mo>&gt;</mml:mo>
                                <mml:mn>0</mml:mn>
                                <mml:mspace width="0.25em"/>
                                <mml:mtext mathvariant="italic">and</mml:mtext>
                                <mml:mspace width="0.25em"/>
                                <mml:msub>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msub>
                                <mml:mo>&gt;</mml:mo>
                                <mml:mn>0</mml:mn>
                            </mml:mrow>
                        </mml:math>

                        <label>(8.2)</label>
</disp-formula>

                    <disp-formula id="e21">

                        <mml:math display="block">
                            <mml:mi mathvariant="normal">L</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mrow>
                                <mml:mo stretchy="true">{</mml:mo>
                                <mml:msup>
                                    <mml:mi>T</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msup>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:msup>
                                    <mml:mi>T</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msup>
                                <mml:mo>,</mml:mo>
                                <mml:msub>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msub>
                                <mml:mo>&lt;</mml:mo>
                                <mml:mn>0</mml:mn>
                                <mml:mspace width="0.25em"/>
                                <mml:mtext mathvariant="italic">and</mml:mtext>
                                <mml:mspace width="0.25em"/>
                                <mml:msub>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msub>
                                <mml:mo>&lt;</mml:mo>
                                <mml:mn>0</mml:mn>
                            </mml:mrow>
                        </mml:math>

                        <label>(8.3)</label>
</disp-formula>

                    <disp-formula id="e22">

                        <mml:math display="block">
                            <mml:mi mathvariant="italic">pix</mml:mi>
                            <mml:mo>=</mml:mo>
                            <mml:mfrac>
                                <mml:mi>L</mml:mi>
                                <mml:mrow>
                                    <mml:msub>
                                        <mml:mi>D</mml:mi>
                                        <mml:msup>
                                            <mml:mi>x</mml:mi>
                                            <mml:mi>r</mml:mi>
                                        </mml:msup>
                                    </mml:msub>
                                    <mml:mo>&#x2212;</mml:mo>
                                    <mml:msub>
                                        <mml:mi>D</mml:mi>
                                        <mml:msup>
                                            <mml:mi>x</mml:mi>
                                            <mml:mi>l</mml:mi>
                                        </mml:msup>
                                    </mml:msub>
                                </mml:mrow>
                            </mml:mfrac>
                        </mml:math>

                        <label>(9)</label>
</disp-formula>
                </p>
                <fig fig-type="figure" id="f8" orientation="portrait" position="float">
                    <label>
Figure 8. </label>
                    <caption>
                        <title>Depth coordinate system to pixel.</title>
                    </caption>
                    <graphic id="gr8" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure8.gif"/>
                </fig>
                <p>For example, we measure to calculated the distance between 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> in 
                    <xref ref-type="fig" rid="f7">
Figure 7.2</xref>. First, we used the Depth Perception API of the stereo camera zed2 SDK to calculate the depth map to obtain the depth distances 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>Z</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>Z</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> for two points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>. Then, the stereo camera zed2 SDK API was used to calculate the depth map for conversion to a 3d point cloud. Sets the 3d point cloud coordinates to the actual world coordinates. Using the formula shown in 
                    <xref ref-type="fig" rid="f8">
Figure 8</xref> the 3d point cloud coordinates were finally converted to pixel coordinates. When calculating the distance between two points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>, we did not use the left and right camera parameters to calculate the measurements. We use the left (point L) camera in 
                    <xref ref-type="fig" rid="f7">
Figure 7.2</xref> for the mapping and calculation of the pixel coordinates of the two points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>. First, we obtained the depths 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>Z</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>Z</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>. Using the 3d point cloud coordinate system was used for conversion to a pixel coordinate system. Later, the pixel coordinate system is utilized with u: x-axis pixel coordinate values and v: y-axis pixel coordinate values. The 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mtext mathvariant="italic">pixel</mml:mtext>
                            </mml:msub>
                        </mml:math>
</inline-formula> of 
                    <xref ref-type="disp-formula" rid="e15">
Equation 4</xref> is the measurement point x-coordinate converted to a pixel coordinate value (
                    <xref ref-type="fig" rid="f8">
Figure 8</xref> Pixel coordinate u value). It is possible to obtain the values of dark red 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and green 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> for points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>p</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> by using 
                    <xref ref-type="disp-formula" rid="e15">
Equation 4</xref>. 
                    <xref ref-type="disp-formula" rid="e16">
Equation 5</xref> was used to obtain 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="italic">ob</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi mathvariant="italic">ob</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>. 
                    <xref ref-type="disp-formula" rid="e17">
Equation 6</xref> was used to obtain 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi mathvariant="italic">ob</mml:mi>
                                <mml:mrow>
                                    <mml:mi>l</mml:mi>
                                    <mml:mo>&#x2032;</mml:mo>
                                    <mml:mo>&#x2032;</mml:mo>
                                </mml:mrow>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi mathvariant="italic">ob</mml:mi>
                                <mml:mrow>
                                    <mml:mi>r</mml:mi>
                                    <mml:mo>&#x2032;</mml:mo>
                                    <mml:mo>&#x2032;</mml:mo>
                                </mml:mrow>
                            </mml:msup>
                        </mml:math>
</inline-formula> values. 
                    <xref ref-type="disp-formula" rid="e18">
Equation 7</xref> is then used to obtain the value of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>T</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> at point 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and the value of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>T</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> at point 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>.</p>
                <p>In 
                    <xref ref-type="fig" rid="f7">
Figure 7.2</xref> plane1 is the object reality plane, plane2 is the image pixel plane, and plane3 is the camera lens plane. 
                    <xref ref-type="fig" rid="f7">
Figure 7.2</xref> shows the pixel coordinate x-values of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> in the negative and positive fields. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>: 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> x-coordinate values in the pixel coordinate system and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula>:
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:mspace width="0.25em"/>
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> x-coordinate values in the pixel coordinate system. In the ideal model, the 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> point is to the left of the left camera center line and the 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> point is to the right of the right camera center line. Using Eqs. 
                    <xref ref-type="disp-formula" rid="e15">
Equations 4</xref>, 
                    <xref ref-type="disp-formula" rid="e16">5</xref>, 
                    <xref ref-type="disp-formula" rid="e17">6</xref>, and 
                    <xref ref-type="disp-formula" rid="e18">7</xref> it is possible to obtain 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>T</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>T</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> using Eqs. 
                    <xref ref-type="disp-formula" rid="e19">
Equations 8.1</xref>, 
                    <xref ref-type="disp-formula" rid="e20">8.2</xref>, and 
                    <xref ref-type="disp-formula" rid="e21">8.3</xref>. If two points are distributed in the positive and negative value domains use 
                    <xref ref-type="disp-formula" rid="e19">
Equation 8.1</xref> to calculate the distance L between the points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>. 
                    <xref ref-type="fig" rid="f7">
Figure 7.3</xref> shows the pixel coordinate x values of both 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> in the positive domain. If both points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>x</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msub>
                        </mml:math>
</inline-formula> are distributed in the positive domain use 
                    <xref ref-type="disp-formula" rid="e20">
Equation 8.2</xref> to calculate the distance L between points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>. If the two points of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> are completely in the negative domain and the value domain of 
                    <xref ref-type="fig" rid="f7">
Figure 7.3</xref> is taken to be opposite, the distance L between the two points of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> is calculated using 
                    <xref ref-type="disp-formula" rid="e21">
Equation 8.3</xref> when, the two points are distributed in the negative domain.</p>
                <p>
                    <xref ref-type="disp-formula" rid="e22">
Equation 9</xref> calculates the actual length of a single pixel between two points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>. 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>D</mml:mi>
                                <mml:msup>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>l</mml:mi>
                                </mml:msup>
                            </mml:msub>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msub>
                                <mml:mi>D</mml:mi>
                                <mml:msup>
                                    <mml:mi>x</mml:mi>
                                    <mml:mi>r</mml:mi>
                                </mml:msup>
                            </mml:msub>
                        </mml:math>
</inline-formula> are the x-coordinate values of 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> in the depth map. When we choose the coordinates of the two points 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula> and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>, we choose the same y-coordinate value. Therefore, only the x-coordinate variable was used in 
                    <xref ref-type="disp-formula" rid="e22">
Equation 9</xref> to calculate the actual distance of a single pixel.</p>
                <p>
                    <xref ref-type="fig" rid="f9">
Figure 9(upper)</xref> on the left show the actual semantic segmentation recognized image. 
                    <xref ref-type="fig" rid="f9">
Figure 9(upper)</xref> on the right shows a the clothing boundary recognition image. 
                    <xref ref-type="fig" rid="f9">
Figure 9(lower left)</xref> shows the predicted shoe semantic segmentation result, after which the selected measurement points were red 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>l</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>:l and 
                    <inline-formula>

                        <mml:math display="inline">
                            <mml:msup>
                                <mml:mi>P</mml:mi>
                                <mml:mi>r</mml:mi>
                            </mml:msup>
                        </mml:math>
</inline-formula>:r. Two calculation points are selected in the shoe category, after which the size of a single pixel in the actual space was calculated. As shown in 
                    <xref ref-type="fig" rid="f9">
Figure 9(lower right)</xref>, the actual spatial distance was obtained using the sum of the pixel points calculated between the clothing boundary and shoes. Finally, the data were transmitted to the control system to move to the auxiliary position using the IoT method.</p>
                <fig fig-type="figure" id="f9" orientation="portrait" position="float">
                    <label>
Figure 9. </label>
                    <caption>
                        <title>Example results of boundary (upper). Example results of boundary (lower left). Example results of boundary (lower right).</title>
                    </caption>
                    <graphic id="gr9" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure9.gif"/>
                </fig>
            </sec>
            <sec id="sec5">
                <title>2.3 IoT control communication methods</title>
                <p>In recent years, the fusion of IoT technology and robotics for the Internet of Robots (IoRT) has been developed.
                    <sup>
                        <xref ref-type="bibr" rid="ref7">7</xref>,
                        <xref ref-type="bibr" rid="ref8">8</xref>
                    </sup> In this study, a combined IoT and robotics approach is used for a clothing boundary recognition control system. 
                    <xref ref-type="fig" rid="f10">
Figure 10</xref> shows the flowchart of IoT communication for the clothing boundary identification control system in 
                    <xref ref-type="fig" rid="f3">
Figure 3</xref>. The clothing boundary identification control IoT communication system is divided into three main layers: physical, network, and service application. 
                    <xref ref-type="fig" rid="f10">
Figure 10</xref> Left: data prediction physical layer; middle: data transmission network layer; right: robot service application layer. Stereo cameras were used to acquire images and models to compute the predictions. The predicted control commands are then transmitted to the cloud in the network layer. Finally, control commands are received at the robot service application layer to realize the auxiliary position movement control of the support robot. 
                    <xref ref-type="fig" rid="f11">
Figure 11</xref> shows the IoT data communication and control system hardware for dress-supporting robots in the robot service application layer. Obniz 1Y was used for the data communication. and Arduino for the control data processing. Finally, an L6470 control board was used to drive the lifting device of the support robot.</p>
                <fig fig-type="figure" id="f10" orientation="portrait" position="float">
                    <label>
Figure 10. </label>
                    <caption>
                        <title>Clothing boundary identification control IoT communication flow chart.</title>
                    </caption>
                    <graphic id="gr10" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure10.gif"/>
                </fig>
                <fig fig-type="figure" id="f11" orientation="portrait" position="float">
                    <label>
Figure 11. </label>
                    <caption>
                        <title>IoT data communication and control hardware system for clothing support.</title>
                    </caption>
                    <graphic id="gr11" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure11.gif"/>
                </fig>
            </sec>
        </sec>
        <sec id="sec6">
            <title>3. Exerimental results</title>
            <p>In the actual experiments, we fixed the relative position for stereo camera recognition to 79 cm high and the measurement distance to 130 cm. Because of the assistance of the system, the acquired recognition image must be a full-body image. However, it is not necessary to acquire and recognize dynamic images. Therefore, we fixed the relative position of the camera during our experiments. It is guaranteed that the entire body image information is obtained each time. The fixed height and measuring distance for the camera settings can also be adjusted to change if the acquisition of full-body image information can be guaranteed. In our experiments, we evaluate actual clothing boundary recognition and machine-assisted position control under different conditions. Examples include different lighting conditions, same-color or non-same-color pajamas, and standing or incomplete poses.</p>
            <p>
                <xref ref-type="table" rid="T2">
Table 2</xref> presents the evaluation results of the clothes boundary recognition and control experiments. The composite average correct recognition rate for clothing boundary recognition in different lighting environments with different jacket and pant color schemes was 77.35%. As shown in 
                <xref ref-type="table" rid="T2">
Table 2</xref>, we used nine different conditions for clothes the boundary recognition and control experiments. The clothes boundary recognition and control system can be affected by multiple factors. Therefore, we used the average of nine different conditions tor evaluate the accuracy of the combined environment. The control experiment is to used a stereo camera to recognize the auxiliary clothing boundary and computation to obtain the actual spatial height position information, and then used the IoT control system for robot control. The control accuracy of the stereo camera recognition control system in the control experiment was 97.21%.</p>
            <table-wrap id="T2" orientation="portrait" position="float">
                <label>
Table 2. </label>
                <caption>
                    <title>Clothing boundary recognition and control evaluation results.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top">NO.</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">1</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">2</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">3</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">4</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">5</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">6</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">7</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">8</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">9</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">10</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Daytime</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td colspan="1" rowspan="1"/>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Nighttime</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td colspan="1" rowspan="1"/>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Top and pants</bold>

                                <break/>

                                <bold>in the same color</bold>

                                <break/>

                                <bold>or non-same color</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25b3;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Overall</bold>

                                <break/>

                                <bold>Accuracy</bold>

                                <break/>

                                <bold>rate</bold>
</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>With or without</bold>

                                <break/>

                                <bold>image overexposure</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>NO</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>NO</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Large area</bold>

                                <break/>

                                <bold>strong</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Medium</bold>

                                <break/>

                                <bold>strong</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Small</bold>

                                <break/>

                                <bold>strong</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Large area</bold>

                                <break/>

                                <bold>Weak</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Medium</bold>

                                <break/>

                                <bold>Weak</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Medium</bold>

                                <break/>

                                <bold>Weak</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Small</bold>

                                <break/>

                                <bold>strong</bold>

                                <break/>

                                <bold>Weak</bold>
</td>
                            <td colspan="1" rowspan="1"/>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>With or without</bold>

                                <break/>

                                <bold>indoor light</bold>

                                <break/>

                                <bold>source</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x00d7;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">&#x25ef;</td>
                            <td colspan="1" rowspan="1"/>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Clothing boundary</bold>

                                <break/>

                                <bold>Recognition accuracy</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.8125</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.9368</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.5</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.8235</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.5937</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.9</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>77.35%</bold>
</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Control system</bold>

                                <break/>

                                <bold>movement accuracy</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.979</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.934</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.8823</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.857</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>97.21 %</bold>
</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Clothing boundary</bold>

                                <break/>

                                <bold>Recognition precision</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.808</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.931</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.465</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.823</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.13</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.9</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>74.7%</bold>
</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Control system</bold>

                                <break/>

                                <bold>movement precision</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.976</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.896</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.75</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0.857</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>94.8%</bold>
</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Clothing boundary</bold>

                                <break/>

                                <bold>Recognition Recall</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>0</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>100%</bold>
</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>Control system</bold>

                                <break/>

                                <bold>movement Recall</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>1</bold>
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">
                                <bold>100%</bold>
</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
            <p>
                <xref ref-type="table" rid="T2">
Table 2</xref> of Experiments 1 and 2 shows the evaluation of recognition control experiments for same-color and non-same-color clothing in a nighttime environment. It can be seen that the experiment in the night environment hads good recognition and control accuracy. Moreover, we verified the recognition effect in the case of incomplete standing (as shown in 
                <xref ref-type="fig" rid="f12">
Figure 12</xref>). In 
                <xref ref-type="fig" rid="f12">
Figure 12</xref>, the pink recognition line of 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mn>0</mml:mn>
                        </mml:msub>
                    </mml:math>
</inline-formula> image is the recognition result at 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mrow>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:mn>1</mml:mn>
                            </mml:mrow>
                        </mml:msub>
                    </mml:math>
</inline-formula> time, and the blue recognition line is the result of 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mn>0</mml:mn>
                        </mml:msub>
                    </mml:math>
</inline-formula> real time recognition. Because the recognition poses at time 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mrow>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:mn>1</mml:mn>
                            </mml:mrow>
                        </mml:msub>
                    </mml:math>
</inline-formula> and 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mn>0</mml:mn>
                        </mml:msub>
                    </mml:math>
</inline-formula> are basically the same, only a small recognition difference, for example, in 
                <xref ref-type="fig" rid="f12">
Figure 12</xref>, the 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mn>0</mml:mn>
                        </mml:msub>
                    </mml:math>
</inline-formula> time position information is 577.41mm and the 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mrow>
                                <mml:mo>+</mml:mo>
                                <mml:mn>1</mml:mn>
                            </mml:mrow>
                        </mml:msub>
                    </mml:math>
</inline-formula> time updated position information is 574.87 mm, the recognition control position difference is 2.54 mm.</p>
            <fig fig-type="figure" id="f12" orientation="portrait" position="float">
                <label>
Figure 12. </label>
                <caption>
                    <title>Recognition and control of results.</title>
                </caption>
                <graphic id="gr12" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure12.gif"/>
            </fig>
            <p>In 
                <xref ref-type="fig" rid="f12">
Figure 12</xref>, the recognition image at time 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>t</mml:mi>
                            <mml:mrow>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:mn>1</mml:mn>
                            </mml:mrow>
                        </mml:msub>
                    </mml:math>
</inline-formula> has a large deviation for the actual distance position calculation of the recognition line. We used calculation results below or above the robot's movement range, in which case the last position information is retained, and the movement control processing is not updated. Setting up a constraint mechanism ensures user safety. It has been verified that the cause of the positional distance error is that the foot semantic segmentation recognizes that the difference between the coordinates of the two points is too small, causing an error in the calculation. To avoid errors in the prediction and measurement, calculations of the semantic segmentation result in incorrect control of the robot. We have included mechanism of security range control to ensure user the safety. For example, no control is performed when the semantic segmentation of clothes is incompletely recognized or when boundaries are incompletely recognized. In addition, if the control command is not within the safe movable range. Thus, the system does not process the control. The reason for the recognition errors is incomplete recognition of the semantic segmentation of clothes or incomplete recognition of boundaries. If the feature diversity of the training set is increased. This can be improved to reduce the error rate and enhance the safety of the system.</p>
            <p>Incomplete recognition is caused by missing semantic segmentation categories. For example, the jacket category was not recognized and the other categories were correctly identified. The jacket and pant categories were recognized, but the shoes were not. We defined these cases as incomplete recognition. Incomplete recognition can lead to incorrect predictions of the actual spatial coordinates. This can ultimately lead to exceeding the control range of the robot.</p>
            <p>In 
                <xref ref-type="table" rid="T2">
Table 2</xref>, the jackets and trousers are homochromatic and non-homochromatic denotation symbols. &#x25ef;: clothes homochromatic, &#x00d7;: clothes non-homochromatic, &#x2206;: clothes non-homochromatic and homochromatic both. In 
                <xref ref-type="table" rid="T2">
Table 2</xref>, Experiments from 3 to 8 are the experiments performed in the daytime. In Experiment 3, the red boxed area in 
                <xref ref-type="fig" rid="f13">
Figure 13</xref>(3) is the case of a large over exposed area and an unlit room; in this case, it is not possible to recognize the correct semantic segmentation clothing boundaries. Experiments 4 and 5 aim to reduce the overexposed area, as shown in 
                <xref ref-type="fig" rid="f13">
Figure 13</xref>(4). The overexposed area is defined as the medium area, and 13(1) is the overexposed area defined as a small area. By changing the overexposure area, the recognition rate of the semantic segmentation of clothing boundaries was significantly improved in Experiments 3 and 4. Experiments 6, 7, and 8 were conducted with large-area overexposure and medium-area overexposure under weaker outdoor light than Experiments 3, 4, and 5. Experiments 3 and 6 compared the results, and it can be observed that there is a significant improvement in the recognition rate of clothing boundaries in a room with a light source. Experiments 7 and 8 showed higher recognition accuracy for non-homochromatic clothes than for homochromatic clothes in the non-homochromatic conditions for jackets and trousers. Experiments 4 and 8 show that overexposure to brightness reduces recognition accuracy.
                <disp-formula id="e26">

                    <mml:math display="block">
                        <mml:mtext mathvariant="italic">accuracy</mml:mtext>
                        <mml:mo>=</mml:mo>
                        <mml:mfrac>
                            <mml:mrow>
                                <mml:mi mathvariant="italic">TP</mml:mi>
                                <mml:mo>+</mml:mo>
                                <mml:mi mathvariant="italic">TN</mml:mi>
                            </mml:mrow>
                            <mml:mrow>
                                <mml:mi mathvariant="italic">TP</mml:mi>
                                <mml:mo>+</mml:mo>
                                <mml:mi mathvariant="italic">FP</mml:mi>
                                <mml:mo>+</mml:mo>
                                <mml:mi mathvariant="italic">TN</mml:mi>
                                <mml:mo>+</mml:mo>
                                <mml:mi mathvariant="italic">FN</mml:mi>
                            </mml:mrow>
                        </mml:mfrac>
                    </mml:math>

                    <label>(10)</label>
</disp-formula>

                <disp-formula id="e27">

                    <mml:math display="block">
                        <mml:mtext mathvariant="italic">precision</mml:mtext>
                        <mml:mo>=</mml:mo>
                        <mml:mfrac>
                            <mml:mi mathvariant="italic">TP</mml:mi>
                            <mml:mrow>
                                <mml:mi mathvariant="italic">TP</mml:mi>
                                <mml:mo>+</mml:mo>
                                <mml:mi mathvariant="italic">FP</mml:mi>
                            </mml:mrow>
                        </mml:mfrac>
                    </mml:math>

                    <label>(11)</label>
</disp-formula>

                <disp-formula id="e28">

                    <mml:math display="block">
                        <mml:mtext mathvariant="italic">Recall</mml:mtext>
                        <mml:mo>=</mml:mo>
                        <mml:mfrac>
                            <mml:mi mathvariant="italic">TP</mml:mi>
                            <mml:mrow>
                                <mml:mi mathvariant="italic">TP</mml:mi>
                                <mml:mo>+</mml:mo>
                                <mml:mi mathvariant="italic">FN</mml:mi>
                            </mml:mrow>
                        </mml:mfrac>
                    </mml:math>

                    <label>(12)</label>
</disp-formula>
            </p>
            <fig fig-type="figure" id="f13" orientation="portrait" position="float">
                <label>
Figure 13. </label>
                <caption>
                    <title>Experiment evaluation examples. (1) Clothing boundary Recognition: TP and Control system movement: TP. (2) Clothing boundary Recognition: FP and Control system movement: TN. (3) Clothing boundary Recognition: TN and Control system movement: TN. (4) Clothing boundary Recognition: TN and Control system movement: FP. (The left and right pictures are a group.)</title>
                </caption>
                <graphic id="gr13" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/173044/d4b854bc-cbea-4185-be90-90bfbb5326b1_figure13.gif"/>
            </fig>
            <p>In the experiment, semantic segmentation, clothing boundary prediction results, spatial distance information, and the control parameters were all without target parameters. Therefore, a manual evaluation method was used. A binary classification evaluation method. 
                <xref ref-type="disp-formula" rid="e26">
Equation 10</xref>
                <sup>
                    <xref ref-type="bibr" rid="ref12">12</xref>
                </sup> is our adopted accuracy rate evaluation Equation; 
                <xref ref-type="disp-formula" rid="e27">
Equation 11</xref> shows the precision rate
                <sup>
                    <xref ref-type="bibr" rid="ref12">12</xref>
                </sup>; 
                <xref ref-type="disp-formula" rid="e28">
Equation 12</xref> is the recall rate
                <sup>
                    <xref ref-type="bibr" rid="ref12">12</xref>
                </sup>; We performed a binary evaluation for clothing boundary identification prediction, spatial distance calculation, and control. In the evaluation, incorrectly calculated position information that does not perform an incorrect update of the control signal is not recorded as an incorrect identification or control.</p>
            <p>The experimental images evaluated were non-fixed test datasets, and real-time captured images were used as the evaluation data. The size of the evaluation image was fixed to the image size 480&#x00d7;480 for Pspnet network training. The training dataset comprised of 567 images. 
                <xref ref-type="table" rid="T3">
Table 3</xref> shows the experimental data for the positive and negative samples in the boundary identification evaluation and control system evaluation experiments and the total number of evaluation data for each experimental condition.</p>
            <table-wrap id="T3" orientation="portrait" position="float">
                <label>
Table 3. </label>
                <caption>
                    <title>Number of experimental evaluation data.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="2" valign="top"/>
                            <th align="left" colspan="2" rowspan="1" valign="top">Clothing boundary recognition</th>
                        </tr>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top">
Actual Ture+</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Actual False-</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Predicated P+</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">192</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">65</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Predicated N-
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">30</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="3" rowspan="1" valign="top">
                                <styled-content style="#FF0000" style-type="color">222/287= 0.7735</styled-content>
</td>
                        </tr>
                    </tbody>
                </table>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="2" valign="top"/>
                            <th align="left" colspan="2" rowspan="1" valign="top">Control system movement</th>
                        </tr>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top">Actual Ture+</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Actual False-</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Predicated P+</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">147</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">8</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Predicated N-
</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">132</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">0</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="3" rowspan="1" valign="top">
                                <styled-content style="#FF0000" style-type="color">279/287= 0.9721</styled-content>
</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 1:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">48</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 2:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">95</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 3:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">10</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 4:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">46</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 5:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">17</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 6:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">32</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 7:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">14</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 8:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">11</td>
                        </tr>
                        <tr>
                            <td align="char" char="&#x00d7;" colspan="2" rowspan="1" valign="top">Number of data evaluated for Experiment 9:</td>
                            <td align="char" char="&#x00d7;" colspan="1" rowspan="1" valign="top">14</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
            <p>In clothing boundary recognition, the TP of 
                <xref ref-type="disp-formula" rid="e26">
Equation 10</xref> was used to successfully recognize the predicted clothing boundary, and the predicted clothing boundary was correct. TN indicates that the clothing boundaries are not recognizable, but the clothing boundary results are unpredictable and considered correct. The FP successfully identified the predicted clothing boundary, but the prediction results were erroneous. In FN, the clothing boundaries are unrecognizable, but the clothing boundaries are recognised and the prediction results are incorrect.</p>
            <p>In addition, in evaluating the control system movement, the TP of 
                <xref ref-type="disp-formula" rid="e26">
Equation 10</xref>: the robot obtains the movement parameters and movement control command, and the movement parameters are correct. TN: The robot is given the no-movement parameter and no-movement control command, and the actual parameter command is no-movement, which is evaluated as correct. FP was successfully recognized to predict clothing boundaries, but the prediction results were incorrect. In FN, the clothing boundaries are unrecognizable, but the clothing boundaries are recognized and the prediction results are incorrect.
                <disp-formula id="e31">

                    <mml:math display="block">
                        <mml:mtext mathvariant="italic">Raev</mml:mtext>
                        <mml:mo>=</mml:mo>
                        <mml:mfrac>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:mi>A</mml:mi>
                                <mml:mi mathvariant="normal">m</mml:mi>
                                <mml:mi>v</mml:mi>
                                <mml:mo>&#x2212;</mml:mo>
                                <mml:mi mathvariant="italic">tv</mml:mi>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                            <mml:mrow>
                                <mml:mo stretchy="true">(</mml:mo>
                                <mml:mfrac>
                                    <mml:mi mathvariant="italic">tv</mml:mi>
                                    <mml:mn>100</mml:mn>
                                </mml:mfrac>
                                <mml:mo stretchy="true">)</mml:mo>
                            </mml:mrow>
                        </mml:mfrac>
                    </mml:math>

                    <label>(13)</label>
</disp-formula>

                <disp-formula id="e32">

                    <mml:math display="block">
                        <mml:mi mathvariant="italic">aev</mml:mi>
                        <mml:mo>=</mml:mo>
                        <mml:mi mathvariant="italic">Atv</mml:mi>
                        <mml:mo>&#x2212;</mml:mo>
                        <mml:mi mathvariant="italic">tv</mml:mi>
                    </mml:math>

                    <label>(14)</label>
</disp-formula>
            </p>
            <p>In our experiments, we used 
                <xref ref-type="disp-formula" rid="e31">
Equation 13</xref> and 
                <xref ref-type="disp-formula" rid="e32">
Equation 14</xref> to evaluate the stereo camera measurement accuracy by calculating the relative the mean error and mean error values obtained. 
                <xref ref-type="disp-formula" rid="e31">
Equation 13</xref> is used to calculate the relative mean error percentage, where Amv is the mean measured value, and tv is the true value. 
                <xref ref-type="disp-formula" rid="e32">
Equation 14</xref> represents the average error value.</p>
            <p>
                <xref ref-type="table" rid="T4">
Table 4</xref> shows the data on the average error of the measurement of the actual distance between two point pixels of the stereo camera evaluated in our experiments. Four cases were used to evaluate of the average measurement error. The first experimental evaluation case is when the pixel coordinate values 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xl</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> and 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xr</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> were in the positive and negative ranges (between 566 pixels at point 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi>l</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> x-coordinate and 675 pixels at point 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi>l</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> x-coordinate), the relative average error was -1.87% and the average error value was -5.55 mm. The second experimental evaluation case was when the pixel coordinate values 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xl</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> and 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xr</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> were in the positive range, the relative average error was 13.87% and the average error value was 41.22mm. In the third experimental case was when the pixel coordinate values 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xl</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> and 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xr</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> were both in the negative domain, the relative average error was 23.18%, and the average error value was 68.86mm. In the fourth experimental case, when the pixel coordinate values 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xl</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> and 
                <inline-formula>

                    <mml:math display="inline">
                        <mml:msub>
                            <mml:mi>P</mml:mi>
                            <mml:mi mathvariant="italic">xr</mml:mi>
                        </mml:msub>
                    </mml:math>
</inline-formula> are evaluated in the overall average of the above three cases, the relative average error is 16.73%, and the average error value is 49.70 mm.</p>
            <table-wrap id="T4" orientation="portrait" position="float">
                <label>
Table 4. </label>
                <caption>
                    <title>Stereo camera distance measurement accuracy evaluation results between two points.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top"/>
                            <th align="left" colspan="1" rowspan="1" valign="top">

                                <inline-formula>

                                    <mml:math display="inline">
                                        <mml:msub>
                                            <mml:mi>P</mml:mi>
                                            <mml:mi mathvariant="italic">xl</mml:mi>
                                        </mml:msub>
                                    </mml:math>
</inline-formula> and 
                                <inline-formula>

                                    <mml:math display="inline">
                                        <mml:msub>
                                            <mml:mi>P</mml:mi>
                                            <mml:mi mathvariant="italic">xr</mml:mi>
                                        </mml:msub>
                                    </mml:math>
</inline-formula> in the positive and negative domain</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">

                                <inline-formula>

                                    <mml:math display="inline">
                                        <mml:msub>
                                            <mml:mi>P</mml:mi>
                                            <mml:mi mathvariant="italic">xl</mml:mi>
                                        </mml:msub>
                                    </mml:math>
</inline-formula> and 
                                <inline-formula>

                                    <mml:math display="inline">
                                        <mml:msub>
                                            <mml:mi>P</mml:mi>
                                            <mml:mi mathvariant="italic">xr</mml:mi>
                                        </mml:msub>
                                    </mml:math>
</inline-formula> in the positive domain</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">

                                <inline-formula>

                                    <mml:math display="inline">
                                        <mml:msub>
                                            <mml:mi>P</mml:mi>
                                            <mml:mi mathvariant="italic">xl</mml:mi>
                                        </mml:msub>
                                    </mml:math>
</inline-formula> and 
                                <inline-formula>

                                    <mml:math display="inline">
                                        <mml:msub>
                                            <mml:mi>P</mml:mi>
                                            <mml:mi mathvariant="italic">xr</mml:mi>
                                        </mml:msub>
                                    </mml:math>
</inline-formula> in the negative domain</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Total average error</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Relative error rate</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">-1.87%</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">13.87%</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">23.18%</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">16.73%</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Average error value</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">-5.55mm</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">41.22mm</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">68.86mm</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">49.70mm</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
        </sec>
        <sec id="sec7" sec-type="conclusion">
            <title>4. Conclusion</title>
            <p>In this paper, we present the design and development of a clothing-assisted support robot for elderly people's homes or toilet environments in the home. In cases where the elderly or patients in the toilet have difficulty standing autonomously, hands are used to support standing or muscle weakness in both hands, the assisted position is identified and adjusted autonomously through a recognition system without the assistance of a nurse or a caregiver, Assist to complete the action of dressing and undressing. For this purpose, we propose a machine vision control scheme for a clothes-wearing support robot that can be applied to toilet scenes. Using stereo camera depth information and image information, the IoT control system is based on deep learning and machine learning for clothing boundary recognition and calculation of spatial position information. In an experiment to verify the standing or incomplete standing situation of the assisted person, the recognition of clothing-specific boundaries and the actual spatial height position calculation can be performed to control the robot to move to the assisted position.</p>
            <p>We implemented a multi-technology fusion of a clothing boundary recognition and control system. However, it is still not possible to fully implement a high autorecognition control. Moreover, because of the fusion of multiple technologies, the accuracy is reduced. Because of, the accuracy of the image recognition, the accuracy of the binocular camera measurement and the accuracy of the communication control system each lose accuracy; therefore, the accuracy is greatly reduced in the final recognition control feedback. This is also a topic for future study.</p>
            <p>In addition, it recognizes high real-time problems. This is because the Pspnet model is not highly real-time and uses multi-stage processing. The processing of data dimensionality reduction was used in the SVM stage to improve the computational speed. However, this does not fully realize the high real-time performance of clothing boundary recognition. Moreover, communication in combination with IoT has some latency, increasing the problem of not being able to operate in real-time. This will be addressed in a future study. This problem can be further improved if an end-to-end modeling pattern is used, and the model design and adjustment are based on prior research on semantic segmentation models with real-time capability.</p>
        </sec>
        <sec id="sec8">
            <title>Ethics and consent</title>
            <p>Not applicable.</p>
        </sec>
    </body>
    <back>
        <sec id="sec11">
            <title>Data availability</title>
            <sec id="sec12">
                <title>Underlying data</title>
                <p>Param Aggarwal. (2019). Fashion Product Images (Small) [Data set]. Kaggle.</p>
                <p>DOI: 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.34740/KAGGLE/DS/175990">https://doi.org/10.34740/KAGGLE/DS/175990</ext-link>
                    <sup>
                        <xref ref-type="bibr" rid="ref19">19</xref>
                    </sup>
                </p>
            </sec>
            <sec id="sec13">
                <title>Extended data</title>
                <p>This is extended supplementary data that extends the semantic segmentation images of the dressing support robot.</p>
                <p>DOI: 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.27987545.v2">https://doi.org/10.6084/m9.figshare.27987545.v2</ext-link>
                    <sup>
                        <xref ref-type="bibr" rid="ref20">20</xref>
                    </sup>
                </p>
                <p>Experimental video</p>
                <p>DOI: 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.6084/m9.figshare.27377199.v3">https://doi.org/10.6084/m9.figshare.27377199.v3</ext-link>
                    <sup>
                        <xref ref-type="bibr" rid="ref21">21</xref>
                    </sup>
                </p>
                <p>

                    <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">All the data is available under cc by 4.0 license</ext-link>
                </p>
            </sec>
        </sec>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <label>1</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Nambo</surname>
                            <given-names>H</given-names>
                        </name>
</person-group>:
                    <chapter-title>A System of Clothing Boundary Recognition Using Machine Learning For Life Support Robots.</chapter-title>
                    <source>

                        <italic toggle="yes">2020 5th International Conference on Intelligent Informatics and Biomedical Sciences (ICIIBMS 2020).</italic>
</source>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <etal/>
</person-group>:
                    <article-title>A novel algorithm for distance measurement using stereo camera.</article-title>
                    <source>

                        <italic toggle="yes">CAAI Transactions on Intelligence Technology.</italic>
</source>
                    <year>2022</year>;<volume>7</volume>;<fpage>177</fpage>&#x2013;<lpage>186</lpage>.
                    <pub-id pub-id-type="doi">10.1049/cit2.12098</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Said</surname>
                            <given-names>AF</given-names>
                        </name>
</person-group>:
                    <chapter-title>ROBUST AND ACCURATE OBJECTS MEASUREMENT IN REAL-WORLD BASED ON CAMERA SYSTEM.</chapter-title>
                    <source>

                        <italic toggle="yes">IEEE Applied Imagery Pattern Recognition Workshop (AIPR).</italic>
</source>
                    <year>2017</year>.</mixed-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Limeng</surname>
                            <given-names>P</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <chapter-title>Novel Object-Size Measurement Using the Digital Camera.</chapter-title>
                    <source>

                        <italic toggle="yes">IEEE Advanced Information Management, Communicates, Electronic and Automation Control Conference (IMCEC).</italic>
</source>
                    <year>2016</year>.</mixed-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Vo-Le</surname>
                            <given-names>C</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Van Muoi</surname>
                            <given-names>P</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <chapter-title>Automatic Method for Measuring Object Size Using 3D Camera.</chapter-title>
                    <source>

                        <italic toggle="yes">IEEE Eighth International Conference on Communications and Electronics (ICCE).</italic>
</source>
                    <year>2020</year>.</mixed-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

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

                        <etal/>
</person-group>:
                    <chapter-title>Pyramid scene parsing network.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the IEEE conference on computer vision and pattern recognition.</italic>
</source>
                    <year>2017</year>.</mixed-citation>
            </ref>
            <ref id="ref7">
                <label>7</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Villa</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Song</surname>
                            <given-names>X</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <article-title>Internet of Robotic Things: Current Technologies, Applications, Challenges and Future Directions.</article-title>
                    <source>

                        <italic toggle="yes">arXiv:2101.06256.</italic>
</source>
                    <year>Jan 2021</year>.</mixed-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Afanasyev</surname>
                            <given-names>I</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <chapter-title>Towards the Internet of Robotic Things: Analysis, Architecture, Components and Challenges.</chapter-title>
                    <source>

                        <italic toggle="yes">12th International Conference on Developments in eSystems Engineering (DeSE).</italic>
</source>
                    <year>2019</year>.</mixed-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Demiris</surname>
                            <given-names>Y</given-names>
                        </name>
</person-group>:
                    <chapter-title>Learning grasping points for garment manipulation in robot-assisted dressing.</chapter-title>
                    <source>

                        <italic toggle="yes">2020 IEEE International Conference on Robotics and Automation (ICRA).</italic>
</source>
                    <publisher-name>IEEE</publisher-name>;<year>2020</year>.</mixed-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhang</surname>
                            <given-names>F</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cully</surname>
                            <given-names>A</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Demiris</surname>
                            <given-names>Y</given-names>
                        </name>
</person-group>:
                    <article-title>Probabilistic real-time user posture tracking for personalized robot-assisted dressing.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Robot.</italic>
</source>
                    <year>2019</year>;<volume>35</volume>(<issue>4</issue>):<fpage>873</fpage>&#x2013;<lpage>888</lpage>.
                    <pub-id pub-id-type="doi">10.1109/TRO.2019.2904461</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <label>11</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <chapter-title>Tracking objects with point clouds from vision and touch.</chapter-title>
                    <source>

                        <italic toggle="yes">Proc. IEEE Int. Conf. Robot.</italic>
</source>
                    <publisher-name>Au-tom</publisher-name>;<year>2017</year>; pp.<fpage>4000</fpage>&#x2013;<lpage>4007</lpage>.</mixed-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Visani</surname>
                            <given-names>G</given-names>
                        </name>
</person-group>:
                    <article-title>Metrics for multi-class classification: an overview.</article-title>
                    <source>

                        <italic toggle="yes">arXiv preprint arXiv:2008.05756.</italic>
</source>
                    <year>2020</year>.</mixed-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Gao</surname>
                            <given-names>Y</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <chapter-title>User Modelling for Personalised Dressing Assistance by HumanoidRobots.</chapter-title>
                    <source>

                        <italic toggle="yes">IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS).</italic>
</source>
                    <year>2015</year>.
                    <pub-id pub-id-type="doi">10.1109/IROS.2015.7353617</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Jipeng</surname>
                            <given-names>W</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <article-title>Real-time semantic segmentation via sequential knowledge distillation.</article-title>
                    <source>

                        <italic toggle="yes">Neurocomputing.</italic>
</source>
                    <year>June 2021</year>;<volume>439</volume>(<issue>7</issue>):<fpage>134</fpage>&#x2013;<lpage>145</lpage>.
                    <pub-id pub-id-type="doi">10.1016/j.neucom.2021.01.086</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Yu</surname>
                            <given-names>Z</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <chapter-title>Casenet: Deep category-aware semantic edge detection.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the IEEE conference on computer vision and pattern recognition.</italic>
</source>
                    <year>2017</year>.</mixed-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

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

                        <etal/>
</person-group>:
                    <chapter-title>Rindnet: Edge detection for discontinuity in reflectance, illumination, normal and depth.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the IEEE/CVF international conference on computer vision.</italic>
</source>
                    <year>2021</year>.</mixed-citation>
            </ref>
            <ref id="ref17">
                <label>17</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Xie</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Zhuowen</surname>
                            <given-names>T</given-names>
                        </name>
</person-group>:
                    <chapter-title>Holistically-nested edge detection.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the IEEE international conference on computer vision.</italic>
</source>
                    <year>2015</year>.</mixed-citation>
            </ref>
            <ref id="ref18">
                <label>18</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Kalkan</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Akbas</surname>
                            <given-names>E</given-names>
                        </name>
</person-group>:
                    <chapter-title>RankED: Addressing Imbalance and Uncertainty in Edge Detection Using Ranking-based Losses.</chapter-title>
                    <source>

                        <italic toggle="yes">roceedings of the IEEE/CVF Conference on Computer Vision and Pattern Recognition.</italic>
</source>
                    <year>2024</year>.</mixed-citation>
            </ref>
            <ref id="ref19">
                <label>19</label>
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Param</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <data-title>Fashion Product Images (Small)</data-title>. [Data set]. Kaggle.<year>2019</year>.
                    <pub-id pub-id-type="doi">10.34740/KAGGLE/DS/175990</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhao</surname>
                            <given-names>H</given-names>
                        </name>
</person-group>:
                    <data-title>Trian dataset. figshare.</data-title>[Dataset].<year>2024</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.27987545.v2</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <mixed-citation publication-type="data">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zhao</surname>
                            <given-names>H</given-names>
                        </name>
</person-group>:
                    <data-title>Supplemental video of the experiment.zip. figshare.</data-title>Media.<year>2024</year>.
                    <pub-id pub-id-type="doi">10.6084/m9.figshare.27377199.v3</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report385724">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.173044.r385724</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Lee</surname>
                        <given-names>Jiho</given-names>
                    </name>
                    <xref ref-type="aff" rid="r385724a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-2830-3487</uri>
                </contrib>
                <aff id="r385724a1">
                    <label>1</label>Purdue University, West Lafayette, USA</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>13</day>
                <month>6</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Lee J</copyright-statement>
                <copyright-year>2025</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="relatedArticleReport385724" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.157582.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>reject</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This paper titled "Using machine learning based stereo camera clothing boundary recognition control system for dressing assistance support robot" presents a vision-based control system for dressing assistance, utilizing PSPNet-based semantic segmentation, stereo camera-based spatial measurement, and IoT-enabled lifting mechanisms. The proposed system aims to support elderly or mobility-impaired users by automatically identifying clothing boundaries and controlling lifting positions. While the application domain is socially relevant and the structure of the manuscript follows a logical pipeline, several areas require substantial clarification and enhancement for scientific soundness and reproducibility. The main technical contribution is the combination of semantic segmentation and SVM-based classification to identify jacket and pant boundaries (Section 2.1), followed by stereo camera-based 3D distance estimation (Section 2.2), and IoT-based actuation (Section 2.3). However, the paper falls short in multiple aspects that must be addressed:</p>
            <p> </p>
            <p> 1. In Section 2.1, the rationale for selecting PSPNet as the semantic segmentation model is not adequately justified. The authors mention that real-time capability was sacrificed in favor of accuracy, but no comparative results (e.g., with ENet, BiSeNet, or other lightweight models) are provided to support this trade-off. Similarly, the Canny edge filter and subsequent SVM classification are not benchmarked against alternative boundary refinement techniques.</p>
            <p> </p>
            <p> 2. The paper introduces a multi-stage pipeline involving i) semantic segmentation, ii) Canny edge extraction, and iii) SVM-based boundary classification. While the concept is reasonable, the model training pipeline lacks essential details, including the architecture settings of PSPNet (e.g., input size, backbone), SVM feature selection and dimensionality, Hyperparameter settings, and Learning curves or convergence behavior. This lack of transparency makes it difficult to reproduce or validate the proposed system.</p>
            <p> </p>
            <p> 3. In Section 2.2, the stereo camera-based spatial calculation is described in great mathematical detail, but implementation-level clarity is lacking. For instance, the transition from disparity map to actual point cloud coordinates is explained theoretically but without examples of how these are implemented in practice (e.g., via ZED2 SDK, OpenCV stereo matching settings, calibration parameters). Including a sample pseudo-code or data flow chart would greatly improve understanding.</p>
            <p> </p>
            <p> 4. Figure 1 and Figure 2 merely present whole-device photos and 3D renderings without labels. These figures would be much more informative if the authors annotated key components such as the stereo camera, lifting actuator, clothing region, and IoT controller modules. Currently, the figures fail to visually support the textual explanation. Similarly, in Figure 9, the font size of the embedded text is too small to be legible and should be improved for clarity.</p>
            <p> </p>
            <p> 5. Although experimental results are reported across 9 conditions (Table 3), the evaluation lacks statistical rigor. Accuracy, precision, and recall are listed without confidence intervals or standard deviations. More importantly, the methodology excludes mispredictions from being counted as errors if they do not result in actuator movement, which introduces a significant bias and overestimates performance.</p>
            <p> </p>
            <p> 6. The boundary recognition accuracy of 77.35% and control system accuracy of 97.21% (Table 2) are promising, but the system&#x2019;s limitations should be better acknowledged. For example, the authors briefly mention that the segmentation fails under certain lighting or overexposure conditions, but there is no structured analysis of failure modes.</p>
            <p> </p>
            <p> 7. The system is described as a &#x201c;dressing assistance robot,&#x201d; yet it does not perform any physical manipulation of garments. It would be more appropriate to present this as a perceptual support module for dressing assistance, as the only mechanical component is a linear lifting actuator. This point should be reflected both in the title and throughout the manuscript to avoid overstating the contribution.</p>
            <p> </p>
            <p> 8. While the authors claim that the system operates in real time, there is no measurement of system latency or processing speed (FPS). Since PSPNet is known for high computational cost, omitting this information weakens the real-time claim.</p>
            <p> </p>
            <p> 9. Finally, the manuscript would benefit from a careful language edit. Several sentences are grammatically awkward or ambiguous. For example, the phrase &#x201c;the jacket and pant categories were recognized, but the shoes were not. We defined these cases as incomplete recognition&#x201d; can be stated more clearly. A professional proofreading would significantly improve readability and credibility.</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>Partly</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>No</p>
            <p>Reviewer Expertise:</p>
            <p>AI in Smart Manufacturing, Robotic automation, Vision recognition for autonomous systems.</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report381636">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.173044.r381636</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Yamasaki</surname>
                        <given-names>Kakeru</given-names>
                    </name>
                    <xref ref-type="aff" rid="r381636a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0009-0003-6777-6903</uri>
                </contrib>
                <aff id="r381636a1">
                    <label>1</label>Kyushu Institute of Technology, Kitakyushu, Japan</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>5</month>
                <year>2025</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2025 Yamasaki K</copyright-statement>
                <copyright-year>2025</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>
                <license>
                    <license-p>The author(s) is/are employees of the US Government and therefore domestic copyright protection in USA does not apply to this work. The work may be protected under the copyright laws of other jurisdictions when used in those jurisdictions.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport381636" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.157582.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>reject</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>
                <bold>Summary:</bold>
            </p>
            <p> This manuscript proposes a vision-based control system for dressing assistance, combining semantic segmentation (PSPNet), stereo camera-based depth estimation, and IoT-based actuation. While the topic is societally relevant, particularly for elderly care, there are significant issues in presentation, reproducibility, evaluation rigor, and alignment between claimed contributions and actual implementation.</p>
            <p> 
                <bold>Evaluation Breakdown and Corresponding Comments</bold>
            </p>
            <p> 
                <bold>1. Is the work clearly and accurately presented and does it cite the current literature? &#x2192; Partly</bold>
            </p>
            <p> The manuscript presents the system pipeline with reasonable clarity, but its contextualization in the field is lacking. The literature review does not sufficiently reference or engage with prior work on robotic dressing assistance, such as: 
                <list list-type="bullet">
                    <list-item>
                        <p>Cloth manipulation strategies</p>
                    </list-item>
                    <list-item>
                        <p>Personalized HRI and adaptation</p>
                    </list-item>
                    <list-item>
                        <p>Assist-as-needed (AAN) control</p>
                    </list-item>
                    <list-item>
                        <p>Safety constraints in physical HRI</p>
                    </list-item>
                </list> Without this, the novelty of the work remains unclear, and its connection to existing challenges in assistive robotics is weak.</p>
            <p> 
                <bold>2. Is the study design appropriate and is the work technically sound? &#x2192; Partly</bold>
            </p>
            <p> The integration of stereo vision and machine learning is well motivated, but the model selection and system design lack sufficient technical depth. The choice of PSPNet is not justified through comparative evaluation, and no ablation studies or benchmarks are provided. There is also no performance comparison with other semantic segmentation architectures. Moreover, the robotic component is limited to a lifting mechanism without autonomous clothing manipulation.</p>
            <p> 
                <bold>3. Are sufficient details of methods and analysis provided to allow replication by others? &#x2192; No</bold>
            </p>
            <p> Key implementation details are missing. The authors do not provide: 
                <list list-type="bullet">
                    <list-item>
                        <p>Training hyperparameters</p>
                    </list-item>
                    <list-item>
                        <p>Learning curves</p>
                    </list-item>
                    <list-item>
                        <p>Feature representation used in the SVM</p>
                    </list-item>
                    <list-item>
                        <p>Source code or pre-trained models</p>
                    </list-item>
                </list> This lack of detail makes it impossible for other researchers to replicate or validate the study.</p>
            <p> 
                <bold>4. If applicable, is the statistical analysis and its interpretation appropriate? &#x2192; Partly</bold>
            </p>
            <p> Although basic performance metrics (accuracy, precision, recall) are reported, the manuscript lacks statistical rigor. There are no standard deviations, significance tests, or error bars, making it difficult to assess the reliability of the reported improvements across experimental conditions.</p>
            <p> 
                <bold>5. Are all the source data underlying the results available to ensure full reproducibility? &#x2192; Partly</bold>
            </p>
            <p> The authors reference public datasets (e.g., Kaggle and figshare), but these are insufficient to reproduce the study. The critical training dataset, evaluation code, and configuration details are not shared. As a result, full reproducibility is not achieved.</p>
            <p> 
                <bold>6. Are the conclusions drawn adequately supported by the results? &#x2192; Partly</bold>
            </p>
            <p> The conclusions overstate the system&#x2019;s contribution in the context of robotic assistance. Although the authors refer to their system as a "robot," the implementation consists solely of a vertical lift actuator without any articulated robotic manipulation or autonomous interaction with garments. As such, it falls short of what is typically expected in robotic dressing assistance research, where end-effectors, compliant arms, motion planning, and physical human-robot interaction are often involved.</p>
            <p> Moreover, the paper fails to compare its system to prior works that implement full or partial robotic dressing capabilities, such as systems capable of handling shirts, jackets, or pants using arms and grippers. These earlier works address core challenges, including cloth deformation, safety in physical interaction, and real-time human state estimation. The current work does not acknowledge these efforts or clarify how its contribution fits into this landscape.</p>
            <p> Additionally, the evaluation is performed manually, but the protocol is not described in sufficient detail. There is no mention of inter-rater agreement or validation, and the fact that mispredictions are excluded from being counted as errors if they do not cause incorrect movement introduces potential bias. This undermines the strength of the conclusions drawn.</p>
            <p> To justify claims of robotic contribution, the authors should either develop a more integrated robotic system or reframe the work as a perceptual support module for future robotic dressing systems.</p>
            <p> 
                <bold>Additional Issues</bold> 
                <list list-type="bullet">
                    <list-item>
                        <p>The evaluation method is manual due to the absence of ground truth, but no formal procedure or inter-rater reliability is reported. Furthermore, mispredictions that do not lead to control errors are excluded from being counted as errors, which inflates reported accuracy.</p>
                    </list-item>
                    <list-item>
                        <p>The robotic contribution is minimal and not justified under the title. It would be more accurate to present this work as a perception-based control support module rather than a robotic dressing system.</p>
                    </list-item>
                    <list-item>
                        <p>Real-time performance claims are made, but no FPS or latency benchmarks are presented.</p>
                    </list-item>
                </list> 
                <bold>Required Revisions Before Indexing</bold> 
                <list list-type="order">
                    <list-item>
                        <p>Revise the title and claims to reflect the actual scope (i.e., remove or qualify "robot").</p>
                    </list-item>
                    <list-item>
                        <p>Expand the literature review to include recent and relevant work on robotic dressing, human-robot interaction, and cloth manipulation.</p>
                    </list-item>
                    <list-item>
                        <p>Include benchmark comparisons or justification for the model choice.</p>
                    </list-item>
                    <list-item>
                        <p>Disclose training settings, provide code and datasets, and show learning curves or training behavior.</p>
                    </list-item>
                    <list-item>
                        <p>Define a clear and objective evaluation protocol or label a validation dataset for quantitative assessment.</p>
                    </list-item>
                    <list-item>
                        <p>Include standard deviation or confidence intervals and consider statistical significance testing.</p>
                    </list-item>
                    <list-item>
                        <p>Discuss the practical limits of the current system, especially regarding real-time constraints and generalizability.</p>
                    </list-item>
                </list>
            </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>Partly</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>No</p>
            <p>Reviewer Expertise:</p>
            <p>Human-Robot Interaction, Assistive Robotics, Robotic Manipulation, Elderly Care Technology</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above.</p>
        </body>
    </sub-article>
</article>
