<?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.51916.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>CytoBrowser: a browser-based collaborative annotation platform for whole slide images</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 1 approved with reservations, 1 not approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Rydell</surname>
                        <given-names>Christopher</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-3855-8734</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Lindblad</surname>
                        <given-names>Joakim</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/">Funding Acquisition</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Resources</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Validation</role>
                    <role content-type="http://credit.niso.org/">Visualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-7312-8222</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>MIDA Group, Department of Information Technology, Uppsala University, Uppsala, 751 05, Sweden</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:joakim@cb.uu.se">joakim@cb.uu.se</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>22</day>
                <month>3</month>
                <year>2021</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2021</year>
            </pub-date>
            <volume>10</volume>
            <elocation-id>226</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>11</day>
                    <month>3</month>
                    <year>2021</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2021 Rydell C and Lindblad J</copyright-statement>
                <copyright-year>2021</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/10-226/pdf"/>
            <abstract>
                <p>We present CytoBrowser, an open-source (GPLv3) JavaScript and Node.js driven environment for fast and accessible collaborative online visualization, assessment, and annotation of very large microscopy images, including, but not limited to, z-stacks (focus stacks) of cytology or histology whole slide images. CytoBrowser provides a web-based viewer for high-resolution zoomable images and facilitates easy remote collaboration, with options for joint-view visualization and simultaneous collaborative annotation of very large datasets. It delivers a unique combination of functionalities not found in other software solutions, making it a preferred tool for large scale annotation of whole slide image data. The web browser interface is directly accessible on any modern computer or even on a mobile phone, without need for additional software. By sharing a &#x201c;session&#x201d;, several remote users can interactively explore and jointly annotate whole slide image data, thereby reaching improved data understanding and annotation quality, effortless project scaling and distribution of resources to/from remote locations, efficient creation of &#x201c;ground truth&#x201d; annotations for methods&#x2019; evaluation and training of machine learning-based approaches, a user-friendly learning environment for medical students, to just name a few. Rectangle and polygon region annotations complement point-based annotations, each with a selectable annotation-class as well as free-form text fields. The default setting of CytoBrowser presents an interface for the Bethesda cancer grading system, while other annotation schemes can easily be incorporated. Automatic server side storage of annotations is complemented by JSON-based import/export options facilitating easy interoperability with other tools. CytoBrowser is available here: 
                    <ext-link ext-link-type="uri" xlink:href="https://mida-group.github.io/CytoBrowser/">https://mida-group.github.io/CytoBrowser/</ext-link>.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>virtual microscopy</kwd>
                <kwd>digital cytology</kwd>
                <kwd>whole slide image</kwd>
                <kwd>annotation</kwd>
                <kwd>assessment</kwd>
                <kwd>visualization</kwd>
                <kwd>bioimage informatics</kwd>
                <kwd>JavaScript</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1">
                    <funding-source>Sweden&#x2019;s Innovation Agency, VINNOVA</funding-source>
                    <award-id>2017-02447</award-id>
                    <award-id>2020-03611</award-id>
                </award-group>
                <funding-statement>The project is financially supported by Sweden&#x2019;s Innovation Agency, VINNOVA, through grants 2017-02447 and 2020-03611.</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 sec-type="intro">
            <title>Introduction</title>
            <p>The acquisition and use of whole-slide images (WSIs) is rapidly growing in research and medical practice
                <sup>
                    <xref ref-type="bibr" rid="ref-1">1</xref>,
                    <xref ref-type="bibr" rid="ref-2">2</xref>
                </sup>. The use of WSIs is often referred to as 
                <italic toggle="yes">virtual microscopy</italic>, due to the appealing ability to digitally recreate the microscopy experience. WSIs are produced by high-resolution scanning of entire microscopy glass slides. The resulting images are often larger than 100,000 
                <italic toggle="yes">&#x00d7;</italic> 100,000 pixels and many gigabytes in size; one single image of a cytological or histological specimen may contain more than 100,000 cells. The ability to inspect and annotate WSIs and therefrom derive results has become a crucial component of many bioimage analysis workflows and is also making headway into modern clinical practice. The sheer size of WSI data, where a single image may be larger than the available RAM memory of a standard workstation, is problematic for many standard visualization tools, imposing a need for specialized software solutions.</p>
            <p>There is lately a strong desire within the scientific community towards increased use of open and collaborative solutions and the development of open-source software (OSS)
                <sup>
                    <xref ref-type="bibr" rid="ref-3">3</xref>
                </sup>. A strong argument for the open philosophy is that it efficiently reduces the risk for vendor lock-in situations, where a customer using a proprietary product or service cannot easily transition to another technology due to incompatibilities, inefficient processes, or contract constraints.</p>
            <p>A variety of OSS project that support WSIs exist, examples include caMicroscope
                <sup>
                    <xref ref-type="bibr" rid="ref-4">4</xref>
                </sup>, Digital Slide Archive
                <sup>
                    <xref ref-type="bibr" rid="ref-5">5</xref>
                </sup>, Sedeen viewer
                <sup>
                    <xref ref-type="bibr" rid="ref-6">6</xref>
                </sup>, TissUUmaps
                <sup>
                    <xref ref-type="bibr" rid="ref-7">7</xref>
                </sup>, Cytomine
                <sup>
                    <xref ref-type="bibr" rid="ref-8">8</xref>
                </sup>, OMERO
                <sup>
                    <xref ref-type="bibr" rid="ref-9">9</xref>
                </sup>, and QuPath
                <sup>
                    <xref ref-type="bibr" rid="ref-10">10</xref>
                </sup>. The vast majority of existing WSI tools are developed with histology in mind, whereas cytology is only recently gaining increased attention.</p>
            <p>One specificity of cytopathological analysis, as compared to tissue based histopathological analysis, is the need for several focus levels. Where a tissue sample provides a reasonably flat surface, cells of a cytological sample are distributed in a layer of a certain thickness, from a few micrometers for a liquid-based sample, up to several tens of micrometers for a smear. The depth of field of a high resolution light microscope is often below 1 &#x00b5;m, and microscopic analysis of cytological specimen typically involves adjusting focus individually for each cell. A skilled cytopathologist utilizes the limited depth of focus as a way to separate overlapping cells and also to get a 3D feeling of the sample. To accommodate this property in virtual microscopy, it is common to acquire several focal layers of a specimen and create a so called z-stack. Several studies have examined the importance of z-stacking for whole slide imaging; Hanna 
                <italic toggle="yes">et al.</italic>,
                <sup>
                    <xref ref-type="bibr" rid="ref-11">11</xref>
                </sup> conclude that z-stacks offer a superior mechanism for overcoming focusing problems encountered with digital cytology slides, while Lu 
                <italic toggle="yes">et al.</italic>,
                <sup>
                    <xref ref-type="bibr" rid="ref-12">12</xref>
                </sup> demonstrated that even such a small deviation from the in-focus plane as 0.8 &#x00b5;m may have a clear negative impact on deep learning-based classification performance. Visual assessment of scanned samples requires easy interactive inspection at multiple resolutions and focus levels, but only very few of the above mentioned OSS solutions offer smooth and fast handling of z-stacks, where changing focus is as easy as in a light microscope.</p>
            <p>A great benefit of virtual microscopy over optical microscopy is the possibilities for sharing and collaboration. Digitized WSIs can be made accessible via the Internet, thereby enabling efficient usage of distributed resources and reaching remote parts of the world. Tools for interactive visualization and collaborative assessment of WSIs facilitate improved understanding as well as increased quality of analysis, where several experts may share experiences. Collaborative tools for WSI annotations are also gaining popularity in medical education; in a mixed methods trial
                <sup>
                    <xref ref-type="bibr" rid="ref-13">13</xref>
                </sup> it was found that collaborative WSI annotation provided superior understanding of key microscopic features by senior medical students as compared to individual WSI annotation.</p>
            <p>Despite the growing number of tools for WSI visualization and annotation, we find that there is a lack of light-weight, easy to use OSS tools which are well suited for collaborative annotation of cytological data. The majority of existing tools are directed towards histopathology, with different needs and requirements. Aiming to gather the experience and knowledge of experts from all over the globe, an easy to use, browser-based solution, which may be directly utilized on any computer or tablet without need for software installation, is highly desired. The ability for several users to simultaneously view and comment the same sample improves understanding and analysis quality. The CytoBrowser software, presented here, aims to meet all of these needs and desires. It delivers easy and flexible access to WSIs through a browser-based interface, see 
                <xref ref-type="fig" rid="f1">Figure 1</xref> for an example view. CytoBrowser aims to well replicate the optical microscope feeling, with good support for z-stacks. A growing set of annotation tools are well suited for cytological data. Efficient collaboration is achieved through shared views, with option to follow the view of another user. Annotations may be added and commented on concurrently by several users. The software, completely in JavaScript and Node.js, is light-weight and very easy to install and run. CytoBrowser is typically hosted as a web service, but may also be used locally. We share the source code of CytoBrowser openly and freely under the GNU General Public License v3.0, with the hope that a growing community of users will jointly contribute to its further improvement.</p>
            <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                <label>Figure 1. </label>
                <caption>
                    <title>Example of typical usage &#x2013; annotation of a brightfield WSI in a standard web browser.</title>
                    <p>The user has just placed a marker on a cell nucleus, indicating the Bethesda grade HSIL (High-grade squamous intraepithelial lesion). An overview of the WSI is presented in the lower left part of the screen, with the current zoomed-in viewport indicated as a small red rectangle.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/55127/8e72d789-1e79-4df4-b9e4-a04ae6b3618c_figure1.gif"/>
            </fig>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <p>CytoBrowser is a fork and extension of TissUUmaps
                <sup>
                    <xref ref-type="bibr" rid="ref-7">7</xref>
                </sup> (GPLv3 license), which in turn builds on the OpenSeadragon
                <sup>
                    <xref ref-type="bibr" rid="ref-14">14</xref>
                </sup> (BSD-3-Clause license) web-based viewer for high-resolution zoomable images. Although TissUUmaps is a very capable tool for visualization of cytology WSIs, it is developed with tissue analysis in primary focus and the user interface and tools are not always ideal for cytological data. CytoBrowser instead puts cytological analysis in the main focus. An important feature for cytological data is efficient handling of z-stacks (currently not supported in TissUUmaps); CytoBrowser delivers fast browsing through focus levels by use of transparent layers. CytoBrowser also allows z-level differentiated annotations, useful, e.g., for annotating overlapping cells.</p>
            <p>The development of CytoBrowser is aimed towards ease of use by cytotechnologists and cytopathologists on a global scale. Implemented tools for shared multi-user sessions facilitate efficient remote collaboration, including options for joint-view visualization and collaborative annotation and assessment of very large datasets. CytoBrowser delivers this through a web-browser interface which is functional on any modern computer or tablet, facilitating efficient utilization of distributed resources. A demonstration setup of CytoBrowser running on several devices (Microsoft Edge browser under Windows, Firefox browser under Linux, Chrome browser on Android tablet and phone) is shown in 
                <xref ref-type="fig" rid="f2">Figure 2</xref>. The multi-user design of CytoBrowser offers concurrent access to samples, where different experts may assess, comment on, or edit each others annotations, or where an educator may, e.g., show students different medically relevant examples.</p>
            <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                <label>Figure 2. </label>
                <caption>
                    <title>Demonstration of several users collaboratively annotating a cytology WSI using different devices. </title>
                    <p>The tablet and the laptop in the foreground follow the view displayed on the larger monitor in the background, while the phone is showing a somewhat larger view. The user of the laptop in the foreground is adding a text comment to the upper left marker, while the (followed) user has just placed a HSIL marker on the nucleus in the lower part of the screen. CytoBrowser is compatible with all modern browsers.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/55127/8e72d789-1e79-4df4-b9e4-a04ae6b3618c_figure2.gif"/>
            </fig>
            <sec>
                <title>Implementation</title>
                <p>The frontend of CytoBrowser is implemented in JavaScript. The implementation makes use of the Revealing Module
                    <sup>
                        <xref ref-type="bibr" rid="ref-15">15</xref>
                    </sup> design pattern to clearly separate different parts of functionality and to make it both easily maintainable and expandable. OpenSeadragon
                    <sup>
                        <xref ref-type="bibr" rid="ref-14">14</xref>
                    </sup> is used to display a viewport in the user interface and to dynamically load different parts of the image from the server as needed. The annotations that the user can place on an image belong to one of several annotation classes. By default these classes follow the Bethesda grading system
                    <sup>
                        <xref ref-type="bibr" rid="ref-16">16</xref>
                    </sup>. Classes are defined in a separate file and can easily be modified to suit the specific task.</p>
                <p>CytoBrowser utilizes the Deep Zoom Image (DZI) format for fast rendering of very large WSIs.  Currently, each z-layer is provided as a separate DZI file, where a filename of the form 
                    <monospace>imagename_zNNN.dzi</monospace> indicates an image with name &#x2019;imagename&#x2019; at z-level &#x2019;NNN&#x2019;, and where &#x2019;NNN&#x2019; is any number, typically an offset in nanometer.</p>
                <p>The backend of CytoBrowser is run in Node.js
                    <sup>
                        <xref ref-type="bibr" rid="ref-17">17</xref>
                    </sup>, with a web server implemented with the Express
                    <sup>
                        <xref ref-type="bibr" rid="ref-18">18</xref>
                    </sup> module. The server provides HTTP endpoints for getting information about the available images as well as for writing and reading annotation data in server-side storage. While these endpoints are mainly intended to be used by the CytoBrowser client, they could also be used to easily access this information from other applications. The server also provides a WebSocket endpoint for full-duplex communication between the client and server to facilitate the collaboration functionality. This communication is done using JSON messages. The only mandatory field in a such a message is the 
                    <italic toggle="yes">type</italic> field, which informs the recipient how to process any other fields that may be present.</p>
                <p>When a user opens an image in CytoBrowser, they either select an existing set of annotations to work on or start a new set. Different sets of annotations for the same image may, e.g., originate from different experts or be imported from a machine learning-based classification. The annotation set also defines a collaboration session, consisting of all users currently working on the same annotation set, much like users collaborate on the same document in web-based applications such as Google Docs
                    <sup>
                        <xref ref-type="bibr" rid="ref-19">19</xref>
                    </sup>. By encoding the current state of the interface, including the active image and annotation set, but also viewport location and zoom level, in the dynamically updated URL, it becomes very easy to invite colleagues to discuss a sample by simply sharing the active URL. In the same manner, it is easy to return to a previous image location through a stored browser bookmark.</p>
                <p>The protocol implemented for collaborations has been created with robustness in mind. The backend stores a canonical copy of the shared data, including information about the participating users, the active image and the placed annotations, that the clients request when entering a collaboration. The backend also verifies that clients are displaying the correct image. When data is altered by a connected client, only the alteration is broadcast to other collaborators.</p>
                <p>For additional details regarding the implementation, we refer the reader to the 
                    <ext-link ext-link-type="uri" xlink:href="https://github.com/MIDA-group/CytoBrowser/blob/master/implementation.md">implementation.md</ext-link> file of the software.</p>
            </sec>
            <sec>
                <title>Operation</title>
                <p>Opening images stored on the server is easy; available images are presented to the user as a gallery of thumbnails, see 
                    <xref ref-type="fig" rid="f3">Figure 3</xref> for an example. By default these thumbnails display a lower-resolution version of the full image, but by hovering over a specific entry the user is presented a zoomed-in view from the middle part of the image. After selecting an image, the user is prompted to either start a new annotation session or to continue on a previously created.</p>
                <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                    <label>Figure 3. </label>
                    <caption>
                        <title>Example of a user selecting which WSI to open, the active image (3rd row, 2nd column) is shown zoomed-in. </title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/55127/8e72d789-1e79-4df4-b9e4-a04ae6b3618c_figure3.gif"/>
                </fig>
                <p>CytoBrowser enables placing several different kinds of annotations on an image. Markers can be placed by clicking a single point, rectangular regions can be placed by clicking two opposite corners, and polygonal regions can be placed by clicking each vertex, see 
                    <xref ref-type="fig" rid="f4">Figure 4</xref> for an example of the latter. While these three annotation tools are currently present in CytoBrowser, the system is designed to allow easy addition of new tools.</p>
                <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                    <label>Figure 4. </label>
                    <caption>
                        <title>Example of a user in the process of outlining a polygonal region in a fluorescence microscopy z-stack.</title>
                    </caption>
                    <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/55127/8e72d789-1e79-4df4-b9e4-a04ae6b3618c_figure4.gif"/>
                </fig>
                <p>Once annotations are placed, there are different ways of interacting with them. They can be moved or deleted using the mouse. By right-clicking an annotation, the user gets access to more actions in a context menu. Here they can change the class assigned to the annotation or leave text comments on it to provide information that is not captured by the class label alone. In 
                    <xref ref-type="fig" rid="f2">Figure 2</xref>, the user of the laptop in the foreground is adding such a comment.</p>
                <p>Three different options for saving and loading annotation data are provided. The easiest option is for the user to rely on the autosave functionality of CytoBrowser, where the current annotation set is continuously stored on the hosting server. The second option is to manually store the data on the server. For this option, we also provide a simple versioning system. If a file is saved to a directory that contains a file with the same name, the user gets the option to either rewrite the latest version of the file or to create a new version of it. The user is then able to choose which version of a file to load when browsing the server files. The third option is to store the annotation set on the local machine of the user, using the &#x201c;import&#x201d; and &#x201c;export&#x201d; buttons in the interface. For all three options, the annotations are stored as JSON files, making the data easily transferable between different tools. This enables the annotations to be used for data selection or training of machine learning methods. Inversely, CytoBrowser may be used to visualize the classification or segmentation results generated by other tools.</p>
                <p>We believe that easy collaboration between experts from different fields is important for an efficient workflow. For CytoBrowser, we have implemented functionality that enables such collaboration to be performed remotely, where two or more users can browse and annotate the same image together in a shared session. Any changes made by one user will be seen by the other users in real-time. Users can see each other&#x2019;s mouse cursors in the viewport, and they have the option to lock their view to follow that of another user. This may be useful, e.g., in cases where an expert from one domain needs to visually explain something about the data to an expert in another domain. This capability may thus enhance the transfer of knowledge between different fields and simplify multidisciplinary research.</p>
            </sec>
        </sec>
        <sec>
            <title>Use cases</title>
            <p>To  download and install the software, follow the instructions at 
                <ext-link ext-link-type="uri" xlink:href="https://mida-group.github.io/CytoBrowser/">https://mida-group.github.io/CytoBrowser/</ext-link>. It is very easy to set up a local CytoBrowser server to be accessed from the same machine (localhost), or, e.g., through an SSH tunnel. For larger and more persistent use cases, we recommend to rely on one of popular open-source web servers, such as Apache and Nginx, as a secure loadbalancing frontend for the server.</p>
            <p>Example Bash scripts, demonstrating how to download and convert publicly available images in Zeiss (.zvi) and Hamamatsu (.ndpi) format into the Deep Zoom Image (.dzi) format, suitable for CytoBrowser, are provided together with the software in the 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/MIDA-group/CytoBrowser/tree/master/examples">examples</ext-link> directory. Software packages which may be useful for converting WSIs include 
                <ext-link ext-link-type="uri" xlink:href="https://libvips.github.io/libvips/">libvips</ext-link>, 
                <ext-link ext-link-type="uri" xlink:href="https://www.openmicroscopy.org/bio-formats/">Bio-Formats</ext-link>, and 
                <ext-link ext-link-type="uri" xlink:href="https://www.imnc.in2p3.fr/pagesperso/deroulers/software/ndpitools/">NDPITools</ext-link>.</p>
        </sec>
        <sec sec-type="conclusions">
            <title>Conclusions</title>
            <p>We present CytoBrowser, an OSS developed in response to the request for light-weight, open, flexible, and easy to use tools for collaborative visualization, annotation and assessment of whole slide image data. CytoBrowser is developed particularly with cytological analysis on mind, where efficient handling of z-stacks is a central requirement. The combi- nation of a JavaScript based browser component and a Node.js driven server-side component enables fast access to large image data together with easy and flexible storage and sharing of annotations. Being a tool particularly designed for collaborative interactive multi-user access, it facilitates knowledge exchange and alleviates interdisciplinary research.</p>
            <p>In addition to being a much desired resource for the creation of large annotated datasets, crucial for training and evaluation of machine and deep learning-based approaches to bioimage analysis, as well as the visualization and qualitative evaluation of the results of such methods, we also envision that CytoBrowser may be a useful tool for distributed education, quality improvement, competency assessment, proficiency testing, and performance evaluation
                <sup>
                    <xref ref-type="bibr" rid="ref-20">20</xref>
                </sup>.</p>
            <p>By delivering a powerful virtual microscope environment which is easily accessed through a web-browser interface and functional on any modern computer or tablet, we hope that CytoBrowser, facilitating efficient utilization of distributed resources and expert knowledge, may contribute towards fair and universally accessible health-care.</p>
        </sec>
        <sec>
            <title>Software availability</title>
            <list list-type="bullet">
                <list-item>
                    <p>Software available from:  
                        <ext-link ext-link-type="uri" xlink:href="https://mida-group.github.io/CytoBrowser/">https://mida-group.github.io/CytoBrowser/</ext-link>
                    </p>
                </list-item>
                <list-item>
                    <p>Source code available from: 
                        <ext-link ext-link-type="uri" xlink:href="https://github.com/MIDA-group/CytoBrowser">https://github.com/MIDA-group/CytoBrowser</ext-link>
                    </p>
                </list-item>
                <list-item>
                    <p>Archived  source  code  at  time  of  publication:   
                        <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.4582760">https://doi.org/10.5281/zenodo.4582760</ext-link>
                        <sup>
                            <xref ref-type="bibr" rid="ref-21">21</xref>
                        </sup>
                    </p>
                </list-item>
                <list-item>
                    <p>License: GNU General Public License v3.0</p>
                </list-item>
            </list>
        </sec>
    </body>
    <back>
        <ack>
            <title>Acknowledgements</title>
            <p>We thank Leslie Solorzano and Prof.  Carolina W&#x00e4;hlby for their support in forking TissUUmaps.</p>
            <p>This publication was supported by COST Action NEUBIAS (CA15124), funded by COST (European Cooperation in Science and Technology).</p>
        </ack>
        <ref-list>
            <ref id="ref-1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Zarella</surname>
                            <given-names>MD</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <article-title>Introduction to digital image analysis in whole-slide imaging: a white paper from the digital pathology association.</article-title>
                    <source>

                        <italic toggle="yes"> J Pathol Inform.</italic>
</source>
                    <year>2019</year>;<volume>10</volume>:<fpage>9</fpage>.
                    <pub-id pub-id-type="pmid">30984469</pub-id>
                    <pub-id pub-id-type="doi">10.4103/jpi.jpi_82_18</pub-id>
                    <pub-id pub-id-type="pmcid">6437786</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Gupta</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>Whole slide imaging (WSI) in pathology: current perspectives and future directions.</article-title>
                    <source>

                        <italic toggle="yes">J Digit Imaging.</italic>
</source>
                    <year>2020</year>;<volume>33</volume>(<issue>4</issue>):<fpage>1034</fpage>&#x2013;<lpage>1040</lpage>.
                    <pub-id pub-id-type="pmid">32468487</pub-id>
                    <pub-id pub-id-type="doi">10.1007/s10278-020-00351-z</pub-id>
                    <pub-id pub-id-type="pmcid">7522141</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Mar&#x00e9;e</surname>
                            <given-names>R</given-names>
                        </name>
</person-group>:
                    <article-title>Open practices and resources for collaborative digital pathology.</article-title>
                    <source>

                        <italic toggle="yes"> Front Med (Lausanne).</italic>
</source>
                    <year>2019</year>;<volume>6</volume>:<fpage>255</fpage>.
                    <pub-id pub-id-type="pmid">31799253</pub-id>
                    <pub-id pub-id-type="doi">10.3389/fmed.2019.00255</pub-id>
                    <pub-id pub-id-type="pmcid">6868018</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>A containerized software system for generation, management, and exploration of features from whole slide tissue images.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Res.</italic>
</source>
                    <year>2017</year>;<volume>77</volume>(<issue>21</issue>):<fpage>e79</fpage>&#x2013;<lpage>e82</lpage>.
                    <pub-id pub-id-type="pmid">29092946</pub-id>
                    <pub-id pub-id-type="doi">10.1158/0008-5472.CAN-17-0316</pub-id>
                    <pub-id pub-id-type="pmcid">5987533</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>The digital slide archive: A software platform for management, integration, and analysis of histology for cancer research.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Res.</italic>
</source>
                    <year>2017</year>;<volume>77</volume>(<issue>21</issue>):<fpage>e75</fpage>&#x2013;<lpage>e78</lpage>.
                    <pub-id pub-id-type="pmid">29092945</pub-id>
                    <pub-id pub-id-type="doi">10.1158/0008-5472.CAN-17-0629</pub-id>
                    <pub-id pub-id-type="pmcid">5898232</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Martel</surname>
                            <given-names>AL</given-names>
                        </name>

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

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

                        <etal/>
</person-group>:
                    <article-title>An image analysis resource for cancer research: Piip&#x2014;pathology image informatics platform for visualization, analysis, and management.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Res.</italic>
</source>
                    <year>2017</year>;<volume>77</volume>(<issue>21</issue>):<fpage>e83</fpage>&#x2013;<lpage>e86</lpage>.
                    <pub-id pub-id-type="pmid">29092947</pub-id>
                    <pub-id pub-id-type="doi">10.1158/0008-5472.CAN-17-0323</pub-id>
                    <pub-id pub-id-type="pmcid">5679396</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>W&#x00e4;hlby</surname>
                            <given-names>C</given-names>
                        </name>
</person-group>:
                    <article-title>TissUUmaps: Interactive visualization of large-scale spatial gene expression and tissue morphology data.</article-title>
                    <source>

                        <italic toggle="yes">Bioinformatics.</italic>
</source>
                    <year>2020</year>;<volume>36</volume>(<issue>15</issue>):<fpage>4363</fpage>&#x2013;<lpage>4365</lpage>.
                    <pub-id pub-id-type="pmid">32449759</pub-id>
                    <pub-id pub-id-type="doi">10.1093/bioinformatics/btaa541</pub-id>
                    <pub-id pub-id-type="pmcid">7520034</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Mar&#x00e9;e</surname>
                            <given-names>R</given-names>
                        </name>

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

                        <name name-style="western">
                            <surname>St&#x00e9;vens</surname>
                            <given-names>B</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Collaborative analysis of multi-gigapixel imaging data using cytomine.</article-title>
                    <source>

                        <italic toggle="yes">Bioinformatics.</italic>
</source>
                    <year>2016</year>;<volume>32</volume>(<issue>9</issue>):<fpage>1395</fpage>&#x2013;<lpage>1401</lpage>.
                    <pub-id pub-id-type="pmid">26755625</pub-id>
                    <pub-id pub-id-type="doi">10.1093/bioinformatics/btw013</pub-id>
                    <pub-id pub-id-type="pmcid">4848407</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>OMERO: flexible, model-driven data management for experimental biology.</article-title>
                    <source>

                        <italic toggle="yes"> Nat Methods.</italic>
</source>
                    <year>2012</year>;<volume>9</volume>(<issue>3</issue>):<fpage>245</fpage>&#x2013;<lpage>253</lpage>.
                    <pub-id pub-id-type="pmid">22373911</pub-id>
                    <pub-id pub-id-type="doi">10.1038/nmeth.1896</pub-id>
                    <pub-id pub-id-type="pmcid">3437820</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Loughrey</surname>
                            <given-names>MB</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Fern&#x00e1;ndez</surname>
                            <given-names>JA</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>QuPath: open source software for digital pathology image analysis.</article-title>
                    <source>

                        <italic toggle="yes">Sci Rep.</italic>
</source>
                    <year>2017</year>;<volume>7</volume>(<issue>1</issue>):<fpage>16878</fpage>.
                    <pub-id pub-id-type="pmid">29203879</pub-id>
                    <pub-id pub-id-type="doi">10.1038/s41598-017-17204-5</pub-id>
                    <pub-id pub-id-type="pmcid">5715110</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Hanna</surname>
                            <given-names>MG</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Monaco</surname>
                            <given-names>SE</given-names>
                        </name>

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

                        <etal/>
</person-group>:
                    <article-title>Comparison of glass slides and various digital-slide modalities for cytopathology screening and interpretation.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Cytopathol.</italic>
</source>
                    <year>2017</year>;<volume>125</volume>(<issue>9</issue>):<fpage>701</fpage>&#x2013;<lpage>709</lpage>.
                    <pub-id pub-id-type="pmid">28558124</pub-id>
                    <pub-id pub-id-type="doi">10.1002/cncy.21880</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

                        <name name-style="western">
                            <surname>Stark</surname>
                            <given-names>CR</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title> A deep learning based pipeline for efficient oral cancer screening on whole slide images</article-title>. In
                    <source>

                        <italic toggle="yes">International Conference on Image Analysis and Recognition.</italic>
</source>
                    <year>2020</year>;<fpage>249</fpage>&#x2013;<lpage>261</lpage>. Springer.
                    <pub-id pub-id-type="doi">10.1007/978-3-030-50516-5_22</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-13">
                <label>13</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

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

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

                        <etal/>
</person-group>:
                    <article-title>Learning pathology using collaborative vs. individual annotation of whole slide images: a mixed methods trial.</article-title>
                    <source>

                        <italic toggle="yes">BMC Med Educ.</italic>
</source>
                    <year>2016</year>;<volume>16</volume>(<issue>1</issue>):<fpage>311</fpage>.
                    <pub-id pub-id-type="pmid">27955651</pub-id>
                    <pub-id pub-id-type="doi">10.1186/s12909-016-0831-x</pub-id>
                    <pub-id pub-id-type="pmcid">5154086</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <collab>OpenSeadragon</collab>:
                    <article-title>An open-source, web-based viewer for high-resolution zoomable images, implemented in pure JavaScript, for desktop and mobile.</article-title>Accessed on: Feb. 2021.
                    <ext-link ext-link-type="uri" xlink:href="https://openseadragon.github.io/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <article-title>The revealing module pattern in javascript.</article-title>Accessed on: Feb. 2021.
                    <ext-link ext-link-type="uri" xlink:href="https://gist.github.com/zcaceres/bb0eec99c02dda6aac0e041d0d4d7bf2">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Wilbur</surname>
                            <given-names>DC</given-names>
                        </name>
</person-group>:
                    <article-title>The Bethesda system for reporting cervical cytology: definitions, criteria, and explanatory notes</article-title>. Springer,<year>2015</year>.
                    <ext-link ext-link-type="uri" xlink:href="https://www.springer.com/gp/book/9783319110738">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <collab>Node.js</collab>:
                    <article-title>A javascript runtime built on Chrome&#x2019;s V8 JavaScript engine</article-title>. Accessed on: Feb. 2021.
                    <ext-link ext-link-type="uri" xlink:href="https://nodejs.org/en/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-18">
                <label>18</label>
                <mixed-citation publication-type="journal">
                    <collab>Express</collab>:
                    <article-title>Fast, unopinionated, minimalist web framework for Node.js</article-title>. Accessed on: Feb. 2021.
                    <ext-link ext-link-type="uri" xlink:href="https://expressjs.com/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-19">
                <label>19</label>
                <mixed-citation publication-type="journal">
                    <article-title>Announcing Google Workspace, everything you need to get it done, in one location</article-title>. Google Cloud Blog. Accessed on: Feb. 2021.
                    <ext-link ext-link-type="uri" xlink:href="https://cloud.google.com/blog/products/workspace/introducing-google-workspace">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-20">
                <label>20</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Minhajuddin</surname>
                            <given-names>AT</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hynan</surname>
                            <given-names>LS</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Agreement between cytotechnologists and cytopathologists as a new measure of cytopathologist performance in gynecologic cytology.</article-title>
                    <source>

                        <italic toggle="yes">Cancer Cytopathol.</italic>
</source>
                    <year>2017</year>;<volume>125</volume>(<issue>7</issue>):<fpage>576</fpage>&#x2013;<lpage>580</lpage>.
                    <pub-id pub-id-type="pmid">28346747</pub-id>
                    <pub-id pub-id-type="doi">10.1002/cncy.21856</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-21">
                <label>21</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

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

                        <name name-style="western">
                            <surname>Lindblad</surname>
                            <given-names>J</given-names>
                        </name>
</person-group>:
                    <article-title>MIDA-group/CytoBrowser: Bugfix release v1.0.1, URL location encoding (Version v1.0.1).</article-title>
                    <source>

                        <italic toggle="yes">Zenodo.</italic>
</source>
                    <ext-link ext-link-type="uri" xlink:href="http://www.doi.org/10.5281/zenodo.4582760">http://www.doi.org/10.5281/zenodo.4582760</ext-link>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report81855">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.55127.r81855</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Bankhead</surname>
                        <given-names>Peter</given-names>
                    </name>
                    <xref ref-type="aff" rid="r81855a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-4851-8813</uri>
                </contrib>
                <aff id="r81855a1">
                    <label>1</label>Edinburgh Pathology, University of Edinburgh, Edinburgh, UK</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>30</day>
                <month>4</month>
                <year>2021</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2021 Bankhead P</copyright-statement>
                <copyright-year>2021</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="relatedArticleReport81855" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.51916.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This paper introduces CytoBrowser, an open-source solution for viewing and annotating whole slide images and other microscopy data. CytoBrowser is a fork of TissUUmaps, adding new functionality to support z-stacks and collaborative annotation.</p>
            <p> </p>
            <p> CytoBrowser looks like it could be very useful for a limited number of specific applications already, and potentially many more with additional development. I believe the paper would be strengthened considerably by describing in more detail the applications where CytoBrowser has been used.</p>
            <p> </p>
            <p> Further documentation and information about future development plans would also be essential if the software is to be widely adopted.&#x00a0;To make use of Cytobrowser's collaborative features (which seem a major strength), it would be necessary to set up a server - requiring some level of computing knowledge, effort and resources.&#x00a0;For this reason, I think it is important to make the benefits of using the software as clear as possible, and the process for using it as straightforward as possible; without this, I am not sure why a potential user would make the effort. A demo server, video demos, more illustrated documentation, and more detail within this article would all help with this.</p>
            <p> </p>
            <p> 
                <bold>Specific points and questions</bold>
            </p>
            <p> </p>
            <p> 
                <italic>'A variety of OSS project that support WSIs exist, examples include caMicroscope4, Digital Slide Archive5, Sedeen viewer6, TissUUmaps7, Cytomine8, OMERO9, and QuPath10. The vast majority of existing WSI tools are developed with histology in mind, whereas cytology is only recently gaining increased attention.'</italic>
            </p>
            <p> - I think SlideRunner (https://github.com/DeepPathology/SlideRunner) should be included. Since there is no real direct comparison, it is not clear what the benefits of CytoBrowser are over the others for any applications. A table comparing relevant features could address this.</p>
            <p> </p>
            <p> 
                <italic>'The majority of existing tools are directed towards histopathology, with different needs and requirements.'</italic>
            </p>
            <p> - Other than z-stack support (which at least some of the listed software provides), I'm not sure what these different needs and requirements are - at least in terms of the annotation tools (points, rectangles, polygons) provided by CytoBrowser.</p>
            <p> </p>
            <p> 
                <italic>'We present CytoBrowser, an OSS developed in response to the request for light-weight, open, flexible, and easy to use tools for collaborative visualization, annotation and assessment of whole slide image data.'</italic>
            </p>
            <p> - I suggest swapping 'request' for 'need', or else elaborating upon who requested it and for what purpose.</p>
            <p> </p>
            <p> 
                <italic>'CytoBrowser provides a web-based viewer for high-resolution zoomable images and facilitates easy remote collaboration, with options for joint-view visualization [...]'</italic>
            </p>
            <p> - It's not obvious to me what 'joint-view visualization' means (I assume multiple users seeing the same region?).</p>
            <p> </p>
            <p> 
                <italic>'The multi-user design of CytoBrowser offers concurrent access to samples, where different experts may assess, comment on, or edit each others annotations, or where an educator may, e.g., show students different medically relevant examples.'</italic>
            </p>
            <p> - Has CytoBrowser been used in education, or would it require further development? Can access and annotation be controlled (i.e. to restrict changes students can make)? In a sense, any platform that allows image viewing might be used in education. If there are specific strengths in using CytoBrowser for this, these should be specified.</p>
            <p> </p>
            <p> 
                <italic>'The protocol implemented for collaborations has been created with robustness in mind. The backend stores a canonical copy of the shared data, including information about the participating users, the active image and the placed annotations, that the clients request when entering a collaboration. The backend also verifies that clients are displaying the correct image. When data is altered by a connected client, only the alteration is broadcast to other collaborators.'</italic>
            </p>
            <p> - I believe the robustness claim needs supporting evidence, particularly given the focus on being lightweight and using json files for storage. Has CytoBrowser been stress-tested, with a large number of concurrent users? Is there an expected limit to the number of concurrent users?</p>
            <p> </p>
            <p> 
                <italic>'Inversely, CytoBrowser may be used to visualize the classification or segmentation results generated by other tools.'</italic>
            </p>
            <p> - How? Are any open standards supported for importing annotations, or must they be converted to a CytoBrowser-specific format? How scalable is this, e.g. does it support thousands or even millions of 'objects'/regions? Are rasterized segmentation results supported (i.e. overlapping another image, rather than annotations)?</p>
            <p> </p>
            <p> 
                <italic>'CytoBrowser delivers fast browsing through focus levels by use of transparent layers.'</italic>
            </p>
            <p> - What are 'transparent layers' here?</p>
            <p> </p>
            <p> 
                <italic>'While these three annotation tools are currently present in CytoBrowser, the system is designed to allow easy addition of new tools.'</italic>
            </p>
            <p> - How? Is this documented?</p>
            <p> </p>
            <p> 
                <italic>'CytoBrowser is a fork and extension of TissUUmaps7 (GPLv3 license)'</italic>
            </p>
            <p> - Is there a justification for forking TissUUmaps, rather than contributing to the original project? How will both be maintained in the future? Is there any intention to incorporate future improvements to one software within the other?</p>
            <p> </p>
            <p> 
                <italic>'We share the source code of CytoBrowser openly and freely under the GNU General Public License v3.0, with the hope that a growing community of users will jointly contribute to its further improvement.'</italic>
            </p>
            <p> - Given that fulfilling the potential of CytoBrowser (as outlined in the paper) would seem to require further development, I would like to understand if the authors intend to further develop the software themselves. Community development would require central maintenance; without clear evidence of active ongoing support it is difficult to see how this hope can be fulfilled.</p>
            <p> </p>
            <p> 
                <bold>Use of CytoBrowser</bold>
            </p>
            <p> </p>
            <p> I was able to successfully run CytoBrowser locally on a Mac. There were a two minor complications, and one possibly bigger limitation: 
                <list list-type="bullet">
                    <list-item>
                        <p>To run the example scripts, I needed to install wget and libvips (via homebrew), as well as finding, downloading &amp; unzipping bftools. Further documentation, with links, would help others do this.</p>
                    </list-item>
                    <list-item>
                        <p>No images are available when using Safari locally, but without explanation - it simply appears to be broken. With Chrome and Firefox it works, but some form of notification when Safari fails would be helpful. This is not entirely compatible with the statement 
                            <italic>'CytoBrowser is compatible with all modern browsers.'</italic>
                        </p>
                    </list-item>
                    <list-item>
                        <p>The proposed ZVI example file is extremely dark. Since .dzi involves conversion to JPEG, colours and contrast seem to be 'fixed' at the conversion step - without any option to adjust these through the UI. This seems like a significant limitation for non-RGB images. Is there a solution?</p>
                    </list-item>
                    <list-item>
                        <p>The need to generate .dzi datasets is a barrier to testing the software (which I imagine is harder on Windows). Providing a relevant dataset (ideally for cytology) without a need for conversion would help overcome this.</p>
                    </list-item>
                </list> Some further comments on using the software: 
                <list list-type="bullet">
                    <list-item>
                        <p>I don't recognize the format of the JSON export; is it custom for CytoBrowser? For interoperability, I think a standard such as GeoJSON would be strongly preferable.</p>
                    </list-item>
                    <list-item>
                        <p>The 'Usage instructions' within the UI are very helpful, although in some cases it would be helpful to have instructions closer to the relevant command, e.g. via tooltips.</p>
                    </list-item>
                    <list-item>
                        <p>Shortcuts are unexpected (e.g. c, v, b to change annotation tool). Shift + mouse wheel is nice to rotate, but I expected the rotation direction to change with the scroll direction.</p>
                    </list-item>
                    <list-item>
                        <p>I find the Session and Collaboration interfaces confusing. I found myself inadvertently creating many new sessions when exploring whether I can make changes to the current one (e.g. to set its name). I think 'Session name' should be above 'Username' under the 'Collaboration' window, but it's not clear to me what is the impact of changing either, nor whether 'Change session' means 'change the properties of the session' or 'switch to a different session'.</p>
                    </list-item>
                    <list-item>
                        <p>The use of separate .dzi datasets for z-slices seems a bit awkward; it would help if these could at least be arranged within the same subdirectory (rather than all inside one 'data' directory) for better data organization.</p>
                    </list-item>
                    <list-item>
                        <p>Clicking on 'Session' at the top of the screen allows me to change the user, but clicking on 'User' does not.</p>
                    </list-item>
                    <list-item>
                        <p>The collaborative features of CytoBrowser sound like a particular strength of the platform, however I was unable to test these.</p>
                    </list-item>
                </list>
            </p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>No</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>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>image analysis, digital pathology, open-source software</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="report81858">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.55127.r81858</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>N&#x00f8;rrelykke</surname>
                        <given-names>Simon</given-names>
                    </name>
                    <xref ref-type="aff" rid="r81858a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-8302-526X</uri>
                </contrib>
                <aff id="r81858a1">
                    <label>1</label>Image and Data Analysis group, ScopeM, ETH Z&#x00fc;rich, Z&#x00fc;rich, Switzerland</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>8</day>
                <month>4</month>
                <year>2021</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2021 N&#x00f8;rrelykke S</copyright-statement>
                <copyright-year>2021</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="relatedArticleReport81858" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.51916.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>reject</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>The authors introduce CytoBrowser, an open-source, server-client, browser-interface solution for collaboratively viewing and annotation of large microscopy image data.</p>
            <p> CytoBrowser is a fork of TissUUmaps, adding handling of z-stacks incl. z-level dependent annotations.</p>
            <p> </p>
            <p> The intended audience are cytotechnologist and cytopathologists, as opposed to histopathologists.</p>
            <p> CytoBrowser also aims to be used in a (remote) teaching setting, through the use of synchronisation between the teacher's/expert's browser-view and the students.</p>
            <p> </p>
            <p> Overall the paper is well written with few if any typographical or grammatical errors and lays out its goal and ambitions in a rather clear fashion.</p>
            <p> </p>
            <p> However, the overall feeling is that CytoBrowser is not ready to be shared with the world as it is missing proper installation instructions, a user-manual, and a demo-site. It feels like a local lab-tool that the authors are taking steps to make more broadly accessible, which is commendable, but there is still some way to go.</p>
            <p> </p>
            <p> 
                <bold>OBSERVATIONS ON WRITING STYLE:</bold>
            </p>
            <p> </p>
            <p> The Introduction is comparatively long, reads somewhat like a sales pamphlet, and includes most of the information repeated in the very brief Methods.</p>
            <p> </p>
            <p> There is a tendency of mixing up turns of phrase, e.g. "making headway into", "There is lately", "in the main focus", and "on mind"; which are probably better put as "making its way into" or "making headway in" etc.</p>
            <p> </p>
            <p> Variations of "easy" (easy, easily, easiest) appear 24 times - in most instances the word could be omitted for a more sober delivery, losing no information.</p>
            <p> </p>
            <p> 
                <bold>RECOMMENDATIONS:</bold>
            </p>
            <p> </p>
            <p> Make a web-server demo-version available so the potential user can try it out without having to install the full solution.</p>
            <p> </p>
            <p> Compare to commercial solutions - open source is not the only player out there.&#x00a0;</p>
            <p> How does is stack up against e.g. Arivis (https://imaging.arivis.com/)?</p>
            <p> </p>
            <p> Improve the installation instructions by having someone try to follow them: I gave it 30 minutes and failed to get it to run (details below).</p>
            <p> </p>
            <p> Make it run on MacOS as well: Many, if not most, biologists use Macs, not Windows, and definitely not Linux.</p>
            <p> </p>
            <p> Be explicit about which other softwares CytoBrowser can directly import/export annotations from/to. Does it play well with e.g. ilastik or Imagej (see here for some ref: 
                <ext-link ext-link-type="uri" xlink:href="https://f1000research.com/articles/9-1248">https://f1000research.com/articles/9-1248</ext-link> incl. Jan Eglinger's referee report)</p>
            <p> </p>
            <p> Be explicit about what image formats are natively supported - it seems only .dzi and the user have to make the conversion using some of your provided scripts or find another way. This is fine, but be very upfront about this</p>
            <p> </p>
            <p> Write a proper user-manual either in GitHub or in https://readthedocs.org/ - this is the accepted standard for useful open-source software looking for users. It is work and it is boring, but it is neccessary if you want to have users outside your own lab.</p>
            <p> </p>
            <p> 
                <bold>LITTLE THINGS:</bold>
            </p>
            <p> </p>
            <p> The figures online and in PowerPoint are not vector graphics and do not allow zooming to a useful level. PDF file is fine.</p>
            <p> </p>
            <p> 
                <bold>INSTALLATION STEPS TAKEN:</bold>
            </p>
            <p> </p>
            <p> Installation on Ubuntu 20.04.2 LTS running on a Thinkpad.</p>
            <p> Notice that the Linux commands are different from and additional to the ones you give in your instructions, in order to get just some of the way.</p>
            <p> I am not saying it cannot be done, I am saying that it would likely take more time than is usual for shared open-source code and defintely more than a test-user can be expected to invest.</p>
            <p> </p>
            <p> #+begin_src&#x00a0;</p>
            <p> git clone https://github.com/MIDA-group/CytoBrowser.git</p>
            <p> cd CytoBrowser/</p>
            <p> </p>
            <p> sudo apt install npm</p>
            <p> </p>
            <p> sudo apt install curl</p>
            <p> sudo apt-get install -y nodejs</p>
            <p> curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash -</p>
            <p> </p>
            <p> npm install express --save</p>
            <p> npm install</p>
            <p> </p>
            <p> mkdir data</p>
            <p> mkdir storage</p>
            <p> mkdir collap_storage</p>
            <p> </p>
            <p> #+end_src</p>
            <p> </p>
            <p> Downloaded the Zeiss example images and moved them to ./data</p>
            <p> </p>
            <p> Running (failing to run):</p>
            <p> #+begin_src&#x00a0;</p>
            <p> simon@simon-ThinkPad-P1-Gen-2:~/Desktop/CB/CytoBrowser$ node cytobrowser.js localhost 8080</p>
            <p> CytoBrowser server listening at http://127.0.0.1:8080</p>
            <p> /home/simon/Desktop/CB/CytoBrowser/server/availableImages.js:142</p>
            <p> &#x00a0; &#x00a0; &#x00a0; &#x00a0; let names = dir.map(name =&gt; name.match(nameEx)).flat();</p>
            <p> &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; &#x00a0; ^</p>
            <p> </p>
            <p> TypeError: dir.map(...).flat is not a function</p>
            <p> &#x00a0; &#x00a0; at fs.readdir (/home/simon/Desktop/CB/CytoBrowser/server/availableImages.js:142:57)</p>
            <p> &#x00a0; &#x00a0; at FSReqWrap.args [as oncomplete] (fs.js:140:20)</p>
            <p> #+end_src</p>
            <p> </p>
            <p> 
                <bold>CONCLUSION:</bold>
            </p>
            <p> Currently I cannot approve for indexing as I could not verify that the software actually works or does any of the wonderful things described in the manuscript: The test of reproducibility failed!</p>
            <p> If the relevant recommendations re. documentation, installation instructions, and a test-server are followed, I would be happy to recommend indexing (after verifying that the software works) - any stylistic and linguistic idiosyncrasies are entirely the choice of the authors and will not influence my decision.</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>Yes</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>No</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>Image analysis. Biophysics.</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to state that I do not consider it to be of an acceptable scientific standard, for reasons outlined above.</p>
        </body>
        <sub-article article-type="response" id="comment6560-81858">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Lindblad</surname>
                            <given-names>Joakim</given-names>
                        </name>
                        <aff>Uppsala University, Sweden</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>11</day>
                    <month>4</month>
                    <year>2021</year>
                </pub-date>
            </front-stub>
            <body>
                <p>
                    <bold>Response to Reviewer Report #1 (S. N&#x00f8;rrelykke)</bold>
                </p>
                <p> </p>
                <p> 
                    <bold>Reviewer: </bold>
                    <italic>&#x201c;Overall the paper is well written with few if any typographical or grammatical errors and lays out its goal and ambitions in a rather clear fashion.&#x201d;</italic>
                </p>
                <p> 
                    <bold>Response: </bold>We are glad to read that the reviewer appreciates our aim towards clarity of presentation.</p>
                <p> </p>
                <p> 
                    <bold>Reviewer: </bold>
                    <italic>&#x201c;However, the overall feeling is that CytoBrowser is not ready to be shared with the world as it is missing proper installation instructions, a user-manual, and a demo-site. It feels like a local lab-tool that the authors are taking steps to make more broadly accessible, which is commendable, but there is still some way to go.&#x201d;</italic>
                </p>
                <p> 
                    <bold>Response: </bold>We agree with the reviewer that a user-manual and a demo-site are certainly desirable additions that will further improve accessibility to the tool. However, we strongly disagree with the reviewer that an absence of such renders it inappropriate to be shared. Yes, it is a &#x201c;local lab-tool&#x201d;, which we have developed based on our own needs, and yes, we feel that it may be useful for a wider community and therefore we wish to inform a broader audience about its existence and invite them to try, use, and possibly contribute to its further development in the spirit of FOSS.</p>
                <p> The alternative, to not publish the tool before we have found resources to host a demo-site and to write a separate user-manual (to complement the existing help pages of the software), seems as a rather unneeded delay. Further, we consider the installation instructions, which assume an ability to install required auxiliary software, to be sufficiently detailed for the envisioned users of the server side of the tool (see also later part of this response). We emphasize that once set up, users of the browser based interface (including cytotechnologist and cytopathologists) need not perform any installation at all.</p>
                <p> </p>
                <p> Regarding 
                    <bold>Observations on writing style</bold>: We appreciate the reviewers opinions and will take them into consideration when updating the manuscript; we will await other reviewer&#x2019;s responses to spare them from reviewing a moving target.</p>
                <p> </p>
                <p> Regarding 
                    <bold>Recommendations</bold>: We hope to find resources to host a demo web-server. We do not consider that to be a requirement for publication though. On 
                    <italic>a comparison with commercial solutions</italic>, we do not consider a closed proprietary solution a reasonable alternative, as clearly explained in the paper. 
                    <italic>&#x201c;Make it run on MacOS&#x201d;</italic> &#x2013; All parts of the software runs well on MacOS. (We wonder how the reviewer reached the (incorrect) conclusion that it does not.) 
                    <italic>&#x201c;Many, if not most, biologists use Macs&#x201d;</italic> &#x2013; Additionally, the end user may run the interface on any browser, in any OS (we believe this is made clear in the manuscript). 
                    <italic>&#x201c;Be explicit about what image formats are natively supported&#x201d;</italic>&#x00a0; &#x2013; This is clearly stated at several places in the text, including very explicitly in the &#x201c;Use cases&#x201d;. 
                    <italic>&#x201c;The figures online and in PowerPoint are not vector graphics&#x201d;</italic> &#x2013; This is due to F1000Research, we will ask them to improve this; we recommend the PDF version where figures are of higher resolution.</p>
                <p> </p>
                <p> 
                    <bold>INSTALLATION STEPS TAKEN:</bold>
                </p>
                <p> Prompted by the reviewer&#x2019;s attempt, we performed an installation on a clean Ubuntu 20.04.2 LTS. This confirmed that the steps listed in the installation instructions are accurate and work as intended. The instructions explicitly point to external sources on how to install an up-to-date Node.js (version 12 or later required).</p>
                <p> For the reviewer&#x2019;s specific case of Ubuntu (which ships with v10 of Node.js, despite v12 being out since April 2019) we recommend to verify that the Node.js update actually succeeded, by typing &#x2018;node -v&#x2019; in a terminal and confirming the correct version. The error performed by the reviewer is that the following two operations were executed in the wrong order (see also the output of the &#x2018;setup_14.x&#x2019;-step): 
                    <list list-type="order">
                        <list-item>
                            <p>curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash -</p>
                        </list-item>
                        <list-item>
                            <p>sudo apt-get install -y nodejs</p>
                        </list-item>
                    </list> </p>
                <p> The below short list of steps perform the complete installation on a clean Ubuntu 20.04.2 LTS (these steps also match the installation instructions):</p>
                <p> </p>
                <p> #+begin_src</p>
                <p> </p>
                <p> #curl needed for the Node.js update, libvips needed for conversion of data to .dzi</p>
                <p> sudo apt -y update &amp;&amp; sudo apt -y install git npm curl libvips-tools</p>
                <p> </p>
                <p> #install a newer node.js for Ubuntu (v12 works as well)</p>
                <p> curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash -</p>
                <p> sudo apt-get install -y nodejs</p>
                <p> </p>
                <p> #the CytoBrowser installation starts here</p>
                <p> git clone 
                    <ext-link ext-link-type="uri" xlink:href="https://github.com/MIDA-group/CytoBrowser.git">
                        <underline>https://github.com/MIDA-group/CytoBrowser.git</underline>
                    </ext-link>
                </p>
                <p> cd CytoBrowser</p>
                <p> npm install</p>
                <p> </p>
                <p> #start the CytoBrowser server</p>
                <p> node cytobrowser.js localhost 8080</p>
                <p> </p>
                <p> #In a separate terminal we download and convert some data using one of the provided example scripts:</p>
                <p> cd CytoBrowser</p>
                <p> ./examples/Hamamatsu-OS-2.sh #downloads, converts, and opens a browser window</p>
                <p> </p>
                <p> #+end_src</p>
                <p> </p>
                <p> If there are any problems, we recommend the Reviewer to post an &#x2018;Issue&#x2019; on GitHub, which is the standard and recommended way to handle such events.</p>
            </body>
        </sub-article>
        <sub-article article-type="response" id="comment6577-81858">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Lindblad</surname>
                            <given-names>Joakim</given-names>
                        </name>
                        <aff>Uppsala University, Sweden</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>13</day>
                    <month>4</month>
                    <year>2021</year>
                </pub-date>
            </front-stub>
            <body>
                <p>
                    <bold>LITTLE THINGS:</bold>
                </p>
                <p> Reviewer: "The figures online and in PowerPoint are not vector graphics and do not allow zooming to a useful level."</p>
                <p> </p>
                <p> Thanks for pointing this out.&#x00a0;We have contacted F1000Research about the issue and they have now (this morning) replaced the web images (and pptx) with higher resolution files.</p>
            </body>
        </sub-article>
    </sub-article>
</article>
