<?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="other" 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.129826.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Software Tool Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>PyRadGUI: A GUI based radiomics extractor software</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 3 approved with reservations]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no" equal-contrib="yes">
                    <name>
                        <surname>Sherkhane</surname>
                        <given-names>Umesh B.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <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/">Software</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>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes" equal-contrib="yes">
                    <name>
                        <surname>Jha</surname>
                        <given-names>Ashish Kumar</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <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/">Software</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-0001-5998-3206</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a2">2</xref>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Mithun</surname>
                        <given-names>Sneha</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/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a2">2</xref>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Jaiswar</surname>
                        <given-names>Vinay</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/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Traverso</surname>
                        <given-names>Alberto</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/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Wee</surname>
                        <given-names>Leonard</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Rangarajan</surname>
                        <given-names>Venkatesh</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Dekker</surname>
                        <given-names>Andre</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Department of Radiation Oncology (Maastro), GROW School for Oncology, Maastricht University Medical Centre+, 6229 ET, Maastricht, 6229, The Netherlands</aff>
                <aff id="a2">
                    <label>2</label>Department of Nuclear Medicine and Molecular Imaging, Tata Memorial Hospital, Mumbai, 400012, India</aff>
                <aff id="a3">
                    <label>3</label>Homi Bhabha National Institute (HBNI), Deemed University, Mumbai, 400012, India</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:ashish.kumar.jha.77@gmail.com">ashish.kumar.jha.77@gmail.com</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>10</day>
                <month>3</month>
                <year>2023</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2023</year>
            </pub-date>
            <volume>12</volume>
            <elocation-id>259</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>26</day>
                    <month>1</month>
                    <year>2023</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Sherkhane UB et al.</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/12-259/pdf"/>
            <abstract>
                <p>Radiomics is the method of extracting high throughput mathematical and statistical features from medical images. These features have the potential to characterize the underlying pathology of the disease that is inappreciable to a trained human eye. There are several open-source and licensed tools to extract radiomic features such as pyradiomics, LIFEx, TexRAD, and RaCat. Although pyradiomics is a widely used radiomics package by researchers, this software is not very user-friendly and can be run using a command line. We have developed and validated the GUI tool, PyRadGUI to make the radiomics software easy to operate. This software adheres to IBSI radiomic feature definition and implements the radiomic pipeline in batch processing to extract radiomic features from multiple patient&#x2019;s data and stores it in a comma separated value (CSV). We validated PyRadGUI software with the existing pyradiomic pipeline.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Graphical User Interface (GUI)</kwd>
                <kwd>machine learning</kwd>
                <kwd>radiomics</kwd>
                <kwd>pyradiomics</kwd>
                <kwd>plastimatch</kwd>
                <kwd>3DSlicer</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1">
                    <funding-source> The Netherlands Enterprise Agency (RVO) and MeITy</funding-source>
                </award-group>
                <funding-statement>Project is funded by The Netherlands Enterprise Agency (RVO) and MeITy for the Indo-Dutch NWO/MeITy BIONIC and TRAIN project.</funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec1">
            <title>Instruction</title>
            <p>As per the World health organization (WHO), cancer is the second leading cause of death worldwide. Globally one out of six deaths are caused by cancer alone which amounts to 9.6 million deaths in 2018 (
                <ext-link ext-link-type="uri" xlink:href="https://www.who.int/news-room/fact-sheets/detail/cancer">WHO-Cancer, 2022</ext-link>; 
                <xref ref-type="bibr" rid="ref7">Ferlay 
                    <italic toggle="yes">et al.</italic>, 2019</xref>). Treatment of cancer has always remained a challenging task for the oncology community. Although earlier diagnosis and treatment are often associated with a better outcome of treatment, at the same time selection of appropriate patients for appropriate treatment is important (
                <xref ref-type="bibr" rid="ref20">Stewart 
                    <italic toggle="yes">et al.</italic>, 2018</xref>). Considering the complexity of this disease and treatment, oncology is gradually moving towards personalized medicine (
                <xref ref-type="bibr" rid="ref2">Agyeman and Ofori-Asenso, 2015</xref>). A pathological test is considered a confirmatory test for cancer. Imaging tests like Computed Tomography (CT)/Positron Emission Tomography (PET)/Magnetic Resonance Imaging (MRI) also play an important role in diagnosis, treatment planning, and follow-up of the disease (
                <xref ref-type="bibr" rid="ref4">Caers 
                    <italic toggle="yes">et al.</italic>, 2014</xref>). In the last several years, the role of imaging and various advanced tests like immunohistochemistry (IHC), polymerase chain reaction (PCR), and gene sequencing has been increasing gradually in personalizing the treatment. Similarly, the role of artificial intelligence (AI) and radiomics has also witnessed a surge in oncology research over the last few years. Radiomics has been identified as an area of research to develop imaging biomarkers for the personalized treatment of cancer (
                <xref ref-type="bibr" rid="ref15">Lambin 
                    <italic toggle="yes">et al.</italic>, 2012</xref>; 
                <xref ref-type="bibr" rid="ref1">Aerts 
                    <italic toggle="yes">et al.</italic>, 2014</xref>; 
                <xref ref-type="bibr" rid="ref9">Goodwin 
                    <italic toggle="yes">et al.</italic>, 2017</xref>). Radiomics is a method to extract high throughput data from medical images. These features have the potential to uncover disease characteristics that are not appreciated by the expert radiologist or imaging personnel through visual interpretation (
                <xref ref-type="bibr" rid="ref22">Yip 
                    <italic toggle="yes">et al.</italic>, 2017</xref>). As radiomic features are extracted directly from medical images it provides a non-invasive method for tumor characterization as demonstrated by various researchers in the past (
                <xref ref-type="bibr" rid="ref15">Lambin 
                    <italic toggle="yes">et al.</italic>, 2012</xref>; 
                <xref ref-type="bibr" rid="ref9">Goodwin 
                    <italic toggle="yes">et al.</italic>, 2017</xref>; 
                <xref ref-type="bibr" rid="ref1">Aerts 
                    <italic toggle="yes">et al.</italic>, 2014</xref>). Researchers have shown the role of radiomics as a clinical predictor helping in advanced cancer care as personalized medicine in cancer (
                <xref ref-type="bibr" rid="ref12">Haider 
                    <italic toggle="yes">et al.</italic>, 2020</xref>). Apart from its role in precision diagnoses and characterization of a tumor, the role of radiomics has also been demonstrated in treatment planning (
                <xref ref-type="bibr" rid="ref16">Limkin 
                    <italic toggle="yes">et al.</italic>, 2017</xref>).</p>
            <p>Several open-source and licensed software packages for radiomic extraction, like IBEX, RaCaT, CaPTK, LifeX or CGITA, Pyradiomics, and TexRad have been developed and used by several researchers in the past (
                <xref ref-type="bibr" rid="ref18">Pfaehler 
                    <italic toggle="yes">et al.</italic>,2019</xref>; 
                <xref ref-type="bibr" rid="ref17">Nioche 
                    <italic toggle="yes">et al.</italic>, 2018</xref>; 
                <xref ref-type="bibr" rid="ref23">Zhang 
                    <italic toggle="yes">et al.</italic>, 2015</xref>; 
                <xref ref-type="bibr" rid="ref5">Davatzikos 
                    <italic toggle="yes">et al.</italic>, 2018</xref>; 
                <xref ref-type="bibr" rid="ref14">Johnson, 2015</xref>; 
                <xref ref-type="bibr" rid="ref13">Haralick 
                    <italic toggle="yes">et al.</italic>, 1973</xref>).</p>
            <p>The main challenges with these software packages are the complexity of radiomic extraction and the lack of standardized feature extraction from this software. The mathematical feature definitions have been provided image biomarker standardization initiative (IBSI) to standardize the radiomic extraction. It has also provided the phantom data sets with radiomic feature values (
                <xref ref-type="bibr" rid="ref25">Zwanenburg, 2017</xref>; 
                <xref ref-type="bibr" rid="ref26">Zwanenburg 
                    <italic toggle="yes">et al.</italic>, 2016</xref>). Although IBSI standard is widely known, only a very few radiomic softwares have standardized the entire radiomic pipeline for feature extraction. Furthermore, the majority of these radiomic extractors have operability issues and not all defined features are extracted as defined by IBSI. Pyradiomics is a widely-used open source radiomics package and adheres to the IBSI standards, but it is not user-friendly. For instance, Pyradiomics is run on a command prompt and customization is technically demanding. Hence, the use of this software is cumbersome and technically demanding for clinical doctors or scientists.</p>
            <p>In this study, we have developed and validated a graphical user interface (GUI) based radiomic extraction software using the pyradiomics package. This software adheres to all features defined by the IBSI.</p>
        </sec>
        <sec id="sec2" sec-type="methods">
            <title>Methods</title>
            <p>This work is part of the Big Imaging data approach for Oncology in a Netherlands India Collaboration (BIONIC) and &#x201c;personal health Train for radiation oncology in India and the Netherlands&#x201d; (TRAIN) project is approved by the IEC of the hospital as a retrospective study. This software (PyRadGUI) was developed using Python open-source software on Windows systems.</p>
            <sec id="sec3">
                <title>Ethical considerations</title>
                <p>This study was approved by the hospital Institutional Ethics Committee (Institutional Ethics Committee-I, Tata Memorial Centre [IEC, TMC], Mumbai, India Approval Number: 1905; dated: October 05, 2017) as a retrospective study, with waivers of informed consent from involved patients as per IEC policy of our hospital by the same Ethics Committee.</p>
            </sec>
            <sec id="sec4">
                <title>Software development</title>
                <p>PyRadGUI front end was developed by using the open-source software Python 3.6.5 
                    <bold>(</bold>
                    <ext-link ext-link-type="uri" xlink:href="https://docs.python.org/3/">Python, 2022</ext-link>) and the Python tk8.6 (
                    <ext-link ext-link-type="uri" xlink:href="https://docs.python.org/3/library/tkinter.html">Python tk, 2022</ext-link>) module was used for the development of the graphical user interface (GUI). The open source Plastimatch package 1.8.0 (
                    <ext-link ext-link-type="uri" xlink:href="http://www.plastimatch.org/">Plastimatch, 2022</ext-link>) was used for Digital Imaging and Communications in Medicine (DICOM) to Nearly Raw Raster Data (NRRD) conversion of imaging data and the radiomic package in python; Pyradiomics 3.0 (
                    <xref ref-type="bibr" rid="ref11">Griethuysen 
                        <italic toggle="yes">et al.</italic>, 2017</xref>) was used for radiomic feature extraction. This software loads DICOM images and region of interest (ROI) from a specific folder on the computer. First, it converts the image and ROI in NRRD format using Plastimatch 1.8.0, subsequently, it extracts radiomic features from the image and finally stores the output in comma separated values (CSV) format in an output folder on the computer. The details of the software are described below (
                    <xref ref-type="fig" rid="f1">Figure 1</xref>).</p>
                <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                    <label>Figure 1. </label>
                    <caption>
                        <title>The batch process of radiomics features extraction from our tool.</title>
                        <p>The user has to select the input folder containing the Digital Imaging and Communications in Medicine (DICOM) image and radiotherapy (RT) structure files. We can select the output folder and also customize the feature extraction process by changing values in the &#x2018;.yaml&#x2019; file.</p>
                    </caption>
                    <graphic id="gr1" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142538/826a7374-8237-4980-b486-6a044110f3ea_figure1.gif"/>
                </fig>
                <p>To start PyRadGUI, GUI_batch_radiomics.py is run on the command prompt. GUI, shown in 
                    <xref ref-type="fig" rid="f2">Figure 2</xref>, has been divided into two parts, i.e., left and right containers. The left container contains three tabs that are used for customization and radiomic extraction and the right container displays the process and error if any.</p>
                <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                    <label>Figure 2. </label>
                    <caption>
                        <title>The figure shows the graphical user interface (GUI) of the radiomic extraction module (A) and customization window (B).</title>
                    </caption>
                    <graphic id="gr2" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142538/826a7374-8237-4980-b486-6a044110f3ea_figure2.gif"/>
                </fig>
                <p>After starting the program, the user must select an input folder containing multiple patient images and a Radio therapy (RT) structure in DICOM format. Next, the user must select an output folder and then change the feature extraction settings from the settings tab.</p>
            </sec>
            <sec id="sec5">
                <title>Steps involved in customization settings</title>
                <p>
                    <list list-type="order">
                        <list-item>
                            <label>1.</label>
                            <p>Selection of image type (Original, Laplace of Gaussian, and Wavelet): To extract features on the original image, we can select the image type as the original. If feature extraction has to be done on the transformed image, then we can select either LoG (Laplace of Gaussian) or Wavelet or both.</p>
                        </list-item>
                        <list-item>
                            <label>2.</label>
                            <p>Selection of feature types: We have to specify the type of features we want to extract. The default includes all 1093 features from all image types.</p>
                        </list-item>
                        <list-item>
                            <label>3.</label>
                            <p>Bin width selection: In the customization window one can select bin width as per the user requirement and the default bin width is 25. We have used 25 bin widths for CT and MRI and 0.5 bin width for PET radiomic extraction.</p>
                        </list-item>
                        <list-item>
                            <label>4.</label>
                            <p>Sigma value for LoG features: In the customization window one can select the sigma value for LoG features. We have selected default 1-, 2-, and 3-mm sigma values for radiomic feature extraction.</p>
                        </list-item>
                        <list-item>
                            <label>5.</label>
                            <p>Selection of resampled pixel spacing: In the customization window one can select pixel spacing as desired by the user for radiomic extraction. We have used the default 2&#x00d7;2&#x00d7;2 cubic mm pixel spacing.</p>
                        </list-item>
                    </list>
                </p>
                <p>After the settings have been customized, radiomics extraction can be started by clicking on the radiomics extraction button. The batch extraction starts by loading the DICOM folder and calls plastimatch. Plastimatch takes the reference CT folder and converts the input DICOM to NRRD (nearly raw raster data) format. It converts the image to image.nrrd and mask to mask.nrrd. Pyradiomics takes the converted nrrd image, nrrd mask, and the settings specified by the user and then extracts the radiomics features and writes the output in CSV format in the selected output folder. In this output, CSV file columns represent radiomic features and rows represent individual patients. The first column of the file is the patient identification number. This CSV file can be used for various analyses. Status of the running of the process, success, failures, and error reports are displayed in the right container in GUI, and processing reports are stored in the output folder as log files.</p>
            </sec>
            <sec id="sec6">
                <title>System requirements</title>
                <p>We have developed and tested our software on two computer systems (machines) using various software packages. The details of system information and software packages are shown in 
                    <xref ref-type="table" rid="T1">Table 1</xref>.</p>
                <table-wrap id="T1" orientation="portrait" position="float">
                    <label>Table 1. </label>
                    <caption>
                        <title>Computer configuration and packages used for this study.</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">Machine 1</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Machine 2</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>
                                        <styled-content style="#202122" style-type="color">Processor</styled-content>
                                    </bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">Intel i7 10</styled-content>
                                    <sup>
                                        <styled-content style="#202122" style-type="color">th</styled-content>
                                    </sup> 
                                    <styled-content style="#202122" style-type="color">generation, 3.6 GHz</styled-content>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">Intel Xeon E3-1220, 3.0 GHz</styled-content>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>
                                        <styled-content style="#202122" style-type="color">Operating system</styled-content>
                                    </bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">Windows 10, 64 bits</styled-content>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">Windows Server 2008 R2, 64 bits</styled-content>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>
                                        <styled-content style="#202122" style-type="color">RAM</styled-content>
                                    </bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">8 GB</styled-content>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">8 GB</styled-content>
                                </td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <bold>
                                        <styled-content style="#202122" style-type="color">Software packages</styled-content>
                                    </bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">Plastimatch 1.8.0</styled-content>
                                    <break/>
                                    <styled-content style="#202122" style-type="color">Pyradiomics 3.0</styled-content>
                                    <break/>
                                    <styled-content style="#202122" style-type="color">Python 3.6.5</styled-content>
                                    <break/>
                                    <styled-content style="#202122" style-type="color">Python tkinter 8.6</styled-content>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">
                                    <styled-content style="#202122" style-type="color">Plastimatch 1.8.0</styled-content>
                                    <break/>
                                    <styled-content style="#202122" style-type="color">Pyradiomics 3.0</styled-content>
                                    <break/>
                                    <styled-content style="#202122" style-type="color">Python 3.6.5</styled-content>
                                    <break/>
                                    <styled-content style="#202122" style-type="color">Python tkinter 8.6</styled-content>
                                </td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
            <sec id="sec7">
                <title>Patient cohort</title>
                <p>In total 50 non-small cell lung carcinomas (NSCLC) patients&#x2019; PET/CT data with delineation and 20 chondrosarcoma patients&#x2019; MRI data with delineation who were imaged between 2014 to 2017 were used for validation and performance testing of this software. The patient&#x2019;s demographic data is shown in 
                    <xref ref-type="table" rid="T2">Table 2</xref>. Images from 100 NSLC patients were utilized to test the batch processing.</p>
                <table-wrap id="T2" orientation="portrait" position="float">
                    <label>Table 2. </label>
                    <caption>
                        <title>Demographic data of patients used in this study.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Disease</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Sex</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Total no.</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Median age</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Image type</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="top">
                                    <bold>NSCLC</bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Male</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">84</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">66</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">CT &amp; WBPET</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Female</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">16</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">53</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">CT &amp; WBPET</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="top">
                                    <bold>Chondrosarcoma</bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Male</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">17</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">46</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">MRI regional</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Female</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">3</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">42</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">MRI regional</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
            <sec id="sec8">
                <title>Software validation</title>
                <p>Software validation was performed by comparing Radiomic feature value extracted using PyRadGUI Workflow (PrGW) and the two reference workflows i.e., Reference Workflow1(RW1) (3DSlicer +Pyradiomics) and Workflow2 (RW2) (Plastimatch +Pyradiomics). The same version of the Pyradiomic package and Plastimatch was used for all the workflows. For the comparison, CT imaging data from 10 patients, PET imaging data from five patients, and MRI imaging data from five patients were all employed. PyRadGUI validation algorithm workflows are shown in 
                    <xref ref-type="fig" rid="f3">Figure 3</xref>.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>Figure 3. </label>
                    <caption>
                        <title>The figure shows the PyRadGUI workflow (PrGW) validation using PyRadiomic Reference Workflow1(RW1) and Reference Workflow2 (RW2) for radiomic extraction.</title>
                    </caption>
                    <graphic id="gr3" orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/142538/826a7374-8237-4980-b486-6a044110f3ea_figure3.gif"/>
                </fig>
                <p>
                    <bold>Reference Workflow1 (RW1):</bold> Individual patient&#x2019;s DICOM image and ROI were loaded in 
                    <ext-link ext-link-type="uri" xlink:href="https://www.slicer.org/wiki/Slicer_3.0_User_Information">3D slicer 3.0</ext-link>. The first appropriateness of tumor delineation was checked by an experienced imaging physicist (15 years of experience). Image and ROI were converted in NRRD format and the image was saved as an 
                    <italic toggle="yes">image.nrrd</italic> and ROI as 
                    <italic toggle="yes">label.nrrd</italic> in the patient's image folder. Again, the NRRD image and label were loaded in 3D Slicer, and appropriateness on tumor delineation was checked by the same physicist. Subsequently, the radiomic feature was extracted and saved in CSV format using the pyradiomic package on the command prompt. The same process was repeated for all 20 patients&#x2019; data.</p>
                <p>
                    <bold>Reference Workflow2 (RW2):</bold> DICOM image and RTStructure were converted in NRRD format using Plastimatch 1.8.0 and stored similarly as it is done in Workflow1. Subsequently, radiomic features were extracted and stored in CSV format similarly as it is done in workflow1. The algorithm used for the manual extraction of radiomic features is shown in 
                    <xref ref-type="fig" rid="f3">Figure 3</xref>. All the patient&#x2019;s radiomic feature data was arranged similarly as it was arranged in the automated extraction of radiomic feature data as described in the automatic extraction section.</p>
            </sec>
            <sec id="sec9">
                <title>Statistical analysis</title>
                <p>Our PyRadGUI workflow was compared with manual Reference Workflow1 and Reference Workflow2 as shown in 
                    <xref ref-type="fig" rid="f3">Figure 3</xref>. Interclass correlation (ICC) was calculated for all 1093 radiomic features to compare PyRadGUI workflow and Reference Workflow1 using python code. As we were expecting the same result in PyRadGUI Workflow and Reference Workflow2, we used the EXACT function of 
                    <ext-link ext-link-type="uri" xlink:href="https://www.microsoft.com/en-us/microsoft-365/excel">Microsoft Excel</ext-link> 2007 software to compare both the data sets. The EXACT function compares two strings for all the characters, if all the characters are the same in both the strings it gives true as an output otherwise false.</p>
            </sec>
            <sec id="sec10">
                <title>Performance testing of software</title>
                <p>The performance of the software was tested for batch processing on the two machines mentioned in 
                    <xref ref-type="table" rid="T1">Table 1</xref>. CT and PET DICOM data were used in the batches of 10, 20, 50, and MRI DICOM data were used in the batches of 10, and 20. The total time required for individual batch processing was recorded.</p>
            </sec>
        </sec>
        <sec id="sec11" sec-type="results">
            <title>Results</title>
            <p>We successfully installed and ran the software on the two computers mentioned in 
                <xref ref-type="table" rid="T1">Table 1</xref>. All the customizations for radiomic extraction work well on multiple trials. With this software, we were able to perform radiomic extraction by batch processing of up to 100 patients&#x2019; CT data on both computers.</p>
            <sec id="sec12">
                <title>Software validation</title>
                <p>The ICC value for the comparison of PrGW and RW1 was ICC =0.978 (range: 0.9612-1.0) across all the modalities. The ICC value for the comparison of PrGW and RW1 is shown in 
                    <xref ref-type="table" rid="T3">Table 3</xref>. All the values (for 1093 radiomic features) in the validation steps for CT, PET, and MRI features for PrGW and RW2 were TRUE, which shows that we were able to extract the same values for all the features for the same data across all the modalities by using this software as confirmed by the manual process.</p>
                <table-wrap id="T3" orientation="portrait" position="float">
                    <label>Table 3. </label>
                    <caption>
                        <title>The table shows the interclass correlation (ICC) value between PrGW and RW1 for CT, PET, and MRI radiomic feature extraction.</title>
                    </caption>
                    <table content-type="article-table" frame="hsides">
                        <thead>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Comparison</th>
                                <th align="left" colspan="3" rowspan="1" valign="top">ICC value (Mean&#x00b1;SD)</th>
                            </tr>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">1093 features</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">CT [10patients]</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">PET [5patients]</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">MRI [5patients]</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">PrGW vs. RW1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.98&#x00b1;0.06</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.72&#x00b1;0.31</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.84&#x00b1;0.23</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">PrGW vs. RW2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.94&#x00b1;0.08</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.74&#x00b1;0.52</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">0.82&#x00b1;0.74</td>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
            <sec id="sec13">
                <title>Performance testing of software</title>
                <p>On both machines the batch processing performance was found to be satisfactory. The details of run time are shown in 
                    <xref ref-type="table" rid="T4">Table 4</xref>. Various imaging modalities were used to test the PyRadGUI tool.</p>
                <table-wrap id="T4" orientation="portrait" position="float">
                    <label>Table 4. </label>
                    <caption>
                        <title>Shows the processing time required by both Machines for batch processing of radiomic extraction.</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"/>
                                <th align="left" colspan="3" rowspan="1" valign="top">Avg. Runtime per patient (sec)</th>
                            </tr>
                            <tr>
                                <th align="left" colspan="1" rowspan="1" valign="top">Modality</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">Computer system</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">A batch of 10 patient</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">A batch of 20 patient</th>
                                <th align="left" colspan="1" rowspan="1" valign="top">A batch of 50 patient</th>
                            </tr>
                        </thead>
                        <tbody>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="top">
                                    <bold>CT</bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Machine 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">81</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">53</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">75</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Machine 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">58</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">30</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">31</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="top">
                                    <bold>PET</bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Machine 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">180</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">190</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">180</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Machine 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">102</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">159</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">112</td>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="2" valign="top">
                                    <bold>MRI</bold>
                                </td>
                                <td align="left" colspan="1" rowspan="1" valign="top">Machine 1</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">75</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">94</td>
                                <td colspan="1" rowspan="1"/>
                            </tr>
                            <tr>
                                <td align="left" colspan="1" rowspan="1" valign="top">Machine 2</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">7</td>
                                <td align="left" colspan="1" rowspan="1" valign="top">7</td>
                                <td colspan="1" rowspan="1"/>
                            </tr>
                        </tbody>
                    </table>
                </table-wrap>
            </sec>
        </sec>
        <sec id="sec14" sec-type="discussion">
            <title>Discussion</title>
            <p>Several licensed and open-source software are available for radiomic extraction, which can extract radiomic features from two- or three-dimensional medical images (
                <xref ref-type="bibr" rid="ref10">Gotz 
                    <italic toggle="yes">et al.</italic>, 2019</xref>; 
                <xref ref-type="bibr" rid="ref21">Szczypinski 
                    <italic toggle="yes">et al.</italic>, 2009</xref>; 
                <xref ref-type="bibr" rid="ref23">Zhang 
                    <italic toggle="yes">et al.</italic>, 2015</xref>; 
                <xref ref-type="bibr" rid="ref3">Apte 
                    <italic toggle="yes">et al.</italic>, 2018</xref>).</p>
            <p>
                <xref ref-type="bibr" rid="ref19">Shi 
                    <italic toggle="yes">et al.</italic> (2019)</xref> have developed an Ontology-guided radiomics analysis workflow (O-RAW) using the Pyradiomics package and SITK Python package, which is also able to extract radiomics features from DICOM images and RTSTRUCT in batch processing and store it in resource description framework (RDF) triple store. Another radiomic extraction software, TexRAD, is a licensed package GUI-based system. It has been used by many researchers for radiomic extraction. TexRAD is unable to do the batch processing and it can handle one patient&#x2019;s data at a time (
                <xref ref-type="bibr" rid="ref10">Gotz 
                    <italic toggle="yes">et al.</italic>, 2019</xref>). This software has capabilities to display and review the image and delineate tumors manually, but another drawback of this software is its inability to use existing delineation (RTStructure) (
                <xref ref-type="bibr" rid="ref8">Ganeshan 
                    <italic toggle="yes">et al.</italic>, 2008</xref>; 
                <xref ref-type="bibr" rid="ref6">Davnall 
                    <italic toggle="yes">et al.</italic>, 2012</xref>).</p>
            <p>The RaCaT is radiomic software that implemented the IBSI defined feature but is not available as a GUI tool as well as unable to perform batch processing. The PyRadGUI software is a GUI-based tool and it can implement batch processing of DICOM images and RT structure for radiomic extraction. As this software is an extension of the pyradiomic package it inherently implements the IBSI feature definition. It can extract radiomic features from hundreds of patients&#x2019; images and RTStructure in batch processing mode and store the result in CSV format. Although we have not compared the delineation converted to NRRD using Plastimatch and 3D Slicer, radiomic feature values comparison show excellent agreement (ICC=0.998&#x00b1;0.012) between the two methods. As our results show, this software calculates radiomics features accurately and reliably. Radiomic extraction from PET and CT images takes a much longer time compared to MRI images, as PET and CT have whole-body images [contains more data] and MRI has regional images [contains less data]. We have used Pyradiomics, open-source software for radiomic extraction in our research infrastructure because this infrastructure can easily be replicated in other research centers. This software works as a plug-in and has no dependencies on the pyradiomic package version, it can be upgraded as and when a new pyradiomic package is available. Customization is the unique feature of this software, which provides flexibility to the user to customize the parameters in the &#x2018;yaml&#x2019; file of the pyradiomics package. The ability of our software to customize and extract 1093 radiomic features from medical images in batch processing enables faster processing of radiomic extraction and storage of feature values in CSV format. During the customization, the user can also select a specific group of features to be extracted. The advantage of this software is its GUI and GUI-based customization of extraction, which allows performing the entire task from the GUI console by clicking the available buttons on the console. The CSV format in which this software stores data where each column represents radiomic features and rows represent individual patient&#x2019;s data makes it easier to be utilized for machine learning. It can also be concatenated with clinical data if required. Log files can be used for identifying any error that occurs during the processing. We can identify the specific data that contains errors and then take corrective action by referring to the error log of each patient's data that is generated and stored in log file. In our existing project, we have also developed artificial intelligence (AI) infrastructure for AI-based research in oncology and PyRadGUI is also an integral part of it. The PyRadGUI can be implemented as standalone as well as part of AI infrastructure for radiomic based research. The portability and easy installation of this software will encourage the radiomic community to use this software and this software can be a valuable addition to radiomic based research infrastructure.</p>
            <p>There are also a few limitations of this software like it is unable to display the image before or during the procedure. It requires a DICOM image as well as structure for radiomic processing. Future work will be to test this software on 
                <italic toggle="yes">Linux operating system</italic>, add a statistical and prediction analytics module and image segmentation and display module to this tool.</p>
        </sec>
        <sec id="sec15" sec-type="conclusion">
            <title>Conclusion</title>
            <p>We successfully implemented and validated, PyRadGUI, a GUI-based easy-to-use Radiomic extraction software. This software can easily be implemented on Windows systems. The extracted features using this software are meeting the IBSI standards. We have found this software able to perform batch processing of up to 100 patients and extract radiomic features and store it in ready-to-use CSV format for machine learning. Documentation including the description of how to install and use this software can be found on GitHub (
                <ext-link ext-link-type="uri" xlink:href="https://github.com/Bionic-TMH/PyRadGUI">https://github.com/Bionic-TMH/PyRadGUI</ext-link>).</p>
        </sec>
    </body>
    <back>
        <sec id="sec19" sec-type="data-availability">
            <title>Data availability</title>
            <p>The corresponding author has access to the data created and used in this study for verification. Data sharing on a public repository is prohibited by IRB permission. Only the project partners are permitted to access the data due to confidentiality reasons regarding patient data.</p>
        </sec>
        <sec id="sec16">
            <title>Software availability</title>
            <p>Source code available from: 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/Bionic-TMH/PyRadGUI">https://github.com/Bionic-TMH/PyRadGUI</ext-link>
            </p>
            <p>Archived source code at time of publication: 
                <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.7524822">https://doi.org/10.5281/zenodo.7524822</ext-link>
            </p>
            <p>License: 
                <ext-link ext-link-type="uri" xlink:href="https://opensource.org/licenses/Apache-2.0">Apache License 2.0</ext-link>
            </p>
        </sec>
        <ack>
            <title>Acknowledgement</title>
            <p>The authors wish to thank The Netherlands Enterprise Agency (RVO) and MeITy for the Indo-Dutch NWO/MeITy BIONIC and TRAIN project.</p>
        </ack>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Aerts</surname>
                            <given-names>HJ</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Velazquez</surname>
                            <given-names>ER</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Leijenaar</surname>
                            <given-names>RT</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Decoding tumour phenotype by noninvasive imaging using a quantitative radiomics approach.</article-title>
                    <source>

                        <italic toggle="yes">Nat. Commun.</italic>
</source>
                    <year>2014 Jun 3</year>;<volume>5</volume>:<fpage>4006</fpage>. Erratum in: Nat Commun. 2014;5:4644. Cavalho, Sara [corrected to Carvalho, Sara].
                    <pub-id pub-id-type="pmid">24892406</pub-id>
                    <pub-id pub-id-type="doi">10.1038/ncomms5006</pub-id>
                    <pub-id pub-id-type="pmcid">PMC4059926</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Agyeman</surname>
                            <given-names>AA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Ofori-Asenso</surname>
                            <given-names>R</given-names>
                        </name>
</person-group>:
                    <article-title>Perspective: Does personalized medicine hold the future for medicine?</article-title>
                    <source>

                        <italic toggle="yes">J. Pharm. Bioallied Sci.</italic>
</source>
                    <year>2015 Jul-Sep</year>;<volume>7</volume>(<issue>3</issue>):<fpage>239</fpage>&#x2013;<lpage>244</lpage>.
                    <pub-id pub-id-type="pmid">26229361</pub-id>
                    <pub-id pub-id-type="doi">10.4103/0975-7406.160040</pub-id>
                    <pub-id pub-id-type="pmcid">PMC4517329</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Apte</surname>
                            <given-names>AP</given-names>
                        </name>

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

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

                        <etal/>
</person-group>:
                    <article-title>Extension of CERR for computational radiomics: a comprehensive MATLAB platform for reproducible radiomics research.</article-title>
                    <source>

                        <italic toggle="yes">Med. Phys.</italic>
</source>
                    <year>2018</year>;<volume>45</volume>:<fpage>3713</fpage>&#x2013;<lpage>3720</lpage>.
                    <pub-id pub-id-type="pmid">29896896</pub-id>
                    <pub-id pub-id-type="doi">10.1002/mp.13046</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6597320</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Caers</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Withofs</surname>
                            <given-names>N</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hillengass</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The role of positron emission tomography-computed tomography and magnetic resonance imaging in diagnosis and follow up of multiple myeloma.</article-title>
                    <source>

                        <italic toggle="yes">Haematologica.</italic>
</source>
                    <year>2014 Apr</year>;<volume>99</volume>(<issue>4</issue>):<fpage>629</fpage>&#x2013;<lpage>637</lpage>.
                    <pub-id pub-id-type="pmid">24688111</pub-id>
                    <pub-id pub-id-type="doi">10.3324/haematol.2013.091918</pub-id>
                    <pub-id pub-id-type="pmcid">PMC3971072</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>Cancer imaging phenomics toolkit: quantitative imaging analytics for precision diagnostics and predictive modeling of clinical outcome.</article-title>
                    <source>

                        <italic toggle="yes">J. Med. Imaging.</italic>
</source>
                    <year>2018</year>;<volume>5</volume>:<fpage>1</fpage>.
                    <pub-id pub-id-type="pmid">29340286</pub-id>
                    <pub-id pub-id-type="doi">10.1117/1.JMI.5.1.011018</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5764116</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref6">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Yip</surname>
                            <given-names>CS</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <article-title>Assessment of tumor heterogeneity: an emerging imaging tool for clinical practice?</article-title>
                    <source>

                        <italic toggle="yes">Insights Imaging.</italic>
</source>
                    <year>2012 Dec</year>;<volume>3</volume>(<issue>6</issue>):<fpage>573</fpage>&#x2013;<lpage>589</lpage>. 2012 Oct 24.
                    <pub-id pub-id-type="pmid">23093486</pub-id>
                    <pub-id pub-id-type="doi">10.1007/s13244-012-0196-6.Epub</pub-id>
                    <pub-id pub-id-type="pmcid">PMC3505569</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Ferlay</surname>
                            <given-names>J</given-names>
                        </name>

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

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

                        <etal/>
</person-group>:
                    <article-title>Estimating the global cancer incidence and mortality in 2018: GLOBOCAN sources and methods.</article-title>
                    <source>

                        <italic toggle="yes">Int. J. Cancer.</italic>
</source>
                    <year>2019 Apr 15</year>;<volume>144</volume>(<issue>8</issue>):<fpage>1941</fpage>&#x2013;<lpage>1953</lpage>.
                    <pub-id pub-id-type="pmid">30350310</pub-id>
                    <pub-id pub-id-type="doi">10.1002/ijc.31937</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref8">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Miles</surname>
                            <given-names>KA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Young</surname>
                            <given-names>RC</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Three-dimensional selective-scale texture analysis of computed tomography pulmonary angiograms.</article-title>
                    <source>

                        <italic toggle="yes">Investig. Radiol.</italic>
</source>
                    <year>2008 Jun</year>;<volume>43</volume>(<issue>6</issue>):<fpage>382</fpage>&#x2013;<lpage>394</lpage>.
                    <pub-id pub-id-type="pmid">18496043</pub-id>
                    <pub-id pub-id-type="doi">10.1097/RLI.0b013e3181690091</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Goodwin</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Neugent</surname>
                            <given-names>ML</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Lee</surname>
                            <given-names>SY</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The distinct metabolic phenotype of lung squamous cell carcinoma defines selective vulnerability to glycolytic inhibition.</article-title>
                    <source>

                        <italic toggle="yes">Nat. Commun.</italic>
</source>
                    <year>2017 May 26</year>;<volume>8</volume>:<fpage>15503</fpage>.
                    <pub-id pub-id-type="pmid">28548087</pub-id>
                    <pub-id pub-id-type="doi">10.1038/ncomms15503</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5458561</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref10">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Maier-Hein</surname>
                            <given-names>K</given-names>
                        </name>
</person-group>:
                    <article-title>MITK Phenotyping: an open-source toolchain for image-based personalized medicine with radiomics.</article-title>
                    <source>

                        <italic toggle="yes">Radiother. Oncol.</italic>
</source>
                    <year>2019</year>;<volume>131</volume>:<fpage>108</fpage>&#x2013;<lpage>111</lpage>.
                    <pub-id pub-id-type="pmid">30773176</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.radonc.2018.11.021</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref11">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Griethuysen</surname>
                            <given-names>JJM</given-names>
                        </name>

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

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

                        <etal/>
</person-group>:
                    <article-title>Computational Radiomics System to Decode the Radiographic Phenotype.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Res.</italic>
</source>
                    <year>2017</year>;<volume>77</volume>(<issue>21</issue>):<fpage>e104</fpage>&#x2013;<lpage>e107</lpage>.
                    <pub-id pub-id-type="pmid">29092951</pub-id>
                    <pub-id pub-id-type="doi">10.1158/0008-5472.CAN-17-0339</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5672828</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref12">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Haider</surname>
                            <given-names>SP</given-names>
                        </name>

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

                        <name name-style="western">
                            <surname>Yarbrough</surname>
                            <given-names>WG</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Applications of radiomics in precision diagnosis, prognostication and treatment planning of head and neck squamous cell carcinomas.</article-title>
                    <source>

                        <italic toggle="yes">Cancers Head Neck.</italic>
</source>
                    <year>2020</year>;<volume>5</volume>:<fpage>6</fpage>.
                    <pub-id pub-id-type="pmid">32391171</pub-id>
                    <pub-id pub-id-type="doi">10.1186/s41199-020-00053-7</pub-id>
                    <pub-id pub-id-type="pmcid">PMC7197186</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Haralick</surname>
                            <given-names>RM</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Shanmugam</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Dinstein</surname>
                            <given-names>I</given-names>
                        </name>
</person-group>:
                    <article-title>Textural Features for Image Classification.</article-title>
                    <source>

                        <italic toggle="yes">IEEE Trans. Syst. Man Cybern.</italic>
</source>
                    <year>1973</year>;<volume>SMC-3</volume>:<fpage>610</fpage>&#x2013;<lpage>621</lpage>.
                    <pub-id pub-id-type="doi">10.1109/TSMC.1973.4309314</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref14">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Johnson</surname>
                            <given-names>MCI</given-names>
                        </name>
</person-group>:
                    <article-title>The ITK Software Guide: Introduction and Development Guidelines. 2015.</article-title>
                    <year>2015</year>.</mixed-citation>
            </ref>
            <ref id="ref15">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>Radiomics: extracting more information from medical images using advanced feature analysis.</article-title>
                    <source>

                        <italic toggle="yes">Eur. J. Cancer.</italic>
</source>
                    <year>2012 Mar</year>;<volume>48</volume>(<issue>4</issue>):<fpage>441</fpage>&#x2013;<lpage>446</lpage>.
                    <pub-id pub-id-type="pmid">22257792</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.ejca.2011.11.036</pub-id>
                    <pub-id pub-id-type="pmcid">PMC4533986</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Limkin</surname>
                            <given-names>EJ</given-names>
                        </name>

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

                        <name name-style="western">
                            <surname>Dercle</surname>
                            <given-names>L</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Promises and challenges for the implementation of computational medical imaging (radiomics) in oncology.</article-title>
                    <source>

                        <italic toggle="yes">Ann. Oncol.</italic>
</source>
                    <year>2017</year>;<volume>28</volume>:<fpage>1191</fpage>&#x2013;<lpage>1206</lpage>.
                    <pub-id pub-id-type="pmid">28168275</pub-id>
                    <pub-id pub-id-type="doi">10.1093/annonc/mdx034</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref17">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>LIFEx: A Freeware for Radiomic Feature Calculation in Multimodality Imaging to Accelerate Advances in the Characterization of Tumor Heterogeneity.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Res.</italic>
</source>
                    <year>2018</year>;<volume>78</volume>:<fpage>4786</fpage>&#x2013;<lpage>4789</lpage>.
                    <pub-id pub-id-type="pmid">29959149</pub-id>
                    <pub-id pub-id-type="doi">10.1158/0008-5472.CAN-18-0125</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref18">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Jong</surname>
                            <given-names>JR</given-names>
                            <prefix>de</prefix>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>RaCaT: An open source and easy to use radiomics calculator tool.</article-title>
                    <source>

                        <italic toggle="yes">PLoS One.</italic>
</source>
                    <year>2019 Feb 20</year>;<volume>14</volume>(<issue>2</issue>):<fpage>e0212223</fpage>.
                    <pub-id pub-id-type="pmid">30785937</pub-id>
                    <pub-id pub-id-type="doi">10.1371/journal.pone.0212223</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6382170</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref19">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Soest</surname>
                            <given-names>J</given-names>
                            <prefix>van</prefix>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Technical Note: Ontology-guided radiomics analysis workflow (O-RAW).</article-title>
                    <source>

                        <italic toggle="yes">Med. Phys.</italic>
</source>
                    <year>2019 Dec</year>;<volume>46</volume>(<issue>12</issue>):<fpage>5677</fpage>&#x2013;<lpage>5684</lpage>.
                    <pub-id pub-id-type="pmid">31580484</pub-id>
                    <pub-id pub-id-type="doi">10.1002/mp.13844</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6916323</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref20">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Stewart</surname>
                            <given-names>CL</given-names>
                        </name>

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

                        <name name-style="western">
                            <surname>Ito</surname>
                            <given-names>K</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Cytoreduction for colorectal metastases: liver, lung, peritoneum, lymph nodes, bone, brain. When does it palliate, prolong survival, and potentially cure?</article-title>
                    <source>

                        <italic toggle="yes">Curr. Probl. Surg.</italic>
</source>
                    <year>2018 Sep</year>;<volume>55</volume>(<issue>9</issue>):<fpage>330</fpage>&#x2013;<lpage>379</lpage>.
                    <pub-id pub-id-type="pmid">30526930</pub-id>
                    <pub-id pub-id-type="doi">10.1067/j.cpsurg.2018.08.004</pub-id>
                    <pub-id pub-id-type="pmcid">PMC6422355</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref21">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Szczypinski</surname>
                            <given-names>PM</given-names>
                        </name>

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

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

                        <etal/>
</person-group>:
                    <article-title>MaZda&#x2014;a software package for image texture analysis.</article-title>
                    <source>

                        <italic toggle="yes">Comput. Methods Prog. Biomed.</italic>
</source>
                    <year>2009</year>;<volume>94</volume>:<fpage>66</fpage>&#x2013;<lpage>76</lpage>.
                    <pub-id pub-id-type="pmid">18922598</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.cmpb.2008.08.005</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref22">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Yip</surname>
                            <given-names>SS</given-names>
                        </name>

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

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

                        <etal/>
</person-group>:
                    <article-title>Associations between radiologist-defined semantic and automatically computed radiomic features in non-small cell lung cancer.</article-title>
                    <source>

                        <italic toggle="yes">Sci. Rep.</italic>
</source>
                    <year>June 2017</year>;<volume>7</volume>(<issue>1</issue>):<fpage>3519</fpage>.
                    <pub-id pub-id-type="pmid">28615677</pub-id>
                    <pub-id pub-id-type="doi">10.1038/s41598-017-02425-5</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5471260</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref23">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Fried</surname>
                            <given-names>DV</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Fave</surname>
                            <given-names>XJ</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>IBEX: an open infrastructure software platform to facilitate collaborative work in radiomics.</article-title>
                    <source>

                        <italic toggle="yes">Med. Phys.</italic>
</source>
                    <year>2015</year>;<volume>42</volume>:<fpage>1341</fpage>&#x2013;<lpage>1353</lpage>.
                    <pub-id pub-id-type="pmid">25735289</pub-id>
                    <pub-id pub-id-type="doi">10.1118/1.4908210</pub-id>
                    <pub-id pub-id-type="pmcid">PMC5148126</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref25">
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zwanenburg</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <article-title>EP-1677: Multicentre initiative for standardisation of image biomarkers.</article-title>
                    <source>

                        <italic toggle="yes">Radiother. Oncol.</italic>
</source>
                    <year>2017</year>;<volume>123</volume>:<fpage>S914</fpage>&#x2013;<lpage>S915</lpage>.
                    <pub-id pub-id-type="doi">10.1016/S0167-8140(17)32209-0</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref26">
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Valli&#x00e8;res</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Initiative for the IBS. Image biomarker standardisation initiative.</article-title>
                    <year>2016</year>;<volume>295</volume>:<fpage>328</fpage>&#x2013;<lpage>338</lpage>.
                    <pub-id pub-id-type="pmid">32154773</pub-id>
                    <pub-id pub-id-type="doi">10.1148/radiol.2020191145</pub-id>
                    <pub-id pub-id-type="pmcid">PMC7193906</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report219099">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.142538.r219099</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Namdar</surname>
                        <given-names>Khashayar</given-names>
                    </name>
                    <xref ref-type="aff" rid="r219099a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-0497-6206</uri>
                </contrib>
                <aff id="r219099a1">
                    <label>1</label>University of Toronto, Toronto, Ontario, Canada</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>22</day>
                <month>11</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Namdar K</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport219099" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.129826.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>The paper has been already reviewed and the current version is in an acceptable stage in terms of writing and structure. As a reviewer, I do not intend to add unnecessary comments. Anything I highlight is for the sake of improving the paper and helping the authors and thus it is open for discussion. Also, the authors are not expected to follow the inefficient tradition of starting every sentence with &#x201c;we thank the reviewer for their helpful comment&#x201d;.</p>
            <p> </p>
            <p> Fundamental comments:</p>
            <p> </p>
            <p> The core of the software is PyRadiomics. As it is mentioned in the manuscript, PyRadiomics is a reliable and popular library for radiomics extraction. Hence, choosing PyRadiomics for the back-end of the software is wise. However, the assumption of &#x201c;PyRadiomics is overcomplicated therefore researchers will use our tool&#x201d; may be superficial. A) this is not a new problem. Cisco routers have been known for their complex terminals and multiple GUI-enabled solutions have been proposed for them. However, still the terminal is the most popular interaction means. Therefore, you need to select your target users and develop the tool for them. B) with LLMs writing advanced scripts, radiomics extraction using PyRadiomics becomes more and more accessible. This is why I do not expect your paper will have many citations. C) As it is mentioned in the manuscript, there are multiple alternatives. The question is not ICC of the extracted features. Those check points are needed, but they are nothing more than sanity checks. The question is &#x201c;why PyRadGUI and not Slicer+PyRadiomics extension?&#x201d; You answered this question partially by highlighting batch processing. You would need more features D) installation of the libraries is always an issue, especially for researchers with limited technical background (which are your target users). Dockerizing the software and selecting a web interface could be a more versatile approach.</p>
            <p> </p>
            <p> Radiomics-based ML pipelines are more comprehensive than radiomics extraction. Authors have tried to include more in the software by adding data-loading. However, this makes the solution project-specific. They should decouple feature extraction so that the software becomes compatible with different settings. What if the starting point is not DICOM files? What if there are no RT Structures? What if NifTi, NRRD, or even 2D JPEG/PNGs are provided?</p>
            <p> </p>
            <p> Technical Considerations: The total number of extracted features can be more than 1093. You may want to read &#x201c;Open-radiomics: A Collection of Standardized Datasets and a Technical Protocol for Reproducible Radiomics Machine Learning Pipelines&#x201d; and check 
                <ext-link ext-link-type="uri" xlink:href="https://openradiomics.org/">https://openradiomics.org/</ext-link>. Please make sure trimesh is installed.</p>
            <p> </p>
            <p> The quality of the figures is low. It seems in Figure 2, Bin Width is misspelled.</p>
            <p> </p>
            <p> Re. &#x201c;To start PyRadGUI, GUI_batch_radiomics.py is run on the command prompt.&#x201d;: A) An executable file could be provided to make the solution more &#x201c;software&#x201d; than a tkinter python script. B) the specific file name is introduced out of the context and when the reader has no knowledge of the script structures. Please start the paragraph with introducing the github repository and the scripts and directory structures and functions.</p>
            <p> </p>
            <p> PyRadiomics has numerous settings and hyperparameters, and you have provided access to several common ones. A) mention what they are why you have decided to choose them B) It would be nice to incorporate an &#x201c;advanced&#x201d; tab for users with more experience</p>
            <p> </p>
            <p> Writing: I would improve the paper is the use of words such as &#x201c;many&#x201d; and &#x201c;several&#x201d; was more controlled. It becomes more important when these words are repeated in the same sentence (e.g. &#x201d; Several open-source and licensed software packages for radiomic extraction, like IBEX, RaCaT, CaPTK, LifeX or CGITA, Pyradiomics, and TexRad have been developed and used by several researchers in the past&#x201d;).</p>
            <p> </p>
            <p> Also, choosing &#x201c;like&#x201d; as a replacement for &#x201c;such as&#x201d; is informal in academic writing.</p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Yes</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Artificial Intelligence, Brain Cancer, Statistics, Neuroscience, MRI</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report211383">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.142538.r211383</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Hosseini</surname>
                        <given-names>Seyyed Ali</given-names>
                    </name>
                    <xref ref-type="aff" rid="r211383a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-7542-7541</uri>
                </contrib>
                <aff id="r211383a1">
                    <label>1</label>McGill University, Montreal, Qu&#x00e9;bec, Canada</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>31</day>
                <month>10</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Hosseini SA</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport211383" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.129826.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>
                <bold>Overall Comments:</bold>
            </p>
            <p> </p>
            <p> The manuscript presents "PyRadGUI," a GUI-based software tool designed to facilitate radiomic feature extraction from medical images. The software aims to address the challenges posed by existing radiomics tools, particularly the lack of user-friendliness and standardization. The authors provide a detailed description of the software's development, features, and validation, along with potential use cases. The manuscript is well-structured, and the software appears promising. However, there are some areas that require further clarification and improvement.</p>
            <p> </p>
            <p> 
                <bold>General Comments:</bold>
            </p>
            <p> </p>
            <p> Clarity and Organization: The manuscript is generally well-organized and clear. However, some sections could benefit from further clarification. For instance, the introduction is lengthy, and while it provides useful background information, it could be more concise. It's essential to maintain a balance between providing context and keeping the reader engaged.</p>
            <p> </p>
            <p> Abstract: The abstract effectively summarizes the key points of the manuscript. However, it would be helpful to include specific results or findings from the study, as this would give readers a quick overview of the software's performance.</p>
            <p> </p>
            <p> Keywords: The chosen keywords are appropriate and relevant to the topic.</p>
            <p> </p>
            <p> Ethical Considerations: The authors mention ethical approval for their study but do not provide any information regarding patient consent or data privacy. It would be beneficial to clarify how patient data were handled, especially regarding privacy and consent, as this is an essential ethical aspect of medical research.</p>
            <p> </p>
            <p> Software Availability: The manuscript mentions the availability of the software on GitHub and provides a DOI link. However, it would be helpful to include a brief section in the manuscript explaining how readers can access and use the software.</p>
            <p> </p>
            <p> 
                <bold>Specific Comments:</bold>
            </p>
            <p> </p>
            <p> Introduction: The introduction provides a comprehensive overview of radiomics and its significance. However, it could be condensed to maintain reader engagement. Also, it would be useful to include a clear statement of the study's objectives and the problem the software aims to address.</p>
            <p> </p>
            <p> Methods: The methods section is detailed and provides a good understanding of how the software was developed and tested. However, there are several grammatical errors and awkward sentences throughout this section that need editing. For example, "Although we have not compared the delineation converted to NRRD using Plastimatch and 3D Slicer, radiomic feature values comparison show excellent agreement (ICC=0.998&#x00b1;0.012) between the two methods." This sentence needs clarification.</p>
            <p> </p>
            <p> Results: The results section provides valuable information regarding software validation and performance testing. However, it could be enhanced by presenting the results in a more organized and visually appealing manner, such as tables or figures.</p>
            <p> </p>
            <p> Discussion: The discussion section effectively highlights the advantages of PyRadGUI and its potential applications. It would be beneficial to address the limitations and future improvements in more detail. For instance, the authors mention future work to add statistical and prediction analytics modules and image segmentation and display modules, but elaborating on these points would provide more insight.</p>
            <p> </p>
            <p> Conclusion: The conclusion appropriately summarizes the key findings and contributions of the study. However, it would be helpful to reiterate the software's main advantages briefly.</p>
            <p> </p>
            <p> Figures and Tables: Figures and tables are crucial for presenting results and data. Consider adding more visual elements to help readers grasp the key points more easily.</p>
            <p> </p>
            <p> Language and Grammar: The manuscript contains numerous grammatical errors and awkward sentences. Careful editing and proofreading are necessary to improve readability.</p>
            <p> </p>
            <p> Software Citation: Encourage authors to cite the software appropriately in their publications, as this is important for acknowledging the work of software developers.</p>
            <p> </p>
            <p> Software Accessibility: Provide clear instructions on how to access and use the software. This should include information on system requirements, installation, and a brief tutorial if possible.</p>
            <p> </p>
            <p> In summary, the manuscript presents a promising software tool for radiomics, but it requires editing for clarity, grammar, and organization. Additionally, providing more information on ethical considerations and access to the software would enhance the manuscript's completeness.</p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Yes</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Machine/Deep Learning Quantitative Imaging Radio/Genomics Neuroscience Radiomics</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report211376">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.142538.r211376</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Le</surname>
                        <given-names>Nguyen Quoc Khanh</given-names>
                    </name>
                    <xref ref-type="aff" rid="r211376a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-4896-7926</uri>
                </contrib>
                <aff id="r211376a1">
                    <label>1</label>Taipei Medical University Digital Library Consortium, Taipei City, Taipei City, Taiwan</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>31</day>
                <month>10</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Le NQK</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport211376" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.129826.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>1. The authors compared radiomic feature values between different software tools. However, they lacked specific details on the metrics used for this comparison. The readers would benefit from knowing the statistical methods employed and the criteria for determining "excellent agreement" (e.g., ICC=0.998&#x00b1;0.012).</p>
            <p> </p>
            <p> 2. The software limitations mentioned, such as the inability to display images before or during the procedure, may be crucial for users. Elaborating on these limitations and their potential impact on the usability and applicability of the software is necessary.</p>
            <p> </p>
            <p> 3. The use of a DICOM image as well as structure for radiomic processing raises concerns about the software's flexibility. A discussion on the potential limitations imposed by this requirement and the implications for users dealing with non-DICOM data should be included.</p>
            <p> </p>
            <p> 4. The intention to test the software on a Linux operating system is mentioned as future work. It would be helpful to provide insights into the challenges and considerations involved in adapting the software to different operating systems, as this can significantly impact its accessibility.</p>
            <p> </p>
            <p> 5. The authors should provide more details on the specific functionalities and capabilities of statistical and prediction analytics module.</p>
            <p> </p>
            <p> 6. Similarly, the mention of adding an image segmentation and display module is a significant enhancement. The authors should discuss the rationale behind this addition and its potential impact on the software's utility.</p>
            <p> </p>
            <p> 7. While the software is mentioned as a valuable addition to radiomic-based research infrastructure and as part of an AI infrastructure, more details on how PyRadGUI integrates with AI models, its compatibility with different machine learning frameworks, and examples of successful integration with AI-based projects would strengthen the study.</p>
            <p> </p>
            <p> 8. The study could benefit from insights into the user experience, including user feedback, challenges faced during implementation, and any user training required.</p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Partly</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Partly</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Partly</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Radiomics; artificial intelligence</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
    </sub-article>
</article>
