The era of connectomics/synaptomics ushered in the advent of large-scale availability of highly complex fruit fly brain data (Chiang et al., 2011; Berck et al., 2016; Takemura et al., 2017a; Scheffer et al., 2020), while simultaneously highlighting the dearth of computational tools with the speed and scale that can be effectively deployed to uncover the functional logic of fly brain circuits. In the early 2000’s, automation tools introduced in computational genomics significantly accelerated the pace of gene discovery from the large amounts of genomic data. Likewise, there is a need to develop tightly integrated computing tools that automate the process of 3D exploration and visualization of fruit fly brain data with the interactive exploration of executable circuits. The fruit fly brain data considered here includes neuroanatomy, genetics, and neurophysiology datasets. Due to space limitations, we mostly focus here on exploring, analyzing, comparing, and evaluating executable circuits informed by wiring diagrams derived from neuroanatomy datasets currently available in public domain.

To meet this challenge, we have built an open-source interactive computing platform called FlyBrainLab. FlyBrainLab is uniquely positioned to accelerate the discovery of the functional logic of the Drosophila brain. It is designed with three main capabilities in mind: (1) 3D exploration and visualization of fruit fly brain data, (2) creation of executable circuits directly from the explored and visualized fly brain data in step (1), and (3) interactive exploration of the functional logic of the executable circuits devised in step (2) (see Figure 1).

Figure 1

Download asset Open asset

To achieve tight integration of the three main capabilities sketched in Figure 1 into a single working environment, FlyBrainLab integrates fly brain data in the NeuroArch Database (Givon et al., 2015) and provides circuit execution with the Neurokernel Execution Engine (Givon and Lazar, 2016) (see Figure 2a). The NeuroArch Database stores neuroanatomy datasets provided by for example, FlyCircuit (Chiang et al., 2011), Larva L1EM (Ohyama et al., 2015), the Medulla 7 Column (Takemura et al., 2017a) and Hemibrain (Scheffer et al., 2020), genetics datasets published by for example, FlightLight (Jenett et al., 2012) and FlyCircuit (Chiang et al., 2011), and neurophysiology datasets including the DoOR (Münch and Galizia, 2016) and our own in vivo recordings (Lazar and Yeh, 2020; Kim et al., 2011; Kim et al., 2015). The Neurokernel Execution Engine (see Figure 2a) supports the execution of fruit fly brain circuits on GPUs. Finally, the NeuroMynerva front-end exhibits an integrated 3D graphics user interface (GUI) and provides the user a unified view of data integration and computation (see Figure 2a (top) and Figure 2b). The FlyBrainLab software architecture is depicted in the Appendix 1—figure 1.

Figure 2

Download asset Open asset

To accelerate the generation of executable circuits from fruit fly brain data, NeuroMynerva supports the following workflow.

First, the 3D GUI, called the NeuroNLP window (see Figure 2b, top middle-left), supports the visual exploration of fly brain data, including neuron morphology, synaptome, and connectome from all available data sources, stored in the NeuroArch Database (Givon et al., 2015). With plain English queries (see Figure 2b, top middle-left), a layperson can perform sophisticated database queries with only knowledge of fly brain neuroanatomy (Ukani et al., 2019).

Second, the circuit diagram GUI, called the NeuroGFX window (see Figure 2b, top middle-right) enables the interactive exploration of executable circuits stored in the NeuroArch Database. By retrieving tightly integrated biological data and executable circuit models from the NeuroArch Database, NeuroMynerva supports the interaction and interoperability between the biological circuit (or pathway for short) built for morphological visualization and the executable circuit created and represented as an interactive circuit diagram, and allows them to build on each other. This helps circuit developers to more readily identify the modeling assumptions and the relationship between neuroanatomy, neurocircuitry, and neurocomputation.

Third, the GUIs can operate in tandem with command execution in Jupyter notebooks (see also Figure 2b, bottom center). Consequently, fly brain pathways and circuit diagrams can be equivalently processed using API calls from Python, thereby ensuring the reproducibility of the exploration of similar datasets with minimal modifications. The Neurokernel Execution Engine (Givon and Lazar, 2016) provides circuit execution on multiple computing nodes/GPUs. The tight integration in the database also allows the execution engine to fetch executable circuits directly from the NeuroArch Database. The tight integration between NeuroArch and Neurokernel is reinforced and made user transparent by NeuroMynerva.

Exploration, analysis, execution, comparison, and evaluation of circuit models, either among versions developed by one’s own, or among those published in literature, are often critical steps toward discovering the functional logic of brain circuits. Six types of explorations, analyses, comparisons, and evaluations are of particular interest. First, build and explore the structure of fly brain circuits with English queries (Use Case 1). Second, explore the structure and function of yet to be discovered brain circuits (Use Case 2). Third, interactively explore executable circuit models (Use Case 3). Fourth, starting from a given dataset and after implementing a number of circuit models published in the literature, analyze and compare these under the same evaluation criteria (Use Case 4). Fifth, automate the construction of executable circuit models from datasets gathered by different labs and analyze, compare, and evaluate the different circuit realizations (Use Case 5). Sixth, analyze, compare, and evaluate fruit fly brain circuit models at different developmental stages (Use Case 6).

In what follows, we present results, supported by the FlyBrainLab Circuits Libraries (see Materials and methods), demonstrating the comprehensive exploration, execution, analysis, comparison, and evaluation capability of FlyBrainLab. While our emphasis here is on building executable circuit models informed by the connectome/synaptome of the fruit fly brain, these libraries together with sensory neuron activity data serve as entry points for an in-depth exploration, execution, analysis, comparison, and evaluation of the functional logic of the fruit fly brain.

Historically, a large number of visualization and computational tools have been developed primarily designed for either neurobiological studies (see Figure 1 (left)) or computational studies (see Figure 1 (right)). These are briefly discussed below.

The computational neuroscience community has invested a significant amount of effort in developing tools for analyzing and evaluating model neural circuits. A number of simulation engines have been developed, including general simulators such as NEURON (Hines and Carnevale, 1997), NEST (Gewaltig and Diesmann, 2007), Brian (Stimberg et al., 2019), Nengo (Bekolay et al., 2014), Neurokernel (Givon and Lazar, 2016), DynaSim (Sherfey et al., 2018), and the ones that specialize in multi-scale simulation, for example MOOSE (Ray and Bhalla, 2008), in compartmental models, for example ARBOR (Akar et al., 2019), and in fMRI-scale simulation for example The Virtual Brain (Sanz Leon et al., 2013; Melozzi et al., 2017). Other tools improve the accessibility to these simulators by (i) facilitating the creation of large-scale neural networks, for example BMTK (Dai et al., 2020a) and NetPyNE (Dura-Bernal et al., 2019), and by (ii) providing a common interface, simplifying the simulation workflow and streamlining parallelization of simulation, for example PyNN (Davison et al., 2008), Arachne (Aleksin et al., 2017), and NeuroManager (Stockton and Santamaria, 2015). To facilitate access and exchange of neurobiological data worldwide, a number of model specification standards have been worked upon in parallel including MorphML (Crook et al., 2007), NeuroML (Gleeson et al., 2010), SpineML (Tomkins et al., 2016), and SONATA (Dai et al., 2020b).

Even with the help of these computational tools, it still takes a substantial amount of manual effort to build executable circuits from real data provided, for example, by model databases such as ModelDB/NeuronDB (Hines et al., 2004) and NeuroArch (Givon et al., 2015). Moreover, with the ever expanding size of the fruit fly brain datasets, it has become more difficult to meet the demand of creating executable circuits that can be evaluated with different datasets. In addition, with very few exceptions, comparisons of circuit models, a standard process in the computer science community, are rarely available in the computational neuroscience literature.

Substantial efforts by the system neuroscience community went into developing tools for visualizing the anatomy of the brain. A number of tools have been developed to provide interactive, web-based interfaces for exploring, visualizing and analyzing fruit fly brain and ventral nerve cord datasets, for both the adult (Chiang et al., 2011; Scheffer et al., 2020) and the larva (Ohyama et al., 2015). These include the FlyCircuit (Chiang et al., 2011), the Fruit Fly Brain Observatory (FFBO/NeuroNLP) (Ukani et al., 2019), Virtual Fly Brain (Milyaev et al., 2012), neuPrintExplorer (Clements et al., 2020), FlyWire (Dorkenwald et al., 2020), and CATMAID (Saalfeld et al., 2009). Similar tools have been developed for other model organisms, such as the Allen Mouse Brain Connectivity Atlas (Oh et al., 2014), the WormAtlas for C. elegans (https://www.wormatlas.org) and the Z Brain for zebra fish (Randlett et al., 2015). A number of projects, for example (Bates et al., 2020), offer a more specialized capability for visualizing and analyzing neuroanatomy data.

While these tools have significantly improved the access to and exploration of brain data a number of recent efforts started to bridge the gap between neurobiological data and computational modeling including the Geppetto (Cantarelli et al., 2018), the OpenWorm (Szigeti et al., 2014) and the Open Source Brain (Gleeson et al., 2019) initiatives and the Brain Simulation Platform of the Human Brain Project (Einevoll et al., 2019). However, without information linking circuit activity/computation to the structure of the underlying neuronal circuits, understanding the function of brain circuits remains elusive. Lacking a systematic method of automating the process of creating and exploring the function of executable circuits at the brain or system scale levels hinders the application of these tools when composing more complex circuits. Furthermore, these tools fall short of offering the capability of generating static circuit diagrams, let alone interactive ones. The experience of VLSI design, analysis, and evaluation of computer circuits might be instructive here. An electronic circuit engineer reads a circuit diagram of a chip, rather than the 3D structure of the tape-out, to understand its function, although the latter ultimately realizes it. Similarly, visualization of a biological circuit alone, while powerful and intuitive for building a neural circuit, provides little insights into the function of the circuit. While simulations can be done without a circuit diagram, understanding how an executable circuit leads to its function remains elusive.

The tools discussed above all fall short of offering an integrated infrastructure that can effectively leverage the ever expanding neuroanatomy, genetic and neurophysiology data for creating and exploring executable fly brain circuits. Creating circuit simulations from visualized data remains a major challenge and requires extraordinary effort in practice as amply demonstrated by the Allen Brain Observatory (de Vries et al., 2020). The need to accelerate the pace of discovery of the functional logic of the brain of model organisms has entered a center stage in brain research.

FlyBrainLab is uniquely positioned to accelerate the discovery of the functional logic of the Drosophila brain. Its interactive architecture seamlessly integrates and brings together computational models with neuroanatomical, neurogenetic, and neurophysiological data, changing the organization of fruit fly brain data from a group of independently created datasets, arrays, and tables, into a well-structured data and executable circuit repository, with a simple API for accessing data in different datasets. Current data integration extensively focuses on connectomics/synaptomics datasets that, as demonstrated, strongly inform the construction of executable circuit models. We will continue to expand the capabilities of the NeuroArch database with genetic Gal4 lines (https://gene.neuronlp.fruitflybrain.org) and neurophysiology recordings including our own (http://antenna.neuronlp.fruitflybrain.org/). How to construct executable models of brain circuits using genetic and neurophysiology data sets is not the object of this publication and will be discussed elsewhere. Pointers to our initial work are given below.

As detailed here, the FlyBrainLab UI supports a highly intuitive and automated workflow that streamlines the 3D exploration and visualization of fly brain circuits, and the interactive exploration of the functional logic of executable circuits created directly from the analyzed fly brain data. In conjunction with the capability of visually constructing circuits, speeding up the process of creating interactive executable circuit diagrams can substantially reduce the exploratory development cycle.

The FlyBrainLab Utility and Circuit Libraries accelerate the creation of models of executable circuits. The Utility Libraries (detailed in the Appendix 2) help untangle the graph structure of neural circuits from raw connectome and synaptome data. The Circuit Libraries (detailed in the Appendix 3) facilitate the exploration of neural circuits of the neuropils of the central complex and, the development and implementation of models of the adult and larva fruit fly early olfactory system.

Importantly, to transcend the limitations of the connectome, FlyBrainLab is providing Circuit Libraries for molecular transduction in sensory coding (detailed in the Appendix 3), including models of sensory transduction and neuron activity data (Lazar et al., 2015a; Lazar et al., 2015b; Lazar and Yeh, 2020). These libraries serve as entry points for discovery of circuit function in the sensory systems of the fruit fly (Lazar and Yeh, 2019; Lazar et al., 2020a). They also enable the biological validation of developed executable circuits within the same platform.

The modular software architecture underlying FlyBrainLab provides substantial flexibility and scalability for the study of the larva and adult fruit fly brain. As more data becomes available, we envision that the entire central nervous system of the fruit fly can be readily explored with FlyBrainLab. Furthermore, the core of the software and the workflow enabled by the FlyBrainLab for accelerating discovery of Drosophila brain functions can be adapted in the near term to other model organisms including the zebrafish and bee.

The FlyBrainLab interactive computing platform tightly integrates tools enabling the morphological visualization and exploration of large connectomics/synaptomics datasets, interactive circuit construction and visualization and multi-GPU execution of neural circuit models for in silico experimentation. The tight integration is achieved with a comprehensive open software architecture and libraries to aid data analysis, creation of executable circuits and exploration of their functional logic.

# query for LPTC

res1 = client.executeNLPquery("show LPTC")

# color the neurons in the previous query
_ = client.executeNLPquery('color orange')

# query for GLN on the right hemisphere using regular expression 
res2 = client.executeNLPquery("add /rGLN(.*)R(.*)/r")

# color the neurons in the previous query
_ = client.executeNLPquery("color cyan") 

# get the unique names of the GLNs
gln = [v['uname'] for v in res2.neurons.values()]

# query using NeuroArch JSON format 
task = {"query": [
          {"action": {"method": {"path_to_neurons": {
              "pass_through": gln,
              "max_hops": 2,
              "synapse_threshold": 5
          }}},
          "object": {"state": 1}}],
        "format": "morphology",
        "verb": "add"
}

res3 = client.executeNAquery(task)
_ = client.executeNLPquery("color red")

Use Case 4: analyzing, evaluating, and comparing circuit models of the fruit fly central complex

Request a detailed protocol

Model A (Givon et al., 2017; Figure 6a), Model B (Kakaria and de Bivort, 2017; Figure 6b) and Model C (Su et al., 2017; Figure 6c) were implemented using the CXcircuits Library (see also Appendix 3). A wild-type fruit fly CX circuit diagram based on model A was created in the SVG format and made interactive in the NeuroGFX window. The neurons modeled in the circuit diagram were obtained by querying all the neurons of the CX neuropils in the FlyCircuit dataset. The innervation pattern of each neuron was obtained from Lin et al., 2013 and visually examined in the NeuroNLP window. Based on the assumptions made for each model, a standard name was assigned to the model of the neuron according to the naming scheme adopted in the CXcircuits Library. The neurons with missing morphologies in the FlyCircuit dataset were augmented with the data available in the literature (Wolff et al., 2015; Lin et al., 2013).

This all encompassing circuit diagram was then adapted to the other models. Since the assumptions about the subregions that neurons receive inputs from and output to are different in each circuit model, slightly different names may be assigned to neurons in different circuit models. The complete list of modeled neurons of the three models are provided in Supplementary file 1 ‘CX_models.xlsx’, along with their corresponding neurons in the FlyCircuit dataset. The CXcircuits Library also uses this list to enable synchronization of the neurons visualized in the NeuroNLP window with the neurons represented in the NeuroGFX window.

All three models include the same core subcircuits for modeling the Protocerebral Bridge - Ellipsoid Body (PB-EB) interaction. The core subcircuits include three cell types, namely, the PB-EB-LAL, PB-EB-NO, and EB-LAL-PB neurons (NO - Noduli, LAL - Lateral Accessory Lobe, see also Givon et al., 2017 for a list of synonyms of each neuron class). These cells innervate three neuropils, either PB, EB and LAL or PB, EB, and NO. Note that only synapses within PB and EB are considered. For model A, this is achieved by removing all neurons that do not belong to the core PB-EB circuit. This can be directly performed on the circuit diagram in the NeuroGFX window or by using the CXcircuits API. Model B includes an additional cell type, the PB local neurons that introduce global inhibition to the PB-EB circuit. Model C does not include PB local neurons, but models 3 types of ring neurons that innervate the EB. Both PB local neurons and ring neurons are present in model A. However, except for their receptive fields, all ring neurons in model A are the same (see below). Figure 9 depicts the correspondence established between the morphology of example neurons and their respective representation in the overall circuit diagram.

Figure 9

Download asset Open asset

In Model C, the subcircuit consisting of the PB-EB-LAL and EB-LAL-PB neurons was claimed to give rise to the persistent bump activity while the interconnect between PB-EB-NO and EB-LAL-PB allowed the bump to shift in darkness. To better compare with the other two models that did not model the shift in darkness, PB-EB-NO neurons were interactively disabled from the diagram.

For a single vertical bar presented to the fly at the position shown in Figure 6 (d1) (see also the flattened visual input in Figure 6 (d2), the PB glomeruli or the EB wedges innervated by neurons of each of the three circuit models that receive injected current or external spike inputs are, respectively, highlighted in Figure 6 (a3, b3, c3). The CXcircuit Library generates a set of visual stimuli and computes the spike train and/or the injected current inputs to each of the three models.

For model A (Givon et al., 2017), each PB glomerulus is endowed with a rectangular receptive field that covers 20° in azimuth and the entire elevation. Together, the receptive fields of all PB glomeruli tile the 360° azimuth. All PB neurons with dendrites in a glomerulus, including the PB-EB-LAL and PB-EB-NO neurons, receive the visual stimulus filtered by the receptive field as an injected current. Additionally, each Bulb (BU) microglomerulus is endowed with a Gaussian receptive field with a standard deviation of 9° in both azimuth and elevation. The ring neuron innervating a microglomerulus receives the filtered visual stimulus as an injected current (see also the arrows in Figure 6 (a3)). Neuron dynamics follow the Leaky Integrate-and-Fire (LIF) neuron model

(1) $C^i\frac{d{V}^i}{dt}=-\frac{V^i-V_0^i}{R^i}+I^i,$

where $V^i$ is the membrane voltage of the $i$ th neuron, $C^i$ is the membrane capacitance, $V_0^i$ is the resting potential, $R^i$ is the resistance, and $I^i$ is the synaptic current. Upon reaching the threshold voltage $V_{th}^i$, each neuron’s, membrane voltage is reset to $V_r^i$. Synapses are modeled as $\alpha$-synapses with dynamics given by the differential equations

(2) ${\displaystyle \begin{array}{ll}{\displaystyle g^i(t)}& {\displaystyle ={\overline{g}}^i{s}^i(t)}\\ {\displaystyle \frac{d{s}^i}{dt}(t)}& {\displaystyle =h^i(t)1_{[t\ge 0]}(t)}\\ {\displaystyle \frac{d{h}^i}{dt}(t)}& {\displaystyle =-(a_r^i+a_d^i)h(t)-a_r^i{a}_d^i{s}^i+a_r^i{a}_d^i\sum _k\delta (t-t_k^i),}\end{array}}$

where ${\overline{g}}^i$ is a scaling factor, $a_r^i$ and $a_d^i$ are, respectively, the rise and decay time of the synapse, $1_{[t\ge 0]}(t)$ is the Heaviside function and $\delta (t)$ is the Dirac function. $\delta (t-t_k^i)$ indicates an input spike to the $i$ th synapse at time $t_k^i$.

For Model B (Kakaria and de Bivort, 2017), the receptive field of each of the 16 EB wedges covers 22.5° in azimuth. All EB-LAL-PB neurons that innervate a wedge receive a spike train input whose rate is proportional to the filtered visual stimulus (see also arrow in Figure 6 (b3)). The maximum input spike rate is 120 Hz when the visual stimulus is a bar of width 20° at maximum brightness 1. A 5 Hz background firing is always added even in darkness. Neurons are modeled as LIF with a refractory period of 2.2 ms as suggested in Kakaria and de Bivort, 2017. For synapses, instead of using the postsynaptic current (PSC)-based model described in Kakaria and de Bivort, 2017, the $\alpha$-synapse described above was used and its parameters were chosen such that the time-to-peak and peak value approximately matched that of the PSC-based synapse.

For Model C (Su et al., 2017), the receptive field of each of the 16 EB wedges covers 22.5° in azimuth. Two PB-EB-LAL neurons project to a wedge each from a different PB glomerulus. Input to the Model C circuit is presented to pairs of PB glomeruli (see also arrows in Figure 6 (c3)), and all neurons with dendrites in these two PB glomeruli receive a spike train input at a rate proportional to the filtered visual stimuli, with a maximum 50 Hz when the bar is at maximum brightness 1. Neurons are modeled as LIF neurons with a refractory period of 2 ms (as suggested in Su et al., 2017). Synapses are either modeled by the AMPA/GABAA receptor dynamics as

(3) ${\displaystyle \begin{array}{ll}{\displaystyle g^i(t)}& {\displaystyle ={\overline{g}}^i{s}^i(t)}\\ {\displaystyle \frac{d{s}^i}{dt}(t)}& {\displaystyle =-\frac{s^i(t)}{{\tau }^i}+\sum _k\delta (t-t_k^i),}\end{array}}$

where $g^i(t)$ is the synaptic conductance, ${\tau }^i$ is the time constant, and $s^i(t)$ is the state variable of the $i$ th synapse, or modeled by the NMDA receptor dynamics (Su et al., 2017)

(4) ${\displaystyle \begin{array}{rl}{\displaystyle g^i(t)}& {\displaystyle =\frac{{\overline{g}}^i{s}^i(t)}{1+[M{g}^{2+}{]}^i{e}^{-\frac{0.062V}{3.56}}}}\\ {\displaystyle \frac{d{s}^i}{dt}(t)}& {\displaystyle =-\frac{s^i(t)}{{\tau }^i}+{\alpha }^i\left(1-s^i(t)\right)\sum _k\delta (t-t_k^i),}\end{array}}$

where $g^i(t)$ is the synaptic conductance, ${\overline{g}}^i$ is the maximum conductance, $s^i(t)$ is the state variable, ${\tau }^i$ is the time constant, ${\alpha }^i>0$ is a constant, ${[M{g}^{2+}]}^i$ is the extracellular concentration of $M{g}^{2+}$, respectively, of the $i$ th synapse and $V$ is the membrane voltage of the postsynaptic neuron.

Parameters of the above models can be found in Givon et al., 2017; Kakaria and de Bivort, 2017; Su et al., 2017 and in the CXcircuit Library.

Commonly used models, such as the LIF neuron and the α-synapse, are built-into the Neurokernel Execution Engine. Only the model parameters residing in the NeuroArch Database need to be specified via NeuroArch API. The Neurokernel automatically retrieves the circuit models and their parameters from the NeuroArch Database based on the last queried circuit model. For models that are not yet built-into the Neurokernel Execution Engine, such as the PSC-based model in Model B, users must provide an implementation supported by the Neurodriver API.

The 35 s visual stimulus, depicted in Figure 6 (d3), was presented to all three models. A bright vertical bar moves back and forth across the entire visual field while a second bar with lower brightness is presented at a fixed position. Figure 6 (d3) (bottom) depicts the time evolution of the visual input.

To visualize the response of the three executable circuits, the mean firing rate $r^j(t)$ of all EB-LAL-PB neurons that innervate the $j$ th EB wedge was calculated following Su et al., 2017.

(5) ${\displaystyle r^j(t)=\frac{1}{N^j}\sum _{i\in {\mathbb{I}}^j}\left(\sum _k\delta (t-t_k^i)\ast e^{-\frac{t}{0.7215}}\right),}$

where ∗ denotes the convolution operator, ${?}^j$ is the index set of EB-LAL-PB neurons that innervate the $j$ th EB wedge, whose cardinality is $N^j$, and $t_k^i$ is the time of kth spike generated by ith neuron. CXcircuit Library provides utilities to visualize the circuit response.

Jupyter notebooks for Models A, B and C used to generate Video 1 are available at https://github.com/FlyBrainLab/CXcircuits/tree/master/notebooks/elife20.

General information about the FlyBrainLab is available at https://www.fruitflybrain.org. Stable and tested FlyBrainLab installation instructions are available at https://github.com/FlyBrainLab/FlyBrainLab. An overview of the FlyBrainLab resources can be found at the FlyBrainLab Resource wiki page at https://github.com/FlyBrainLab/FlyBrainLab/wiki/FlyBrainLab-Resources. It includes links to individual code repositories for components, libraries and tutorials. The NeuroArch Database hosting publicly available FlyCircuit, Hemibrain, Medulla 7-column and Larva L1EM datasets can be downloaded from https://github.com/FlyBrainLab/datasets. The same repository provides Jupyter notebooks for loading publicly available datasets, such as the FlyCircuit dataset with inferred connectivity, the Hemibrain dataset, the Medulla 7-column dataset and the Larva L1 EM dataset.

1. 1. Chiang AS
   2. et al.

   (2011) FlyCircuit DB

   FlyCircuit.

   https://doi.org/10.1016/j.cub.2010.11.056
2. 1. Ohyama T
   2. et al.

   (2015) CATMAID

   L1EM.

   https://doi.org/10.1038/nature14297
3. 1. Scheffer LK
   2. et al.

   (2020) neuPrint

   Hemibrain.

   https://doi.org/10.7554/eLife.57443
4. 1. Takemura SY
   2. et al.

   (2015) github

   Medulla 7 Column Data.

   https://doi.org/10.1073/pnas.1509820112

1. Preprint

   1. Akar NA
   2. Ben Cumming VK
   3. Küsters A
   4. Klijn W
   5. Peyser A

   (2019) Arbor - a morphologically-detailed neural network simulation library for contemporary high-performance computing architectures

   arXiv.

   https://arxiv.org/abs/1901.07454

   • Google Scholar
2. 1. Aleksin SG
   2. Zheng K
   3. Rusakov DA
   4. Savtchenko LP

   (2017) ARACHNE: a neural-neuroglial network builder with remotely controlled parallel computing

   PLOS Computational Biology 13:e1005467.

   https://doi.org/10.1371/journal.pcbi.1005467

   • PubMed
   • Google Scholar
3. 1. Ascoli GA
   2. Donohue DE
   3. Halavi M

   (2007) NeuroMorpho.Org: a central resource for neuronal morphologies

   Journal of Neuroscience 27:9247–9251.

   https://doi.org/10.1523/JNEUROSCI.2055-07.2007

   • PubMed
   • Google Scholar
4. 1. Bates AS
   2. Manton JD
   3. Jagannathan SR
   4. Costa M
   5. Schlegel P
   6. Rohlfing T
   7. Jefferis GS

   (2020) The Natverse, a versatile toolbox for combining and analysing neuroanatomical data

   eLife 9:e53350.

   https://doi.org/10.7554/eLife.53350

   • PubMed
   • Google Scholar
5. 1. Bekolay T
   2. Bergstra J
   3. Hunsberger E
   4. Dewolf T
   5. Stewart TC
   6. Rasmussen D
   7. Choo X
   8. Voelker AR
   9. Eliasmith C

   (2014) Nengo: a Python tool for building large-scale functional brain models

   Frontiers in Neuroinformatics 7:48.

   https://doi.org/10.3389/fninf.2013.00048

   • PubMed
   • Google Scholar
6. 1. Berck ME
   2. Khandelwal A
   3. Claus L
   4. Hernandez-Nunez L
   5. Si G
   6. Tabone CJ
   7. Li F
   8. Truman JW
   9. Fetter RD
   10. Louis M
   11. Samuel AD
   12. Cardona A

   (2016) The wiring diagram of a glomerular olfactory system

   eLife 5:e14859.

   https://doi.org/10.7554/eLife.14859

   • PubMed
   • Google Scholar
7. 1. Blondel VD
   2. Guillaume J-L
   3. Lambiotte R
   4. Lefebvre E

   (2008)

   Fast unfolding of communities in large networks

   Journal of Statistical Mechanics: Theory and Experiment 2008:P10008.

   • Google Scholar
8. 1. Cantarelli M
   2. Marin B
   3. Quintana A
   4. Earnshaw M
   5. Court R
   6. Gleeson P
   7. Dura-Bernal S
   8. Silver RA
   9. Idili G

   (2018) Geppetto: a reusable modular open platform for exploring neuroscience data and models

   Philosophical Transactions of the Royal Society B: Biological Sciences 373:20170380.

   https://doi.org/10.1098/rstb.2017.0380

   • Google Scholar
9. 1. Chiang AS
   2. Lin CY
   3. Chuang CC
   4. Chang HM
   5. Hsieh CH
   6. Yeh CW
   7. Shih CT
   8. Wu JJ
   9. Wang GT
   10. Chen YC
   11. Wu CC
   12. Chen GY
   13. Ching YT
   14. Lee PC
   15. Lin CY
   16. Lin HH
   17. Wu CC
   18. Hsu HW
   19. Huang YA
   20. Chen JY
   21. Chiang HJ
   22. Lu CF
   23. Ni RF
   24. Yeh CY
   25. Hwang JK

   (2011) Three-dimensional reconstruction of brain-wide wiring networks in Drosophila at single-cell resolution

   Current Biology 21:1–11.

   https://doi.org/10.1016/j.cub.2010.11.056

   • PubMed
   • Google Scholar
10. Preprint

    1. Clements J
    2. Dolafi T
    3. Umayam L
    4. Neubarth NL
    5. Berg S
    6. Scheffer LK
    7. Plaza SM

    (2020) neuPrint: analysis tools for EM connectomics

    bioRxiv.

    https://doi.org/10.1101/2020.01.16.909465

    • Google Scholar
11. 1. Crook S
    2. Gleeson P
    3. Howell F
    4. Svitak J
    5. Silver RA

    (2007) MorphML: level 1 of the NeuroML standards for neuronal morphology data and model specification

    Neuroinformatics 5:96–104.

    https://doi.org/10.1007/s12021-007-0003-6

    • PubMed
    • Google Scholar
12. 1. Dai K
    2. Gratiy SL
    3. Billeh YN
    4. Xu R
    5. Cai B
    6. Cain N
    7. Rimehaug AE
    8. Stasik AJ
    9. Einevoll GT
    10. Mihalas S
    11. Koch C
    12. Arkhipov A

    (2020a) Brain modeling ToolKit: an open source software suite for multiscale modeling of brain circuits

    PLOS Computational Biology 16:e1008386.

    https://doi.org/10.1371/journal.pcbi.1008386

    • PubMed
    • Google Scholar
13. 1. Dai K
    2. Hernando J
    3. Billeh YN
    4. Gratiy SL
    5. Planas J
    6. Davison AP
    7. Dura-Bernal S
    8. Gleeson P
    9. Devresse A
    10. Dichter BK
    11. Gevaert M
    12. King JG
    13. Van Geit WAH
    14. Povolotsky AV
    15. Muller E
    16. Courcol JD
    17. Arkhipov A

    (2020b) The SONATA data format for efficient description of large-scale network models

    PLOS Computational Biology 16:e1007696.

    https://doi.org/10.1371/journal.pcbi.1007696

    • PubMed
    • Google Scholar
14. 1. Davis FP
    2. Nern A
    3. Picard S
    4. Reiser MB
    5. Rubin GM
    6. Eddy SR
    7. Henry GL

    (2020) A genetic, genomic, and computational resource for exploring neural circuit function

    eLife 9:e50901.

    https://doi.org/10.7554/eLife.50901

    • PubMed
    • Google Scholar
15. 1. Davison AP
    2. Brüderle D
    3. Eppler J
    4. Kremkow J
    5. Muller E
    6. Pecevski D
    7. Perrinet L
    8. Yger P

    (2008) PyNN: a common interface for neuronal network simulators

    Frontiers in Neuroinformatics 2:11.

    https://doi.org/10.3389/neuro.11.011.2008

    • PubMed
    • Google Scholar
16. 1. de Vries SEJ
    2. Lecoq JA
    3. Buice MA
    4. Groblewski PA
    5. Ocker GK
    6. Oliver M
    7. Feng D
    8. Cain N
    9. Ledochowitsch P
    10. Millman D
    11. Roll K
    12. Garrett M
    13. Keenan T
    14. Kuan L
    15. Mihalas S
    16. Olsen S
    17. Thompson C
    18. Wakeman W
    19. Waters J
    20. Williams D
    21. Barber C
    22. Berbesque N
    23. Blanchard B
    24. Bowles N
    25. Caldejon SD
    26. Casal L
    27. Cho A
    28. Cross S
    29. Dang C
    30. Dolbeare T
    31. Edwards M
    32. Galbraith J
    33. Gaudreault N
    34. Gilbert TL
    35. Griffin F
    36. Hargrave P
    37. Howard R
    38. Huang L
    39. Jewell S
    40. Keller N
    41. Knoblich U
    42. Larkin JD
    43. Larsen R
    44. Lau C
    45. Lee E
    46. Lee F
    47. Leon A
    48. Li L
    49. Long F
    50. Luviano J
    51. Mace K
    52. Nguyen T
    53. Perkins J
    54. Robertson M
    55. Seid S
    56. Shea-Brown E
    57. Shi J
    58. Sjoquist N
    59. Slaughterbeck C
    60. Sullivan D
    61. Valenza R
    62. White C
    63. Williford A
    64. Witten DM
    65. Zhuang J
    66. Zeng H
    67. Farrell C
    68. Ng L
    69. Bernard A
    70. Phillips JW
    71. Reid RC
    72. Koch C

    (2020) A large-scale standardized physiological survey reveals functional organization of the mouse visual cortex

    Nature Neuroscience 23:138–151.

    https://doi.org/10.1038/s41593-019-0550-9

    • PubMed
    • Google Scholar
17. Preprint

    1. Dorkenwald S
    2. McKellar C
    3. Macrina T
    4. Kemnitz N
    5. Lee K
    6. Lu R
    7. Wu J
    8. Popovych S
    9. Mitchell E
    10. Nehoran B
    11. Jia Z
    12. Alexander Bae J
    13. Mu S
    14. Ih D
    15. Castro M
    16. Ogedengbe O
    17. Halageri A
    18. Ashwood Z
    19. Zung J
    20. Brittain D
    21. Collman F
    22. Schneider-Mizell C
    23. Jordan C
    24. Silversmith W
    25. Baker C
    26. Deutsch D
    27. Encarnacion-Rivera L
    28. Kumar S
    29. Burke A
    30. Gager J
    31. Hebditch J
    32. Koolman S
    33. Moore M
    34. Morejohn S
    35. Ben Silverman KW
    36. Willie R
    37. Yu SC
    38. Murthy M
    39. Sebastian Seung H

    (2020) FlyWire: online community for whole-brain connectomics

    bioRxiv.

    https://doi.org/10.1101/2020.08.30.274225

    • Google Scholar
18. 1. Dura-Bernal S
    2. Suter BA
    3. Gleeson P
    4. Cantarelli M
    5. Quintana A
    6. Rodriguez F
    7. Kedziora DJ
    8. Chadderdon GL
    9. Kerr CC
    10. Neymotin SA
    11. McDougal RA
    12. Hines M
    13. Shepherd GM
    14. Lytton WW

    (2019) NetPyNE, a tool for data-driven multiscale modeling of brain circuits

    eLife 8:e44494.

    https://doi.org/10.7554/eLife.44494

    • PubMed
    • Google Scholar
19. 1. Einevoll GT
    2. Destexhe A
    3. Diesmann M
    4. Grün S
    5. Jirsa V
    6. de Kamps M
    7. Migliore M
    8. Ness TV
    9. Plesser HE
    10. Schürmann F

    (2019) The scientific case for brain simulations

    Neuron 102:735–744.

    https://doi.org/10.1016/j.neuron.2019.03.027

    • PubMed
    • Google Scholar
20. 1. Ellson J
    2. Gansner E
    3. Koutsofios L
    4. North SC
    5. Woodhull G

    (2001)

    International Symposium on Graph Drawing

    pages 483–484, Graphviz—open source graph drawing tools, International Symposium on Graph Drawing, Springer.

    • Google Scholar
21. 1. Fischbach K-F
    2. Dittrich APM

    (1989) The optic lobe of Drosophila melanogaster. I. A Golgi analysis of wild-type structure

    Cell and Tissue Research 258:441–475.

    https://doi.org/10.1007/BF00218858

    • PubMed
    • Google Scholar
22. 1. Gewaltig M-O
    2. Diesmann M

    (2007) NEST (NEural simulation tool)

    Scholarpedia 2:1430.

    https://doi.org/10.4249/scholarpedia.1430

    • Google Scholar
23. 1. Givon LE
    2. Lazar AA
    3. Ukani NH

    (2014) Neuroarch: a graph-based platform for constructing and querying models of the fruit fly brain architecture

    Frontiers in Neuroinformatics 8:e00042.

    https://doi.org/10.3389/conf.fninf.2014.18.00042

    • Google Scholar
24. 1. Givon LE
    2. Lazar AA
    3. Ukani NH

    (2015) Neuroarch: a graph db for querying and executing fruit fly brain circuits

    Neurokernel Request for Comments, Neurokernel RFC # 5:.

    https://doi.org/10.5281/zenodo.44225

    • Google Scholar
25. 1. Givon LE
    2. Lazar AA
    3. Yeh CH

    (2017) Generating executable models of the Drosophila central complex

    Frontiers in Behavioral Neuroscience 11:102.

    https://doi.org/10.3389/fnbeh.2017.00102

    • PubMed
    • Google Scholar
26. 1. Givon LE
    2. Lazar AA

    (2016) Neurokernel: an open source platform for emulating the fruit fly brain

    PLOS ONE 11:e0146581.

    https://doi.org/10.1371/journal.pone.0146581

    • PubMed
    • Google Scholar
27. 1. Gleeson P
    2. Crook S
    3. Cannon RC
    4. Hines ML
    5. Billings GO
    6. Farinella M
    7. Morse TM
    8. Davison AP
    9. Ray S
    10. Bhalla US
    11. Barnes SR
    12. Dimitrova YD
    13. Silver RA

    (2010) NeuroML: a language for describing data driven models of neurons and networks with a high degree of biological detail

    PLOS Computational Biology 6:e1000815.

    https://doi.org/10.1371/journal.pcbi.1000815

    • PubMed
    • Google Scholar
28. 1. Gleeson P
    2. Cantarelli M
    3. Marin B
    4. Quintana A
    5. Earnshaw M
    6. Sadeh S
    7. Piasini E
    8. Birgiolas J
    9. Cannon RC
    10. Cayco-Gajic NA
    11. Crook S
    12. Davison AP
    13. Dura-Bernal S
    14. Ecker A
    15. Hines ML
    16. Idili G
    17. Lanore F
    18. Larson SD
    19. Lytton WW
    20. Majumdar A
    21. McDougal RA
    22. Sivagnanam S
    23. Solinas S
    24. Stanislovas R
    25. van Albada SJ
    26. van Geit W
    27. Silver RA

    (2019) Open source brain: a collaborative resource for visualizing, analyzing, simulating, and developing standardized models of neurons and circuits

    Neuron 103:395–411.

    https://doi.org/10.1016/j.neuron.2019.05.019

    • PubMed
    • Google Scholar
29. 1. Haag J
    2. Mishra A
    3. Borst A

    (2017) A common directional tuning mechanism of Drosophila motion-sensing neurons in the ON and in the OFF pathway

    eLife 6:e29044.

    https://doi.org/10.7554/eLife.29044

    • PubMed
    • Google Scholar
30. Book

    1. Hausen K

    (1984) The lobula-complex of the fly: structure, function and significance in visual behaviour

    In: Ali M. A, editors. Photoreception and Vision in Invertebrates, NATO ASI Series (Series A: Life Sciences), Chapter the Lobula-Complex of the Fly: Structure, Function and Significance in Visual Behaviour. Springer. pp. 523–559.

    https://doi.org/10.1007/978-1-4613-2743-1_15

    • Google Scholar
31. 1. Hines ML
    2. Morse T
    3. Migliore M
    4. Carnevale NT
    5. Shepherd GM

    (2004) ModelDB: a database to support computational neuroscience

    Journal of Computational Neuroscience 17:7–11.

    https://doi.org/10.1023/B:JCNS.0000023869.22017.2e

    • PubMed
    • Google Scholar
32. 1. Hines ML
    2. Carnevale NT

    (1997) The NEURON simulation environment

    Neural Computation 9:1179–1209.

    https://doi.org/10.1162/neco.1997.9.6.1179

    • PubMed
    • Google Scholar
33. 1. Horne JA
    2. Langille C
    3. McLin S
    4. Wiederman M
    5. Lu Z
    6. Xu CS
    7. Plaza SM
    8. Scheffer LK
    9. Hess HF
    10. Meinertzhagen IA

    (2018) A resource for the Drosophila antennal lobe provided by the connectome of glomerulus VA1v

    eLife 7:e37550.

    https://doi.org/10.7554/eLife.37550

    • PubMed
    • Google Scholar
34. 1. Huang YC
    2. Wang CT
    3. Su TS
    4. Kao KW
    5. Lin YJ
    6. Chuang CC
    7. Chiang AS
    8. Lo CC

    (2018) A Single-Cell level and Connectome-Derived computational model of the Drosophila Brain

    Frontiers in Neuroinformatics 12:99.

    https://doi.org/10.3389/fninf.2018.00099

    • PubMed
    • Google Scholar
35. 1. Jenett A
    2. Rubin GM
    3. Ngo TT
    4. Shepherd D
    5. Murphy C
    6. Dionne H
    7. Pfeiffer BD
    8. Cavallaro A
    9. Hall D
    10. Jeter J
    11. Iyer N
    12. Fetter D
    13. Hausenfluck JH
    14. Peng H
    15. Trautman ET
    16. Svirskas RR
    17. Myers EW
    18. Iwinski ZR
    19. Aso Y
    20. DePasquale GM
    21. Enos A
    22. Hulamm P
    23. Lam SC
    24. Li HH
    25. Laverty TR
    26. Long F
    27. Qu L
    28. Murphy SD
    29. Rokicki K
    30. Safford T
    31. Shaw K
    32. Simpson JH
    33. Sowell A
    34. Tae S
    35. Yu Y
    36. Zugates CT

    (2012) A GAL4-driver line resource for Drosophila neurobiology

    Cell Reports 2:991–1001.

    https://doi.org/10.1016/j.celrep.2012.09.011

    • PubMed
    • Google Scholar
36. 1. Kakaria KS
    2. de Bivort BL

    (2017) Ring attractor dynamics emerge from a spiking model of the entire protocerebral bridge

    Frontiers in Behavioral Neuroscience 11:8.

    https://doi.org/10.3389/fnbeh.2017.00008

    • PubMed
    • Google Scholar
37. 1. Kim AJ
    2. Lazar AA
    3. Slutskiy YB

    (2011) System identification of Drosophila olfactory sensory neurons

    Journal of Computational Neuroscience 30:143–161.

    https://doi.org/10.1007/s10827-010-0265-0

    • PubMed
    • Google Scholar
38. 1. Kim AJ
    2. Lazar AA
    3. Slutskiy YB

    (2015) Projection neurons in Drosophila antennal lobes signal the acceleration of odor concentrations

    eLife 4:e06651.

    https://doi.org/10.7554/eLife.06651

    • PubMed
    • Google Scholar
39. 1. Kim SS
    2. Rouault H
    3. Druckmann S
    4. Jayaraman V

    (2017) Ring attractor dynamics in the Drosophila central brain

    Science 356:849–853.

    https://doi.org/10.1126/science.aal4835

    • PubMed
    • Google Scholar
40. 1. Kreher SA
    2. Kwon JY
    3. Carlson JR

    (2005) The molecular basis of odor coding in the Drosophila larva

    Neuron 46:445–456.

    https://doi.org/10.1016/j.neuron.2005.04.007

    • PubMed
    • Google Scholar
41. 1. Lazar AA
    2. Psychas K
    3. Ukani NH
    4. Zhou Y

    (2015a) A parallel processing model of the Drosophila retina

    Neurokernel Request for Comments, Neurokernel RFC # 3:.

    https://doi.org/10.5281/zenodo.30036

    • Google Scholar
42. Conference

    1. Lazar AA
    2. Psychas K
    3. Ukani NH
    4. Zhou Y

    (2015b) Retina of the fruit fly eyes: a detailed simulation model

    BMC Neuroscience 16(Suppl 1): P301, 24th Annual Computational Neurocience Meeting. July 18-23, 2015, Prague, Czech Republic.

    https://doi.org/10.1186/1471-2202-16-S1-P301

    • Google Scholar
43. Conference

    1. Lazar AA
    2. Liu T
    3. Yeh C-H

    (2020a) An odorant encoding machine for sampling, reconstruction and robust representation of odorant identity

    IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP 2020). pp. 1743–1747.

    https://doi.org/10.1109/ICASSP40776.2020.9054588

    • Google Scholar
44. 1. Lazar AA
    2. Ukani NH
    3. Zhou Y

    (2020b) Sparse identification of contrast gain control in the fruit fly photoreceptor and amacrine cell layer

    The Journal of Mathematical Neuroscience 10:3.

    https://doi.org/10.1186/s13408-020-0080-5

    • PubMed
    • Google Scholar
45. Conference

    1. Lazar AA
    2. Yeh C-H

    (2019) Predictive coding in the Drosophila antennal lobe

    BMC Neuroscience, 20(Suppl 1):P346, 2019. 28th Annual Computational Neuroscience Meeting, July 13-17, 2019, Barcelona, Spain.

    https://doi.org/10.1186/s12868-019-0538-0

    • Google Scholar
46. 1. Lazar AA
    2. Yeh C-H

    (2020) A molecular odorant transduction model and the complexity of spatio-temporal encoding in the Drosophila antenna

    PLOS Computational Biology 16:e1007751. Original version posted on bioRxiv (https://doi.org/10.1101/237669), December 2017.

    https://doi.org/10.1371/journal.pcbi.1007751

    • PubMed
    • Google Scholar
47. 1. Li J
    2. Mahoney BD
    3. Jacob MS
    4. Caron SJC

    (2020a) Visual input into the Drosophila melanogaster mushroom body

    Cell Reports 32:108138.

    https://doi.org/10.1016/j.celrep.2020.108138

    • PubMed
    • Google Scholar
48. 1. Li F
    2. Lindsey JW
    3. Marin EC
    4. Otto N
    5. Dreher M
    6. Dempsey G
    7. Stark I
    8. Bates AS
    9. Pleijzier MW
    10. Schlegel P
    11. Nern A
    12. Takemura SY
    13. Eckstein N
    14. Yang T
    15. Francis A
    16. Braun A
    17. Parekh R
    18. Costa M
    19. Scheffer LK
    20. Aso Y
    21. Jefferis GS
    22. Abbott LF
    23. Litwin-Kumar A
    24. Waddell S
    25. Rubin GM

    (2020b) The connectome of the adult Drosophila mushroom body provides insights into function

    eLife 9:e62576.

    https://doi.org/10.7554/eLife.62576

    • PubMed
    • Google Scholar
49. 1. Lin CY
    2. Chuang CC
    3. Hua TE
    4. Chen CC
    5. Dickson BJ
    6. Greenspan RJ
    7. Chiang AS

    (2013) A comprehensive wiring diagram of the protocerebral bridge for visual information processing in the Drosophila brain

    Cell Reports 3:1739–1753.

    https://doi.org/10.1016/j.celrep.2013.04.022

    • PubMed
    • Google Scholar
50. 1. Liu G
    2. Seiler H
    3. Wen A
    4. Zars T
    5. Ito K
    6. Wolf R
    7. Heisenberg M
    8. Liu L

    (2006) Distinct memory traces for two visual features in the Drosophila brain

    Nature 439:551–556.

    https://doi.org/10.1038/nature04381

    • PubMed
    • Google Scholar
51. 1. Liu YY
    2. Slotine JJ
    3. Barabási AL

    (2011) Controllability of complex networks

    Nature 473:167–173.

    https://doi.org/10.1038/nature10011

    • PubMed
    • Google Scholar
52. 1. Maisak MS
    2. Haag J
    3. Ammer G
    4. Serbe E
    5. Meier M
    6. Leonhardt A
    7. Schilling T
    8. Bahl A
    9. Rubin GM
    10. Nern A
    11. Dickson BJ
    12. Reiff DF
    13. Hopp E
    14. Borst A

    (2013) A directional tuning map of Drosophila elementary motion detectors

    Nature 500:212–216.

    https://doi.org/10.1038/nature12320

    • PubMed
    • Google Scholar
53. Preprint

    1. McInnes L
    2. Healy J
    3. Melville J

    (2018) Umap: uniform manifold approximation and projection for dimension reduction

    arXiv.

    https://arxiv.org/abs/1802.03426

    • Google Scholar
54. 1. Melozzi F
    2. Woodman MM
    3. Jirsa VK
    4. Bernard C

    (2017) The virtual mouse brain: a computational neuroinformatics platform to study whole mouse brain dynamics

    Eneuro 4:ENEURO.0111-17.2017.

    https://doi.org/10.1523/ENEURO.0111-17.2017

    • PubMed
    • Google Scholar
55. 1. Milyaev N
    2. Osumi-Sutherland D
    3. Reeve S
    4. Burton N
    5. Baldock RA
    6. Armstrong JD

    (2012) The virtual fly brain browser and query interface

    Bioinformatics 28:411–415.

    https://doi.org/10.1093/bioinformatics/btr677

    • PubMed
    • Google Scholar
56. 1. Modi MN
    2. Shuai Y
    3. Turner GC

    (2020) The Drosophila mushroom body: from architecture to algorithm in a learning circuit

    Annual Review of Neuroscience 43:465–484.

    https://doi.org/10.1146/annurev-neuro-080317-0621333

    • PubMed
    • Google Scholar
57. 1. Münch D
    2. Galizia CG

    (2016) DoOR 2.0--comprehensive mapping of Drosophila melanogaster odorant responses

    Scientific Reports 6:21841.

    https://doi.org/10.1038/srep21841

    • PubMed
    • Google Scholar
58. 1. Oh SW
    2. Harris JA
    3. Ng L
    4. Winslow B
    5. Cain N
    6. Mihalas S
    7. Wang Q
    8. Lau C
    9. Kuan L
    10. Henry AM
    11. Mortrud MT
    12. Ouellette B
    13. Nguyen TN
    14. Sorensen SA
    15. Slaughterbeck CR
    16. Wakeman W
    17. Li Y
    18. Feng D
    19. Ho A
    20. Nicholas E
    21. Hirokawa KE
    22. Bohn P
    23. Joines KM
    24. Peng H
    25. Hawrylycz MJ
    26. Phillips JW
    27. Hohmann JG
    28. Wohnoutka P
    29. Gerfen CR
    30. Koch C
    31. Bernard A
    32. Dang C
    33. Jones AR
    34. Zeng H

    (2014) A mesoscale connectome of the mouse brain

    Nature 508:207–214.

    https://doi.org/10.1038/nature13186

    • PubMed
    • Google Scholar
59. 1. Ohyama T
    2. Schneider-Mizell CM
    3. Fetter RD
    4. Aleman JV
    5. Franconville R
    6. Rivera-Alba M
    7. Mensh BD
    8. Branson KM
    9. Simpson JH
    10. Truman JW
    11. Cardona A
    12. Zlatic M

    (2015) A multilevel multimodal circuit enhances action selection in Drosophila

    Nature 520:633–639.

    https://doi.org/10.1038/nature14297

    • PubMed
    • Google Scholar
60. 1. Olsen SR
    2. Wilson RI

    (2008) Lateral presynaptic inhibition mediates gain control in an olfactory circuit

    Nature 452:956–960.

    https://doi.org/10.1038/nature06864

    • PubMed
    • Google Scholar
61. Preprint

    1. Priebe CE
    2. Park Y
    3. Tang M
    4. Athreya A
    5. Lyzinski V
    6. Vogelstein JT
    7. Qin Y
    8. Ben Cocanougher KE
    9. Zlatic M

    (2017) Semiparametric spectral modeling of the Drosophila connectome

    arXiv.

    https://arxiv.org/abs/1705.03297

    • Google Scholar
62. 1. Randlett O
    2. Wee CL
    3. Naumann EA
    4. Nnaemeka O
    5. Schoppik D
    6. Fitzgerald JE
    7. Portugues R
    8. Lacoste AM
    9. Riegler C
    10. Engert F
    11. Schier AF

    (2015) Whole-brain activity mapping onto a zebrafish brain atlas

    Nature Methods 12:1039–1046.

    https://doi.org/10.1038/nmeth.3581

    • PubMed
    • Google Scholar
63. 1. Ray S
    2. Bhalla US

    (2008) PyMOOSE: interoperable scripting in Python for MOOSE

    Frontiers in Neuroinformatics 2:6.

    https://doi.org/10.3389/neuro.11.006.2008

    • PubMed
    • Google Scholar
64. 1. Rivera-Alba M
    2. Vitaladevuni SN
    3. Mishchenko Y
    4. Mischenko Y
    5. Lu Z
    6. Takemura SY
    7. Scheffer L
    8. Meinertzhagen IA
    9. Chklovskii DB
    10. de Polavieja GG

    (2011) Wiring economy and volume exclusion determine neuronal placement in the Drosophila brain

    Current Biology 21:2000–2005.

    https://doi.org/10.1016/j.cub.2011.10.022

    • PubMed
    • Google Scholar
65. 1. Saalfeld S
    2. Cardona A
    3. Hartenstein V
    4. Tomancak P

    (2009) CATMAID: collaborative annotation toolkit for massive amounts of image data

    Bioinformatics 25:1984–1986.

    https://doi.org/10.1093/bioinformatics/btp266

    • PubMed
    • Google Scholar
66. 1. Sanz Leon P
    2. Knock SA
    3. Woodman MM
    4. Domide L
    5. Mersmann J
    6. McIntosh AR
    7. Jirsa V

    (2013) The virtual brain: a simulator of primate brain network dynamics

    Frontiers in Neuroinformatics 7:10.

    https://doi.org/10.3389/fninf.2013.00010

    • PubMed
    • Google Scholar
67. 1. Saumweber T
    2. Rohwedder A
    3. Schleyer M
    4. Eichler K
    5. Chen YC
    6. Aso Y
    7. Cardona A
    8. Eschbach C
    9. Kobler O
    10. Voigt A
    11. Durairaja A
    12. Mancini N
    13. Zlatic M
    14. Truman JW
    15. Thum AS
    16. Gerber B

    (2018) Functional architecture of reward learning in mushroom body extrinsic neurons of larval Drosophila

    Nature Communications 9:1104.

    https://doi.org/10.1038/s41467-018-03130-1

    • PubMed
    • Google Scholar
68. 1. Scheffer LK
    2. Xu CS
    3. Januszewski M
    4. Lu Z
    5. Takemura SY
    6. Hayworth KJ
    7. Huang GB
    8. Shinomiya K
    9. Maitlin-Shepard J
    10. Berg S
    11. Clements J
    12. Hubbard PM
    13. Katz WT
    14. Umayam L
    15. Zhao T
    16. Ackerman D
    17. Blakely T
    18. Bogovic J
    19. Dolafi T
    20. Kainmueller D
    21. Kawase T
    22. Khairy KA
    23. Leavitt L
    24. Li PH
    25. Lindsey L
    26. Neubarth N
    27. Olbris DJ
    28. Otsuna H
    29. Trautman ET
    30. Ito M
    31. Bates AS
    32. Goldammer J
    33. Wolff T
    34. Svirskas R
    35. Schlegel P
    36. Neace E
    37. Knecht CJ
    38. Alvarado CX
    39. Bailey DA
    40. Ballinger S
    41. Borycz JA
    42. Canino BS
    43. Cheatham N
    44. Cook M
    45. Dreher M
    46. Duclos O
    47. Eubanks B
    48. Fairbanks K
    49. Finley S
    50. Forknall N
    51. Francis A
    52. Hopkins GP
    53. Joyce EM
    54. Kim S
    55. Kirk NA
    56. Kovalyak J
    57. Lauchie SA
    58. Lohff A
    59. Maldonado C
    60. Manley EA
    61. McLin S
    62. Mooney C
    63. Ndama M
    64. Ogundeyi O
    65. Okeoma N
    66. Ordish C
    67. Padilla N
    68. Patrick CM
    69. Paterson T
    70. Phillips EE
    71. Phillips EM
    72. Rampally N
    73. Ribeiro C
    74. Robertson MK
    75. Rymer JT
    76. Ryan SM
    77. Sammons M
    78. Scott AK
    79. Scott AL
    80. Shinomiya A
    81. Smith C
    82. Smith K
    83. Smith NL
    84. Sobeski MA
    85. Suleiman A
    86. Swift J
    87. Takemura S
    88. Talebi I
    89. Tarnogorska D
    90. Tenshaw E
    91. Tokhi T
    92. Walsh JJ
    93. Yang T
    94. Horne JA
    95. Li F
    96. Parekh R
    97. Rivlin PK
    98. Jayaraman V
    99. Costa M
    100. Jefferis GS
    101. Ito K
    102. Saalfeld S
    103. George R
    104. Meinertzhagen IA
    105. Rubin GM
    106. Hess HF
    107. Jain V
    108. Plaza SM

    (2020) A connectome and analysis of the adult Drosophila central brain

    eLife 9:e57443.

    https://doi.org/10.7554/eLife.57443

    • PubMed
    • Google Scholar
69. 1. Seelig JD
    2. Jayaraman V

    (2015) Neural dynamics for landmark orientation and angular path integration

    Nature 521:186–191.

    https://doi.org/10.1038/nature14446

    • PubMed
    • Google Scholar
70. 1. Sengupta B
    2. Stemmler M
    3. Laughlin SB
    4. Niven JE

    (2010) Action potential energy efficiency varies among neuron types in vertebrates and invertebrates

    PLOS Computational Biology 6:e1000840.

    https://doi.org/10.1371/journal.pcbi.1000840

    • PubMed
    • Google Scholar
71. 1. Sherfey JS
    2. Soplata AE
    3. Ardid S
    4. Roberts EA
    5. Stanley DA
    6. Pittman-Polletta BR
    7. Kopell NJ

    (2018) DynaSim: a MATLAB toolbox for neural modeling and simulation

    Frontiers in Neuroinformatics 12:10.

    https://doi.org/10.3389/fninf.2018.00010

    • PubMed
    • Google Scholar
72. 1. Skaggs WE
    2. Knierim JJ
    3. Kudrimoti HS
    4. McNaughton BL

    (1995)

    A model of the neural basis of the rat’s sense of direction

    Advances in Neural Information Processing Systems 7:173–180.

    • PubMed
    • Google Scholar
73. 1. Sokal RR

    (1958)

    A statistical method for evaluating systematic relationships

    Univ. Kansas, Sci. Bull 38:1409–1438.

    • Google Scholar
74. 1. Song Z
    2. Postma M
    3. Billings SA
    4. Coca D
    5. Hardie RC
    6. Juusola M

    (2012) Stochastic, adaptive sampling of information by microvilli in fly photoreceptors

    Current Biology 22:1371–1380.

    https://doi.org/10.1016/j.cub.2012.05.047

    • PubMed
    • Google Scholar
75. 1. Stimberg M
    2. Brette R
    3. Goodman DF

    (2019) Brian 2, an intuitive and efficient neural simulator

    eLife 8:e47314.

    https://doi.org/10.7554/eLife.47314

    • PubMed
    • Google Scholar
76. 1. Stockton DB
    2. Santamaria F

    (2015) NeuroManager: a workflow analysis based simulation management engine for computational neuroscience

    Frontiers in Neuroinformatics 9:24.

    https://doi.org/10.3389/fninf.2015.00024

    • PubMed
    • Google Scholar
77. 1. Stone T
    2. Webb B
    3. Adden A
    4. Weddig NB
    5. Honkanen A
    6. Templin R
    7. Wcislo W
    8. Scimeca L
    9. Warrant E
    10. Heinze S

    (2017) An anatomically constrained model for path integration in the bee brain

    Current Biology 27:3069–3085.

    https://doi.org/10.1016/j.cub.2017.08.052

    • PubMed
    • Google Scholar
78. 1. Su TS
    2. Lee WJ
    3. Huang YC
    4. Wang CT
    5. Lo CC

    (2017) Coupled symmetric and asymmetric circuits underlying spatial orientation in fruit flies

    Nature Communications 8:139.

    https://doi.org/10.1038/s41467-017-00191-6

    • PubMed
    • Google Scholar
79. 1. Sussman DL
    2. Tang M
    3. Fishkind DE
    4. Priebe CE

    (2012) A consistent adjacency spectral embedding for stochastic blockmodel graphs

    Journal of the American Statistical Association 107:1119–1128.

    https://doi.org/10.1080/01621459.2012.699795

    • Google Scholar
80. 1. Szigeti B
    2. Gleeson P
    3. Vella M
    4. Khayrulin S
    5. Palyanov A
    6. Hokanson J
    7. Currie M
    8. Cantarelli M
    9. Idili G
    10. Larson S

    (2014) OpenWorm: an open-science approach to modeling Caenorhabditis elegans

    Frontiers in Computational Neuroscience 8:137.

    https://doi.org/10.3389/fncom.2014.00137

    • PubMed
    • Google Scholar
81. 1. Takemura SY
    2. Xu CS
    3. Lu Z
    4. Rivlin PK
    5. Parag T
    6. Olbris DJ
    7. Plaza S
    8. Zhao T
    9. Katz WT
    10. Umayam L
    11. Weaver C
    12. Hess HF
    13. Horne JA
    14. Nunez-Iglesias J
    15. Aniceto R
    16. Chang LA
    17. Lauchie S
    18. Nasca A
    19. Ogundeyi O
    20. Sigmund C
    21. Takemura S
    22. Tran J
    23. Langille C
    24. Le Lacheur K
    25. McLin S
    26. Shinomiya A
    27. Chklovskii DB
    28. Meinertzhagen IA
    29. Scheffer LK

    (2015) Synaptic circuits and their variations within different columns in the visual system of Drosophila

    PNAS 112:13711–13716.

    https://doi.org/10.1073/pnas.1509820112

    • PubMed
    • Google Scholar
82. 1. Takemura SY
    2. Aso Y
    3. Hige T
    4. Wong A
    5. Lu Z
    6. Xu CS
    7. Rivlin PK
    8. Hess H
    9. Zhao T
    10. Parag T
    11. Berg S
    12. Huang G
    13. Katz W
    14. Olbris DJ
    15. Plaza S
    16. Umayam L
    17. Aniceto R
    18. Chang LA
    19. Lauchie S
    20. Ogundeyi O
    21. Ordish C
    22. Shinomiya A
    23. Sigmund C
    24. Takemura S
    25. Tran J
    26. Turner GC
    27. Rubin GM
    28. Scheffer LK

    (2017a) A connectome of a learning and memory center in the adult Drosophila brain

    eLife 6:e26975.

    https://doi.org/10.7554/eLife.26975

    • PubMed
    • Google Scholar
83. 1. Takemura SY
    2. Nern A
    3. Chklovskii DB
    4. Scheffer LK
    5. Rubin GM
    6. Meinertzhagen IA

    (2017b) The comprehensive connectome of a neural substrate for ‘ON’ motion detection in Drosophila

    eLife 6:e24394.

    https://doi.org/10.7554/eLife.24394

    • PubMed
    • Google Scholar
84. 1. Tomkins A
    2. Ortiz CL
    3. Coca D
    4. Richmond P

    (2016) From GUI to GPU: a toolchain for GPU code generation for large scale Drosophila simulations using SpineML

    Frontiers in Neuroinformatics 2016:49.

    https://doi.org/10.3389/conf.fninf.2016.20.00049

    • Google Scholar
85. Preprint

    1. Ukani NH
    2. Yeh C-H
    3. Tomkins A
    4. Zhou Y
    5. Florescu D
    6. Ortiz CL
    7. Huang Y-C
    8. Wang C-T
    9. Turkcan MK
    10. Liu T
    11. Richmond P
    12. Lo C-C
    13. Coca D
    14. Chiang A-S
    15. Lazar AA

    (2019) The fruit fly brain observatory: from structure to function

    bioRxiv.

    https://doi.org/10.1101/580290

    • Google Scholar
86. 1. Varela N
    2. Gaspar M
    3. Dias S
    4. Vasconcelos ML

    (2019) Avoidance response to CO2 in the lateral horn

    PLOS Biology 17:e2006749.

    https://doi.org/10.1371/journal.pbio.2006749

    • PubMed
    • Google Scholar
87. 1. Ward JH

    (1963) Hierarchical grouping to optimize an objective function

    Journal of the American Statistical Association 58:236–244.

    https://doi.org/10.1080/01621459.1963.10500845

    • Google Scholar
88. 1. Wolff T
    2. Iyer NA
    3. Rubin GM

    (2015) Neuroarchitecture and neuroanatomy of the Drosophila central complex: A GAL4‐based dissection of protocerebral bridge neurons and circuits

    Journal of Comparative Neurology 523:997–1037.

    https://doi.org/10.1002/cne.23705

    • Google Scholar

Acceptance summary:

FlyBrainLab is a resource for driving connectomic analyses of the Drosophila brain and for carrying out computational modeling based on multiple data sources. It supports 3D visualization of datasets published in the worldwide literature, and a number of libraries for integrating anatomical, sensory and physiological data with published and exploratory computational models. It will be useful for a wide range of activities, from exploring the content and intersection of datasets, to comparing circuit models in the same computational setting, to running massively parallel circuit simulations.

Decision letter after peer review:

Thank you for submitting your article "FlyBrainLab:Accelerating the Discovery of the Functional Logic of the Drosophila Brain in the Connectomic/Synaptomic Era" for consideration by eLife. Your article has been reviewed by three peer reviewers, and the evaluation has been overseen by a Reviewing Editor and Ronald Calabrese as the Senior Editor. The following individual involved in review of your submission has agreed to reveal their identity: Padraig Gleeson (Reviewer #1).

The reviewers have discussed the reviews with one another and the Reviewing Editor has drafted this decision to help you prepare a revised submission.

As the editors have judged that your manuscript is of interest, but as described below that additional experiments are required before it is published, we would like to draw your attention to changes in our revision policy that we have made in response to COVID-19 (https://elifesciences.org/articles/57162). First, because many researchers have temporarily lost access to the labs, we will give authors as much time as they need to submit revised manuscripts. We are also offering, if you choose, to post the manuscript to bioRxiv (if it is not already there) along with this decision letter and a formal designation that the manuscript is "in revision at eLife". Please let us know if you would like to pursue this option. (If your work is more suitable for medRxiv, you will need to post the preprint yourself, as the mechanisms for us to do so are still in development.)

Summary:

This manuscript outlines the FlyBrainLab platform, which brings together a number of software packages from the authors to provide a unified interface for viewing data and simulating neuronal activity related to Drosophila. The reviewers felt that the paper had promise but there was substantial work still to be done.

Essential revisions:

1) Could the authors provide substantially more detail on how an experimentalist would use the package? It should be clear why they would want to do so.

2) The manuscript must provide transparency on the data processing and

integration.

3) The package would be far more user-friendly if it had much simpler installation. Detailed instructions would help too.

4) Users would benefit from a process to keep the packages up-to-date, such as for the “hemibrain” module.

In addition, the reviewers have provided many helpful comments to help the authors with their revision.

Reviewer #1:

This manuscript outlines the FlyBrainLab platform, which brings together a number of software packages from the authors to provide a unified interface for viewing data and simulating neuronal activity related to Drosophila.

The application is well described and examples of its use are given. The code for the application components is open source and installation instructions and documented are provided. The suite of components clearly work well together providing a very good example of a user focussed computational neuroscience application for working with advanced data and models.

1) While much of the technical/implementation detail is reserved for the Materials and methods section, the main body of the manuscript would benefit from a high level diagram of the structure of the application (like Supplementary figure 1, or even simpler), or a table defining/summarising the various components mentioned in the main text (NeuroMinerva/CxCircuit/NeuroArch etc.) and how they related to each other.

Reviewer #2:

FlyBrainLab by Lazar et al. provides the ability to set up, execute, and analyze Drosophila neural circuits, while integrating/exploring connectomics data, in a single platform. Such a unified framework has the potential to advance our understanding of the functional logic of the fly brain. The authors show that FlyBrainLab tools can be used to execute models developed previously in the literature. What is missing, however, is a clear demonstration that the platform can be used for de novo exploration and guidance on how the tools offered by the platform will enable new discoveries. In particular, the case is not made that using this library provides an easier path to discovery than the normal ad-hoc approach. The work does not fully describe what a user needs to do to deploy it for their own studies, nor does it clearly show how its own examples were generated.

1) Across the circuit examples supplied in the manuscript, it is not clear what features need to be manually coded up for the particular circuit/question of interest vs. what features can be pulled from FlyBrainLab and directly used. At present, the discussion of the different libraries in the supplement lists capabilities, but there is no guidance or examples of how the libraries can be used in practice. We could not find documentation for CXcircuits, EOScircuits, and MolTrans online. Similarly, the supplementary video illustrates the interactive capabilities of the platform, but the manuscript does not guide the user in replicating these capabilities on their own. To fix this, we advise the authors to include the notebooks used to generate all of the figures/analysis in the main results as supplementary files, with detailed annotation so that a user can use them as starting points for their own analyses.

2) More must be included in the manuscript to describe how the tool can be used for exploratory analysis. Consider including a simple annotated code walkthrough that, starting with some list of neurons, perhaps from the Hemibrain, answers what utilities are available/what code is needed to visualize neuron morphologies, what code is needed to generate an interactive circuit diagram, what code is needed to set up a simple leaky integrate and fire model, what is needed to execute a circuit, and whether resultant firing rate outputs look reasonable. The panels in Supplementary figure 3 are close, but they show the results of the above workflow, and there is no demonstration on how one can get there. Such an example need not (and perhaps is better not to) focus on a well-characterized circuit. The simple examples found in FlyBrainLab/Neuroballad are promising.

3) More work can be done to lower the barrier of entry for FlyBrainLab. Even as a researcher with a few years of Python experience that is currently using the Hemibrain to set up, run, and analyze neural circuits, I had difficulty installing FlyBrainLab and knowing what steps to take to replicate the examples shown in the manuscript. In particular, the installation instructions seem inconsistent/not fully developed on https://github.com/FlyBrainLab/FlyBrainLab. It took hours to figure out which instructions to follow to end up with a Jupyter Lab configuration that resembles the supplementary video, with a notebook, a morphology viewer, and a circuit viewer in the same window. The installation instructions within NeuroMinerva, built on JupyterLab version >2, helped get me to that point, but the instructions on FlyBrainLab, built on JupyterLab version <2, did not get me to that point. In addition, the "Starting Up FlyBrainLab" section on https://github.com/FlyBrainLab/FlyBrainLab should have material on what to do if you do not see an FFBO section or cannot run the example notebook, perhaps in some troubleshooting page.

Reviewer #3:

Lazar and colleagues present a platform, FlyBrainLab that integrates Drosophila neuron and circuit modelling data with neuroanatomy, from morphology to synaptic resolution information. Their desktop system is modular and stand-alone, providing the ability to query, run and visualise particular circuits and models. To demonstrate the functionality of their platform they present 3 specific examples that cover the use of published models, light and electron-microscopy (EM) data and the comparison between larva and adult.

Although the need their platform is addressing is real, the manuscript does not present the work in a compelling way, particularly for this journal's audience. Furthermore, the methods used to integrate data, and how data are used are not described properly. If a system such as this aims to become a standard analytical tool for neuroscientists, it is essential that data integration and processing are transparent.

Please find below a number of concerns. I do not comment on the technical details of the FlyBrainLab platform modules, as that is not my expertise.

1) The structure of the manuscript and the way the examples are presented are not compelling for the average neuroscientist that wants to start using the public data (models, connectome and synaptome). Especially if the one of the main draws of this type of platform is for neuroscientists to start testing models based on real data. The main reason for this is that very little information is given on how experimental data is curated and integrated (see below for more).

2) What neuroanatomical data is being used and in what way is completely opaque. It is assumed that different modalities of data will have been processed in different ways, but very little information is given in this regard. How is the light-level FlyCircuit data processed to infer connectivity and how is this process validated? How are cell types identified and validated, in FlyCircuit and the hemibrain? How many neurons and types are used for each use case?

For example, regarding the CX circuit example, the authors say, "The innervation pattern of each neuron was visually examined in the NeuroNLP window and a standard name assigned according to the naming scheme adopted in the CXcircuit Library." How do these standard names relate to the cell type names used by the community? Identifying cell types from morphological data requires expertise when this is done to the highest resolution, and thus this process should be described in detail. In addition, it becomes very difficult to assess the use cases presented when there is no clarity on what neurons and types are being used.

3) Related to the point above, the authors list the hemibrain data used is from version 1.0.1 (gs://hemibrain-release/neuprint/hemibrain_v1.0.1_neo4j_inputs.zip). However, a new version of the data (1.1) was released online in May, with the data dumps available at least from the end of June (according to https://dvid.io/blog/release-v1.1/). The latest version significantly improves the cell typing that had been released (see https://docs.google.com/document/d/1vae3ClHR8z8uekqwrOHtqiux3oY5-Y_xw6W2srCi3PI/edit?usp=sharing). The authors should update their manuscript to use the latest version of data. This should highlight issues of how data can be kept up to date in these types of platforms and how integration of versions can be achieved. The authors should comment on the processes they use for this.

4) Presenting this platform as a Resource, it becomes essential that it is easy to install. I attempted to install FlyBrainLab according to the instructions in https://github.com/FlyBrainLab/FlyBrainLab. Using miniconda on macOS, which I already had installed for other purposes, I unfortunately ran into errors, and the installation was unsuccessful (seemingly caused by msgpack not being found). The instructions mention that the platform has only been tested in Ubuntu but that it "should work" in other platforms. I understand that it is not possible to test for and avoid, all possible errors, but the authors should test the installation in at least one other OS, if they want the average neuroscientist to start using it.

The tutorials listed in https://github.com/FlyBrainLab/Tutorials are certainly a very useful introduction, although they suffer from the issues in points 2 and 3.

[Editors' note: further revisions were suggested prior to acceptance, as described below.]

Thank you for submitting your article "Accelerating with FlyBrainLab the Discovery of the Functional Logic of the Drosophila Brain in the Connectomic Era" for consideration by eLife. Your article has been overseen by a Reviewing Editor and Ronald Calabrese as the Senior Editor.

The Reviewing Editor has drafted this decision to help you prepare a revised submission.

As the editors have judged that your manuscript is of interest, but as described below that additional work is required before it is published, we would like to draw your attention to changes in our revision policy that we have made in response to COVID-19 (https://elifesciences.org/articles/57162). First, because many researchers have temporarily lost access to the labs, we will give authors as much time as they need to submit revised manuscripts. We are also offering, if you choose, to post the manuscript to bioRxiv (if it is not already there) along with this decision letter and a formal designation that the manuscript is "in revision at eLife". Please let us know if you would like to pursue this option. (If your work is more suitable for medRxiv, you will need to post the preprint yourself, as the mechanisms for us to do so are still in development.)

Summary:

The revised manuscript has addressed some of the technical issues, but has not addressed the core issues of readability of the manuscript , and usability of the software, by a regular fly neurobiologist. This was stated in the Essential revisions, point 1: "1. Could the authors provide substantially more detail on how an experimentalist would use the package? It should be clear why they would want to do so."

While the authors have responded with some limited explanations in the cover letter, the required changes are not evident in the manuscript, and it is there that these essential points of usability must be clarified. Again, it is not sufficient to refer the reader to the website to do this. The appendices, and much of the text, still mostly tell the reader what can be done, rather than how to do it. This should be rather early in the manuscript to motivate what follows.

Similarly, on essential point 2, the reviewers would like to know how their data goes in and is manipulated, and how they can be confident that what the program does is faithful to the original. Issues of installation, which have been presented, are relevant, but of secondary technical importance.

[Editors' note: further revisions were suggested prior to acceptance, as described below.]

Thank you for submitting your article "Accelerating with FlyBrainLab the Discovery of the Functional Logic of the Drosophila Brain in the Connectomic Era" for consideration by eLife. Your article has been reviewed by three peer reviewers, and the evaluation has been overseen by a Reviewing Editor and Ronald Calabrese as the Senior Editor. The following individuals involved in review of your submission have agreed to reveal their identity: Padraig Gleeson (Reviewer #1); Danylo Lavrentovich (Reviewer #2).

The reviewers have discussed their reviews with one another, and the Reviewing Editor has drafted this to help you prepare a revised submission.

Essential Revisions:

The reviewers and I felt that the paper and FlyBrainLab provide a userful resource for the field. The revised version is considerably improved and the reviewers would like to suggest a few essential but straightforward revisions to make it even more accessible to the readers and users of this resource.

1) Update key references (indicated in the detailed reviews).

2) Clarify Figures and their legends, especially Figure 2 and 3.

There are several further important suggestions by the reviewers to strengthen the presentation and improve the accessibility of the paper and resource for readers. These are provided in the detailed reviewer comments below.

Reviewer #1:

This new version of the manuscript has a better layout and will be a more useful introduction to the application for new users. However there are still some issues with how the structure of the application is presented which may be difficult for readers.

Figure 2, especially the legend is quite minimal and there is nothing here to give a reader the key idea that this is a graphical application which a user would interact with through their browser. I suggest to move the screenshot of the application from Appendix 1—figure 2 to a panel in the main figure 2, and make sure these panels are well integrated and explained, e.g. NeuroMynerva in the top panel is what you see in the bottom. Refer the reader here to Appendix 1—figure 1 for more details (some of the colors of the blocks match between the simplified/full versions, e.g. green NeuroArch, there's no reason they all shouldn't for ease of readability).

NeuroNLP and NeuroGFX (window) are mentioned in the text without any context. These need to be shown/explained in Figure 2 and also described briefly where NeuroMynerva etc. are first defined in the Introduction. I would suggest highlighting all important component names in bold where they are first introduced so a user can go back to the definition as they are discussed later in the text.

It is strange that the actual short English language queries used for Figure 3 are not mentioned in the legend or main text. This is an important feature of the application and adding (at least some of) the sequence of commands for one of the panels (e.g. 3a, "show T4a", "color red", "add cholinergic presynaptic neurons" etc.) in another panel/table in the figure would be quite informative for readers. In the main text "(see also Materials and methods)" could be replaced with something better like: (the full sequence of queries which created this panel can be found in the Materials and methods). Also explain that the panels in Figure 3 are screenshots of the NeuroNLP window in Figure 2B, etc.

It is good having a section in the Materials and methods for each of other figures related to the main use cases/examples, but these could be tied together better also, making it clearer that the details of how the figure panels were generated can be found in the Materials and methods. Also some parts of the Materials and methods do not refer back to the figures, e.g. "Model A [26], Model B [27] and Model C [28]" could refer to Figure 6A, B, C etc. Small things like this would improve the readability of the paper significantly.

It might also be worth numbering the use cases/analysis types, e.g. Use Case 1-6, and adding these to subheadings to make it easier to move between the main text and Materials and methods.

Overall the manuscript is a good introduction to the range of features FlyBrainLab offers and is structured such that a user can see what can be accomplished, and is given some guidance how they would achieve it themselves.

Reviewer #2:

The text is clearer and more inviting for a general audience. The enumeration of capabilities in the Introduction is effective. The Results section is structured well, displaying different use cases of FlyBrainLab. The accompanying tutorials online serve as good launching points for researchers.

Thank you to the authors for the additions in the main text, the code walkthroughs in the appendices, and the improved installation instructions. The basic tutorials are simple to follow. My only suggestion on the code side is to be more verbose in the introduction to the lamina cartridge executable circuit notebook and in the limitations of the user-side-only installation.

Reviewer #3:

The revised version of the manuscript addresses many of the concerns previously reported. Thank you to the authors for providing much clearer information about the data that is ready to use in the FlyBrain Lab platform, how it can be used, installed and the components of the FlyBrainLab. There are still some corrections that are needed regarding the source of some of the datasets.

Throughout the paper, reference 4 (Xu et al., 2020) is used as the citation for the hemibrain dataset. This is a preprint that has been superseded by the publication in September 2020 of the peer-reviewed paper (Scheffer et al., 2020, https://doi.org/10.7554/eLife.57443). It also needs updating in GitHub (https://github.com/FlyBrainLab/Datasets#ref-1)

The reference to the larval L1EM dataset also needs correcting. For example this is given as reference 2 (Berck et al., 2016). The correct reference, as correctly shown in https://github.com/FlyBrainLab/Datasets#ref-3, is Ohyama et al., 2015 (reference 69). There might be other instances in the text that use the wrong citation.

The section added to the beginning of the Results, which includes Figure 3, provides readers with some examples on how they can start exploring the data in the platform (published datasets) using plain English queries. However, I do not think the added Figure 3 currently presents the data in a way that makes it easy for readers to link the relevant text and figure legend that describe the connectivity, to the panels. Each of the 4 examples (a-d) displays a neuron plot (left) and a connectivity matrix (right); other than reading each of the row/column names it is not possible to link the neurons plotted on the left to the data plotted on the right. Adding a colored annotation bar or even coloring the row/column names of the connectivity matrices according to the neuron plots would certainly help, or perhaps adding some clustering.

Example 2 refers to a possible direct connection between the mushroom body and the fan-shaped body ("raising the question whether the two memory centers are directly connected"). Some of the neurons directly connecting these 2 neuropils (and possible pathways for visual information in addition to reference 17), have been described already, in Li et al., 2020 (December 2020, https://doi.org/10.7554/eLife.62576), one of the recent papers based on the hemibrain dataset. Could the authors please rephrase?

Essential revisions:

1) Could the authors provide substantially more detail on how an experimentalist would use the package? It should be clear why they would want to do so.

The FlyBrainLab platform has a number of capabilities that can be used by experimentalists with widely different backgrounds in computing.

a) For experimentalists with limited programming experience, the platform can be used for extensive visualization, interactive search and building of simple brain circuits of interest. The FlyBrainLab interactive capabilities only require here basic knowledge of terminology in neurobiology. The user interacts with the UI through natural language queries without the need to go through button-clicking or to learn a new, sophisticated database query language. For example, the NeuroNLP Window (see Appendix 1—figure 2) supports the construction of novel brain circuits (not just displaying individual neuron/cell types) on the morphological level of abstraction. Simple utilities enable the graphical display of connectivity diagrams (graphs). The neurons displayed can be subsequently targeted for genetic manipulation, optogenetic ablation and/or recording. As these properties are not the main focus of our manuscript, we created a notebook to guide the user through the use of English queries and illustrate its effectiveness.

b) Experimentalists with some computer background, say Python programming, have the capability to explore and analyze novel circuits as demonstrated in Figure 6. The level of computing knowledge required is akin to Matlab programming. Here, the exploration and analysis of yet unknown brain circuits may be of interest. For example, if the experimentalist has detailed morphology and/or neural activity data of a cell of interest, he/she can build with FlyBrainLab a circuit containing post and presynaptic neurons and computationally analyze the circuit connectivity and the effect of neuron ablation on its function. The same effect can often be evaluated by experimental means, say by optogenetic ablation of neurons suggested by the computational model. The same methodology can be followed through when choosing a circuit initially investigated in the literature. FlyBrainLab immediately extends the capabilities to visualize and evaluate the functionality of a chosen circuit in a larger context than previously published. In addition, the user can benefit from the Circuit Libraries written by more computationally-advanced users. Since FlyBrainLab bridges the gap between fly brain data and executable circuits, interactive computational models are much easier for an experimentalist to explore than an ad-hoc program. This is clearly reflected in the CX example depicted in Figure 3 where multiple windows synchronize morphology visualization data with circuits diagrams. Furthermore, these libraries provide an easier path for experimentalists to computationally explore the circuits under study and to validate or invalidate models using collected data. For example, users can intuitively silence neurons using an interactive circuit diagram (rather than digging into someone’s code) and compare its response to a recorded circuit where the same neuron is silenced genetically. Ultimately, the exact mechanism underlying the function of brain circuits is what is largely lacking.

c) Experimentalists with more advanced computational neuroscience background, can take full advantage of the capabilities to generate circuit diagrams, and run parallel programs with Neurokernel on GPUs. In this scenario, the experimentalist goes well beyond what is possible today on the bench. The key reason is scaling. An arbitrary number of interconnected neuropils of interest implemented by the same or different research groups can be interconnected and structurally and functionally explored, as these circuit models are also represented in the NeuroArch Database and can be easily retrieved for execution. Scaling circuits say by considering larger and larger brain regions, is clearly of paramount importance in the quest of understanding the logic of brain function. As in classical Computer Science, the question of scaling leads to deep questions of complexity. Here, the FlyBrainLab offers a platform for accelerating the discovery of the functional logic of the Drosophila brain something ad-hoc methods cannot deliver. By analogy, we can of course build cars in a garage, but in order to accelerate the building of cars, the car makers moved on long time ago to the assembly line.

To lower the bar of entry for systems and computational neuroscientists, we now provide a number of tutorials online at https://github.com/FlyBrainLab/Tutorials organized along the technical proficiency required. We are aware, however, that we do not/cannot accommodate the needs of all the users in the neuroscience research community interested in using the FlyBrainLab computing platform.

2) The manuscript must provide transparency on the data processing and

integration.

We would like to stress that FlyBrainLab is not positioned as a data provisioning platform, but rather a computing platform that provides utilities to visualize fly brain data and explore, analyze, evaluate and compare executable circuit models in a common environment.

To evaluate the transparency of the data integration and circuit execution capabilities presented here clearly requires that users have FlyBrainLab fully operational. We strongly recommend that if, for whatever reason, the reviewers run into installation problems, they contact us through the editors. In this context, we would like to emphasize that the complexity of FlyBrainLab platform is well beyond what has been typically attempted in the past computational neuroscience literature. The complexity involved is reminiscent to that of an operating system where processes running on a CPU (Neurokernel) interact with a database (NeuroArch) and are flexibly invoked by the UI through NeuroMynerva.

To further enhance the transparency of the computing platform, we included 2 new figures into the manuscript:

a) Figure 2 in the Introduction section gives an overview of the main components and hints at the complexity of the overall FlyBrainLab architecture.

b) Figure 6 in the Results section demonstrates the capability to effectively explore the structure and function of yet to be discovered brain circuits.

Figure 2 and Appendix 1—figure 1 and 2 help clarify the complexity of the FlyBrainLab architecture. Understanding the underlying design choices of the systems architecture of FlyBrainLab was previously detailed in papers describing the NeuroArch (Givon et al., 2015: http://dx.doi.org/10.5281/zenodo.44225) and Neurokernel (Givon and Lazar, 2016: https://doi.org/10.1371/journal.pone.0146581) components. The NeuroMynerva user-side front end, built on top of JupyterLab is new. We are avoiding listing more details here as they are too technical. They are of course available on Github.

We included now a number of tutorials to help the user take advantage of the Circuit and Utility libraries. Detailed notebooks provide users with an overview and a number of examples how to invoke the libraries. For example, we published the CXcircuits Library at https://github.com/FlyBrainLab/CXcircuits, and included notebooks for each of the three CX models analyzed in the main text. In addition, the notebooks and libraries of the other figures/results will be published once the paper is accepted. They will be listed in the “Publications and Talks” and ”Libraries” sections of the FlyBrainLab Wiki page https://github.com/FlyBrainLab/FlyBrainLab/ wiki/FlyBrainLab-Resources.

Although we do not consider the content of the datasets as being central to capabilities of FlyBrainLab as a computing tool, we welcome the use of our platform with (not instead of) other data provision platforms and have provided examples of how FlyBrainLab can be used with new datasets (https://github.com/FlyBrainLab/Tutorials/blob/ master/tutorials/swc_loading_tutorial/swc_loading.ipynb) However, in order to demonstrate the capabilities of FlyBrainLab to work with a wide range of datasets, we’ve included several publicly available datasets (listed and tracked in the FlyBrainLab Wiki) in the default FlyBrainLab package, which have been loaded into the NeuroArch database with minimal changes (apart from formatting edits for compatibility with the NeuroArch schema, which is specified in Givon et al., 2015 (http://dx.doi. org/10.5281/zenodo.44225)). Notebooks for loading these datasets into NeuroArch databases are provided in https://github.com/FlyBrainLab/datasets.

3) The package would be far more user-friendly if it had much simpler installation. Detailed instructions would help too.

We substantially improved upon and taken the installation process to the next level.

a) We corrected, and significantly expanded the installation instructions at https: //github.com/FlyBrainLab/FlyBrainLab, and added a Wiki page for troubleshooting (https://github.com/FlyBrainLab/FlyBrainLab/wiki/Troubleshooting).

b) We now provide multiple installation options for users of different expertise: 1) using a script, 2) using our docker image, and 3) using an Amazon AWS machine image. All these options typically only require a single command line for installation and a single command line for starting the application. We also clearly listed the system requirements for each installation option. Dependencies are fully described in the installation scripts.

c) We tested the installation procedure on Linux (Ubuntu and CentOS), macOS and Windows.

d) We asked a diverse range of users, including colleagues, collaborators, undergraduate students to test the installation and received positive feedback.

e) We created a number of “get started” tutorials to guide through the basic features of the system (https://github.com/FlyBrainLab/Tutorials/tree/master/ tutorials/getting_started).

f) We now provide users more information about available resources (https:// github.com/FlyBrainLab/FlyBrainLab/wiki/FlyBrainLab-Resources), including i) a list of the latest version of the components, and ii) a list of publicly available datasets that we loaded into the NeuroArch database.

4) Users would benefit from a process to keep the packages up-to-date, such as for the “hemibrain” module.

For installation purposes, we have published and will keep updating a list of the latest versions of all FlyBrainLab components https://github.com/FlyBrainLab/ FlyBrainLab/wiki/FlyBrainLab-Resources#repositories. The installation scripts provide the version number of the dependencies whenever applicable.

For datasets loaded into the NeuroArch Database, we

a) Provided a Datasets Version Tracker https://github.com/FlyBrainLab/datasets, that also includes the latest Hemibrain dataset,

b) Published the code/notebooks used to load the NeuroArch Database with different datasets, thereby helping users to load the NeuroArch Database independently of the main developers,

c) Will periodically and timely update the database, and welcome community contributions.

In addition, the reviewers have provided many helpful comments to help the authors with their revision.

Reviewer #1:

This manuscript outlines the FlyBrainLab platform, which brings together a number of software packages from the authors to provide a unified interface for viewing data and simulating neuronal activity related to Drosophila.

The application is well described and examples of its use are given. The code for the application components is open source and installation instructions and documented are provided. The suite of components clearly work well together providing a very good example of a user focussed computational neuroscience application for working with advanced data and models.

1) While much of the technical/implementation detail is reserved for the Materials and methods section, the main body of the manuscript would benefit from a high level diagram of the structure of the application (like Supplementary figure 1, or even simpler), or a table defining/summarising the various components mentioned in the main text (NeuroMinerva/CxCircuit/NeuroArch etc.) and how they related to each other.

Thank you for the suggestion! We added a new figure (Figure 2) to the manuscript to provide an early overview of the main FlyBrainLab components, i.e., NeuroArch, Neurokernel and NeuroMynerva. As suggested by the reviewer, Figure 2 is a simpler version of Appendix 1—figure 1. It provides an overview of the main datasets currently available in NeuroArch, and the circuit execution capabilities supported by Neurokernel. To put the FlyBrainLab components in a better context, we also added text relating the levels of abstraction underlying Figure 2 and Appendix 1—figure 1.

Reviewer #2:

FlyBrainLab by Lazar et al. provides the ability to set up, execute, and analyze Drosophila neural circuits, while integrating/exploring connectomics data, in a single platform. Such a unified framework has the potential to advance our understanding of the functional logic of the fly brain. The authors show that FlyBrainLab tools can be used to execute models developed previously in the literature. What is missing, however, is a clear demonstration that the platform can be used for de novo exploration and guidance on how the tools offered by the platform will enable new discoveries. In particular, the case is not made that using this library provides an easier path to discovery than the normal ad-hoc approach. The work does not fully describe what a user needs to do to deploy it for their own studies, nor does it clearly show how its own examples were generated.

We thank the reviewer for the constructive comments on the manuscript. At the end of the Results section, we now present several examples and ways for exploring an unknown circuit by expanding upon the Supplementary figure 3 of the original submission.

What FlyBrainLab offers may not be an easier path to discovery, but certainly a faster one. What does a car assembly line provide? Does one still need to design a car? Yes, and it’s a difficult problem. But assembly line makes the production much faster. Similarly, FlyBrainLab provides an essential workflow for building circuits from data, visualizing circuits, comparing existing models within the same platform, interactively manipulating circuits, creating new models that can all be completed within a single environment that provides the much needed integration to accelerate discoveries. Furthermore, we have substantially expanded the tutorials https://github.com/FlyBrainLab/Tutorials, specifically https://github.com/FlyBrainLab/Tutorials/tree/master/tutorials/getting_started to get users started with all aspects of the FlyBrainLab. Notebooks for the CX example have been published, and the notebooks for the other results in the manuscript will be published once the paper is accepted for publication.

The reviewer seems to suggest that comparison between models is not a novel exploration of circuit function. We argue the opposite. Comparison of models in the literature is one of the keys for an in-depth understanding of the exact assumptions, structure and function of the published models, operating under the same setting/environment. This is how fields like machine learning, signal processing, computer vision thrive, where comparisons and being able to run every line of code is a standard practice. However, this is not the norm in systems neuroscience and computational neuroscience, with very few exceptions (see this paper https://doi.org/10.1523/JNEUROSCI.3374-12.2013 for an example). In the two examples involving early olfactory circuits, we do not just “execute models developed previously in the literature”. Rather, the models considered have been adapted to new contexts to explore the function of the circuits under consideration, either due to the more precise connectivity information brought by the Hemibrain dataset, or due to a downsizing of the larva circuit. We consider these also as de novo exploration of the functional logic of the underlying circuits.

1) Across the circuit examples supplied in the manuscript, it is not clear what features need to be manually coded up for the particular circuit/question of interest vs. what features can be pulled from FlyBrainLab and directly used. At present, the discussion of the different libraries in the supplement lists capabilities, but there is no guidance or examples of how the libraries can be used in practice. We could not find documentation for CXcircuits, EOScircuits, and MolTrans online. Similarly, the supplementary video illustrates the interactive capabilities of the platform, but the manuscript does not guide the user in replicating these capabilities on their own. To fix this, we advise the authors to include the notebooks used to generate all of the figures/analysis in the main results as supplementary files, with detailed annotation so that a user can use them as starting points for their own analyses.

We thank the reviewer for this suggestion. To address the concern raised, we published the CXcircuits Library at https://github.com/FlyBrainLab/CXcircuits, and included notebooks for each of the three CX models analyzed in the main text. The notebooks are mentioned in the revised manuscript. To avoid duplication, we chose to publish the code directly on GitHub instead of using supplementary manuscript files. In this way, the code can constantly be updated to include new features and users can benefit from the most up-to-date version. We also note that the exact commit provides access to the code for reproducing the figures/results of the manuscript.

In addition, the notebooks and libraries of the other figures/results will be published once the paper is accepted. They will be listed in the “Publications and Talks” and ”Libraries” sections of the FlyBrainLab Wiki page https://github.com/FlyBrainLab/FlyBrainLab/wiki/ FlyBrainLab-Resources.

We would like to take this opportunity to further clarify the current division of the roles taken by FlyBrainLab platform and its Libraries.

The main components of the FlyBrainLab, as described in the Appendix 1, provide core functionalities required for data storage/retrieval, visualization, user interface and code execution of brain circuits. Examples of capabilities that users can directly invoke are given below:

1) Query using plain English and 3D graphics for building and visualizing brain circuits;

2) Retrieval of connectivity of the brain circuit built/visualized;

3) User interface and API for circuit diagram interaction;

4) Specification of models for each circuit components.

5) Execution of the circuits represented/stored in the NeuroArch Database.

The Utility Libraries provide tools for 1. analyzing data that are retrieved using the core FlyBrainLab functionality, 2. creating circuit diagrams semi-automatically.

The Circuit Libraries are built on top of the core FlyBrainLab functionality and provide tools to study functions of a specific brain region/circuit. An analogy of the relation between Circuit Libraries and the FlyBrainLab platform is that between the toolboxes and core functions of Matlab. In Matlab, the former provide high-level, application-specific functionality realized with some of the core built-in functions (such as a digital signal processing toolbox). In other words, the Circuit Libraries are examples of how the features of FlyBrainLab can/should be used.

2) More must be included in the manuscript to describe how the tool can be used for exploratory analysis. Consider including a simple annotated code walkthrough that, starting with some list of neurons, perhaps from the Hemibrain, answers what utilities are available/what code is needed to visualize neuron morphologies, what code is needed to generate an interactive circuit diagram, what code is needed to set up a simple leaky integrate and fire model, what is needed to execute a circuit, and whether resultant firing rate outputs look reasonable. The panels in Supplementary figure 3 are close, but they show the results of the above workflow, and there is no demonstration on how one can get there. Such an example need not (and perhaps is better not to) focus on a well-characterized circuit. The simple examples found in FlyBrainLab/Neuroballad are promising.

Thank you for your suggestion. We substantially expanded upon the exploratory example in Supplementary figure 3 and moved it to the end of the Results section. It appears now as Figure 6 in the subsection entitled “Exploring the Structure and Function of Yet to be Discovered Brain Circuits”. Three examples are described that demonstrate the use of the Utility Libraries in the quest of novel discoveries.

Furthermore, we have substantially expanded upon the online documentation and tutorials. We have added notebooks showing examples in each of the main steps of the workflow, including:

1) How to ask questions in English to obtain a list of neurons of interest (including visualizing their morphology) and how to build upon an initial set of neurons,

2) How to generate circuit diagrams,

3) How to interact with the circuit diagram layout, build a model and execute it, obtain the result and plot the response.

We will continue to release more examples in the future.

3) More work can be done to lower the barrier of entry for FlyBrainLab. Even as a researcher with a few years of Python experience that is currently using the Hemibrain to set up, run, and analyze neural circuits, I had difficulty installing FlyBrainLab and knowing what steps to take to replicate the examples shown in the manuscript. In particular, the installation instructions seem inconsistent/not fully developed on https://github.com/FlyBrainLab/FlyBrainLab. It took hours to figure out which instructions to follow to end up with a Jupyter Lab configuration that resembles the supplementary video, with a notebook, a morphology viewer, and a circuit viewer in the same window. The installation instructions within NeuroMinerva, built on JupyterLab version >2, helped get me to that point, but the instructions on FlyBrainLab, built on JupyterLab version <2, did not get me to that point. In addition, the "Starting Up FlyBrainLab" section on https://github.com/FlyBrainLab/FlyBrainLab should have material on what to do if you do not see an FFBO section or cannot run the example notebook, perhaps in some troubleshooting page.

We thank the reviewer for the valuable feedback and apologize for the confusion. We substantially improved upon the installation process:

1) We corrected, and significantly expanded the installation instructions at https:// github.com/FlyBrainLab/FlyBrainLab, and added a Wiki page for troubleshooting (https://github.com/FlyBrainLab/FlyBrainLab/wiki/Troubleshooting).

2) We tested the installation procedure on Linux (Ubuntu and CentOS), macOS and Windows.

3) We have already published and will keep updating a Docker image that has the full FlyBrainLab installed (https://hub.docker.com/r/fruitflybrain/fbl). We also included an Amazon Machine Image to be used on the AWS EC2 service https://github.com/ FlyBrainLab/FlyBrainLab#14-amazon-machine-image. Additional images for other cloud services will be provided upon request.

4) We asked a diverse range of users, including colleagues, collaborators, undergraduate students to test the installation and received positive feedback.

Reviewer #3:

Lazar and colleagues present a platform, FlyBrainLab that integrates Drosophila neuron and circuit modelling data with neuroanatomy, from morphology to synaptic resolution information. Their desktop system is modular and stand-alone, providing the ability to query, run and visualise particular circuits and models. To demonstrate the functionality of their platform they present 3 specific examples that cover the use of published models, light and electron-microscopy (EM) data and the comparison between larva and adult.

Although the need their platform is addressing is real, the manuscript does not present the work in a compelling way, particularly for this journal's audience. Furthermore, the methods used to integrate data, and how data are used are not described properly. If a system such as this aims to become a standard analytical tool for neuroscientists, it is essential that data integration and processing are transparent.

We thank the reviewer for providing this perspective and we would like to stress that FlyBrainLab is not positioned as a data provisioning platform, but rather as a computing platform that provides utilities to visualize fly brain data and explore, analyze, evaluate and compare executable circuit models in a common environment. We’d like to clarify that we consider data curation, integration and processing as porting currently publicly available datasets into the NeuroArch database, and we fully respect the expertise of researchers generating and curating fly brain data. As such, apart from formatting changes for consistency with NeuroArch database’s schema, minimal changes are done for any data saved to and loaded from the NeuroArch database into the Neurokernel Execution Engine. Although 6 default datasets are provided as starting points for users, the FlyBrainLab platform was developed to be agnostic of the content of the underlying datasets. We welcome the use of any additional datasets that can be loaded locally on machines running FlyBrainLab without communicating with our publicly hosted data servers. We do acknowledge, however, that in addition to providing the reference to the previous NeuroArch publications, transparency in terms of how data is saved to and loaded from the NeuroArch database could be make clearer. To that end, we’ve done the following:

1) We published the code used to create the NeuroArch database, which can be used directly or indirectly and independently of us to load new datasets and update upstream datasources,

2) We have updated the latest version of NeuroArch database that provides the Hemibrain version 1.1, and

3) We published a webpage tracking versioning of NeuroArch database.

Please find below a number of concerns. I do not comment on the technical details of the FlyBrainLab platform modules, as that is not my expertise.

1) The structure of the manuscript and the way the examples are presented are not compelling for the average neuroscientist that wants to start using the public data (models, connectome and synaptome). Especially if the one of the main draws of this type of platform is for neuroscientists to start testing models based on real data. The main reason for this is that very little information is given on how experimental data is curated and integrated (see below for more).

We thank the reviewer for this feedback. While, as we already mentioned, we do not curate datasets, we included additional tutorials and examples of how individual components of the FlyBrainLab platform can be used to access/visualize/manipulate data types such as neuroanatomical connectomics/synaptomics. We also note that in the example shown in Figure 4 of the Results section, the workflow employed for modifying a previous (FlyCircuit-based) model of the Antennal Lobe to reflect new public (Hemibrain-based) data is intended as an illustration of how models can be updated using more recent (connectomics/synamptomics) data. Furthermore, we would like to clarify that the purpose of the FlyBrainLab platform is to provide an integrated system to experiment with fly brain data that are publicly available worldwide. The developers of FlyBrainLab do minimal modifications to the datasets apart from porting them into the NeuroArch database using a specified schema (as specified in Givon et al., 2015 (http://dx.doi.org/10.5281/zenodo.44225)). We do acknowledge the need for clearer examples of how newly published data can be integrated into the database. For end-users who intend to use other datasets not currently provided as default in FlyBrainLab, we included additional example notebooks detailing how such datasets can be loaded into the FlyBrainLab. Finally, although not generally recommended, we note that components in NeuroMynerva (the user front-end) can be independently invoked without communicating with the database. The neuroanatomy visualizer (Neu3D-Widget), for example, can load arbitrary swc or mesh files, where the corresponding 3D data can be accessed in the associated python kernel once the files are loaded into the widget. An example notebook (link) has been added to highlight this use case as well.

2) What neuroanatomical data is being used and in what way is completely opaque. It is assumed that different modalities of data will have been processed in different ways, but very little information is given in this regard. How is the light-level FlyCircuit data processed to infer connectivity and how is this process validated? How are cell types identified and validated, in FlyCircuit and the hemibrain? How many neurons and types are used for each use case?

For example, regarding the CX circuit example, the authors say, "The innervation pattern of each neuron was visually examined in the NeuroNLP window and a standard name assigned according to the naming scheme adopted in the CXcircuit Library." How do these standard names relate to the cell type names used by the community? Identifying cell types from morphological data requires expertise when this is done to the highest resolution, and thus this process should be described in detail. In addition, it becomes very difficult to assess the use cases presented when there is no clarity on what neurons and types are being used.

We believe that two types of questions are raised above by the reviewer. One relates to how the anatomical data from the original dataset are processed and stored, and the other relates to how the data is interpreted from a model’s perspective and used in modeling.

To address the first type of questions, we would like to reiterate the position we take on connectome data. We do not generate connectome data, including the morphology of the neurons and their connectivities, nor are we in the position to identify large quantities of cell types. The utility that the platform provides is the APIs to read/write the NeuroArch Database. We do not provide any additional interpretations of these datasets. For transparency, we now provide the code that we used to create NeuroArch labeled datasets from their original source (see also the response to your comment #3). For the Hemibrain dataset, the cell types and names of individual neurons have always been assigned according to the original dataset, along with a reference ID pointing to the ID used in the original dataset. For the FlyCircuit dataset, we included original neurons from FlyCircuit 1.2 (http://flycircuit.tw), and the inferred connectivity according to the algorithm published and made available to us by the authors (https://doi.org/10.3389/fninf.2018.00099 now cited in the Data Availability section). For the Larva L1EM dataset, we included detailed description of how the publicly served dataset (https://l1em.catmaid.virtualflybrain.org) is loaded into the NeuroArch Database (https://github.com/FlyBrainLab/datasets#README.md), including a CSV file that shows the mapping between original neuron labels in the raw Dataset to the labels used in FlyBrainLab. For transparency, IDs of the neurons of the original data source are always available/displayed in the Info Panel (see also Appendix 1—figure 2).

To address the second type of questions, we would like to note the following. First, even though a substantial amount of hard work has been put into annotating datasets by their original creators, often there may be missing data/labels, and some labels are simply not really useful. In order to create an executable circuit, a user may need to make additional assumptions to assign labels/names/types. One example is provided by the FlyCircuit dataset which contains no cell type information. Additional information must be brought in from the literature by a user or he/she needs to make further assumptions. Second, the naming scheme provided by the original dataset or even in the literature is not the best possible.

For example, as the reviewer pointed out, the standard naming scheme we used in the CX example is not the same as the one used by the research community (we also have to point out that there are many names used by the community for these neuron types, and depending on the researcher, the names used appear to be largely random). We have adopted a naming scheme (in the original submission) that is both human readable and easily machine-parsable. The latter property has never been the focus of naming schemes used by neurobiologists but is critical when it comes to specifying neurons for code execution. These two points highlight the need for flexibility in processing publicly available data. The FlyBrainLab provides users full access to the NeuroArch Database to update any of the neuron’s information/metadata as desired.

Finally, we would like to address the concern raised in the last sentence in the reviewer’s comment. The types of neurons in the CX example are already provided in the Materials and methods section, including in Figure 7 (in the revised manuscript). We also corrected our statement on visually examining these neurons. The visual examination was aided by the published neuron types in the paper (https://doi.org/10.1016/j.celrep.2013.04.022). For the neurons in the FlyCircuit dataset but not mentioned in the paper, we made assumptions in modeling according to the available evidence in the literature. The details are omitted here as they are largely out of scope. In the revised manuscript, however, we added further information on each individual neuron modeled. Similarly, the types of neurons and the number of neurons of each type is explicitly mentioned in the two examples of the early olfactory system.

3) Related to the point above, the authors list the hemibrain data used is from version 1.0.1 (gs://hemibrain-release/neuprint/hemibrain_v1.0.1_neo4j_inputs.zip). However, a new version of the data (1.1) was released online in May, with the data dumps available at least from the end of June (according to https://dvid.io/blog/release-v1.1/). The latest version significantly improves the cell typing that had been released (see https://docs.google.com/document/d/1vae3ClHR8z8uekqwrOHtqiux3oY5-Y_xw6W2srCi3PI/edit?usp=sharing). The authors should update their manuscript to use the latest version of data. This should highlight issues of how data can be kept up to date in these types of platforms and how integration of versions can be achieved. The authors should comment on the processes they use for this.

We thank the reviewer for this comment. Again, as mentioned in the responses to earlier questions, the main purpose of this manuscript is to describe the FlyBrainLab as a platform of which the NeuroArch database, not an individual dataset, is a critical component. Incidentally, we presented a usage case in which the Hemibrain dataset version 1.0.1 is the main source of data. This should bear no difference in showcasing the capabilities of the FlyBrainLab than using version 1.1. Therefore, we assert that there is no need to update the database in the example we presented in the paper.

To benefit the community, however, we do feel the need to periodically and in a timely fashion update the database for the purpose of general usage. We did the following: (1) we have updated the latest version of the NeuroArch database and currently provide the Hemibrain version 1.1, (2) we published a webpage tracking versions of the NeuroArch database, and 3) we published the code used to create the NeuroArch Database. The code can be used directly or indirectly and independently of us once an update of the upstream datasource is available.

4) Presenting this platform as a Resource, it becomes essential that it is easy to install. I attempted to install FlyBrainLab according to the instructions in https://github.com/FlyBrainLab/FlyBrainLab. Using miniconda on macOS, which I already had installed for other purposes, I unfortunately ran into errors, and the installation was unsuccessful (seemingly caused by msgpack not being found). The instructions mention that the platform has only been tested in Ubuntu but that it "should work" in other platforms. I understand that it is not possible to test for and avoid, all possible errors, but the authors should test the installation in at least one other OS, if they want the average neuroscientist to start using it.

The tutorials listed in https://github.com/FlyBrainLab/Tutorials are certainly a very useful introduction, although they suffer from the issues in points 2 and 3.

We thank the reviewer for the valuable comment. To address the concern, we did the following:

1) We significantly expanded the installation instruction on https://github.com/FlyBrainLab/FlyBrainLab, added a Wiki page for troubleshooting

(https://github.com/FlyBrainLab/FlyBrainLab/wiki/Troubleshooting), and mentioned that the Issue Trackers on GitHub can be useful in this case (we also understand that the reviewer needs the remain anonymous).

2) We tested the installation procedure on Linux (Ubuntu and CentOS), macOS and Windows.

3) We have already published and will keep updating a Docker image that has the full FlyBrainLab installed. We also provide an Amazon Machine Image to be used on the AWS EC2 service. Additional images on other services can be provided if requested.

4) We asked a diverse range of users, including colleagues, collaborators, undergraduate students to test the installation and received positive feedback.

[Editors' note: further revisions were suggested prior to acceptance, as described below.]

The revised manuscript has addressed some of the technical issues, but has not addressed the core issues of readability of the manuscript , and usability of the software, by a regular fly neurobiologist. This was stated in the essential revisions, point 1: "1. Could the authors provide substantially more detail on how an experimentalist would use the package? It should be clear why they would want to do so."

While the authors have responded with some limited explanations in the cover letter, the required changes are not evident in the manuscript, and it is there that these essential points of usability must be clarified. Again, it is not sufficient to refer the reader to the website to do this. The appendices, and much of the text, still mostly tell the reader what can be done, rather than how to do it. This should be rather early in the manuscript to motivate what follows.

Thank you for the clarification. In this revision, we substantially expanded the text to address the readability issue of the manuscript and how an experimentalist can use the platform. We added in the Results section two more examples showing the type of questions FlyBrainLab can be used effectively to answer questions raised by a regular fly neurobiologist, and in the Materials and methods section the steps needed to answer these with FlyBrainLab.

Specifically, we added in the Results section the entry “Building Fly Brain Circuits with English Queries”, showing the versatility of the English query interface of FlyBrainLab, also technically known as NeuroNLP. NeuroNLP enables users, without any programming knowledge, to perform complex queries to build, visualize and explore biological circuits, a capability that none of the current data provisioning services is designed to do or can provide to neurobiologists/neuroscientists. In the corresponding part in the Materials and methods section, the English queries employed are listed in full detail.

We also moved a part of the text previously included in the supplement/appendix to the new entry entitled “Exploring the Structure and Function of Yet to be Discovered Brain Circuits” in the Results section. Here, we provided several examples on how to analyze connectome/synaptome datasets using FlyBrainLab to identify structures and cell types, and create circuit diagrams modeling brain pathways. We describe the steps to achieve these results in the corresponding part of the Materials and methods section.

In the newly added entry “Interactive Exploration of Executable Fruit Fly Brain Circuits” in the Results section, we present the construction of an interactive circuit diagram for rapidly developing circuit models. The capability to remove or reenable a neuron in the circuit diagram is akin to, respectively, silencing and rescuing neurons in an experiment, and is of particular interest to systems neurobiologists. Such a capability quickly enable the exploration of biological findings by means of computational models, and it is highly flexible and scalable beyond the typical experimental settings.

Finally, we added Appendix 4 with a walk through of code highlighting the main capabilities of the FlyBrainLab regarding model creation and circuit execution, including: (1) loading the NeuroArch Database from connectome datasets, (2) building and exploring biological circuits, (3) interactively exploring circuit diagrams, (4) execution of circuits retrieved from the NeuroArch Database.

Concluding, the manuscript now comprehensively describes how neurobiologists and computational neuroscientists alike can leverage the power of FlyBrainLab, whether they want to simply visualize neural circuit through complex English queries, analyze the connectivity data, or construct executable circuit models for exploration, analysis, comparison and evaluation.

Similarly, on essential point 2, the reviewers would like to know how their data goes in and is manipulated, and how they can be confident that what the progam does is faithful to the original. Issues of installation, which have been presented, are relevant, but of secondary technical importance.

Thank you for the clarification. We added the entry “Loading Publicly Available Datasets into NeuroArch Database” in the Materials and methods section. We provided details of how each dataset is handled using the NeuroArch API for loading into the NeuroArch Database. We also provided some high-level statistics of the loaded datasets. The scripts for loading these datasets have been published on GitHub: https://github.com/FlyBrainLab/ Datasets. In addition, in Appendix 4, we now provide a complete walk through some of the core FlyBrainLab capabilities with a simple example, including data loading. Some basic usages of data loading are exemplified.

[Editors' note: further revisions were suggested prior to acceptance, as described below.]

Essential Revisions:

The reviewers and I felt that the paper and FlyBrainLab provide a userful resource for the field. The revised version is considerably improved and the reviewers would like to suggest a few essential but straightforward revisions to make it even more accessible to the readers and users of this resource.

1) Update key references (indicated in the detailed reviews).

We updated the references according to the suggestions of reviewer #3. We also checked and updated references to preprints of other peer-reviewed publications.

2) Clarify Figures and their legends, especially Figure 2 and 3.

We updated Figure 2 and Figure 3 according to the suggestions from the reviewers.

There are several further important suggestions by the reviewers to strengthen the presentation and improve the accessibility of the paper and resource for readers. These are provided in the detailed reviewer comments below.

Reviewer #1:

This new version of the manuscript has a better layout and will be a more useful introduction to the application for new users. However there are still some issues with how the structure of the application is presented which may be difficult for readers.

Figure 2, especially the legend is quite minimal and there is nothing here to give a reader the key idea that this is a graphical application which a user would interact with through their browser. I suggest to move the screenshot of the application from Appendix 1—figure 2 to a panel in the main Figure 2, and make sure these panels are well integrated and explained, e.g. NeuroMynerva in the top panel is what you see in the bottom. Refer the reader here to Appendix 1—figure 1 for more details (some of the colors of the blocks match between the simplified/full versions, e.g. green NeuroArch, there's no reason they all shouldn't for ease of readability).

We updated Figure 2 as well as expanded on its caption as suggested.

NeuroNLP and NeuroGFX (window) are mentioned in the text without any context. These need to be shown/explained in Figure 2 and also described briefly where NeuroMynerva etc. are first defined in the Introduction. I would suggest highlighting all important component names in bold where they are first introduced so a user can go back to the definition as they are discussed later in the text.

As suggested, we highlighted the component names with bold font at their first instance.

It is strange that the actual short English language queries used for Figure 3 are not mentioned in the legend or main text. This is an important feature of the application and adding (at least some of) the sequence of commands for one of the panels (e.g. 3a, "show T4a", "color red", "add cholinergic presynaptic neurons" etc.) in another panel/table in the figure would be quite informative for readers. In the main text "(see also Materials and methods)" could be replaced with something better like: (the full sequence of queries which created this panel can be found in the Materials and methods). Also explain that the panels in Figure 3 are screenshots of the NeuroNLP window in Figure 2B, etc.

We added English queries in the first example (Use Case 1) and refer readers to the Materials and methods section for a full sequence of queries for the rest of the examples.

It is good having a section in the Materials and methods for each of other figures related to the main use cases/examples, but these could be tied together better also, making it clearer that the details of how the figure panels were generated can be found in the Materials and methods. Also some parts of the Materials and methods do not refer back to the figures, e.g. "Model A [26], Model B [27] and Model C [28]" could refer to Figure 6A, B, C etc. Small things like this would improve the readability of the paper significantly.

It might also be worth numbering the use cases/analysis types, e.g. Use Case 1-6, and adding these to subheadings to make it easier to move between the main text and Materials and methods.

We added Use Case 1-6 to each of the subheadings in the Results as well as in the Materials and methods section.

Overall the manuscript is a good introduction to the range of features FlyBrainLab offers and is structured such that a user can see what can be accomplished, and is given some guidance how they would achieve it themselves.

Reviewer #2:

The text is clearer and more inviting for a general audience. The enumeration of capabilities in the Introduction is effective. The Results section is structured well, displaying different use cases of FlyBrainLab. The accompanying tutorials online serve as good launching points for researchers.

Thank you to the authors for the additions in the main text, the code walkthroughs in the appendices, and the improved installation instructions. The basic tutorials are simple to follow. My only suggestion on the code side is to be more verbose in the introduction to the lamina cartridge executable circuit notebook and in the limitations of the user-side-only installation.

We thank the reviewer for the valuable comments and suggestions. We added more detailed instructions in the lamina cartridge tutorial, in particular, on the exact steps for starting the backend servers and creating a workspace so that the code can be readily executed. We further clarified the limitations of the user-side-only installation in the Code Availability and Installation section in Materials and methods .

Reviewer #3:

The revised version of the manuscript addresses many of the concerns previously reported. Thank you to the authors for providing much clearer information about the data that is ready to use in the FlyBrain Lab platform, how it can be used, installed and the components of the FlyBrainLab. There are still some corrections that are needed regarding the source of some of the datasets.

Throughout the paper, reference 4 (Xu et al., 2020) is used as the citation for the hemibrain dataset. This is a preprint that has been superseded by the publication in September 2020 of the peer-reviewed paper (Scheffer et al., 2020, https://doi.org/10.7554/eLife.57443). It also needs updating in GitHub (https://github.com/FlyBrainLab/Datasets#ref-1)

As requested, we updated all citations to the paper above.

The reference to the larval L1EM dataset also needs correcting. For example this is given as reference 2 (Berck et al., 2016). The correct reference, as correctly shown in https://github.com/FlyBrainLab/Datasets#ref-3, is Ohyama et al., 2015 (reference 69). There might be other instances in the text that use the wrong citation.

We corrected the citation and checked to make sure that the reference is cited correctly in the rest of the manuscript.

The section added to the beginning of the Results, which includes Figure 3, provides readers with some examples on how they can start exploring the data in the platform (published datasets) using plain English queries. However, I do not think the added Figure 3 currently presents the data in a way that makes it easy for readers to link the relevant text and figure legend that describe the connectivity, to the panels. Each of the 4 examples (a-d) displays a neuron plot (left) and a connectivity matrix (right); other than reading each of the row/column names it is not possible to link the neurons plotted on the left to the data plotted on the right. Adding a colored annotation bar or even coloring the row/column names of the connectivity matrices according to the neuron plots would certainly help, or perhaps adding some clustering.

In the new Figure 3, we matched the color of row/column neuron names in the adjacency matrix to the color of the visualized neurons. Note that in the interactive user interface, each neuron can be highlighted/addressed by their name. It is, however, not possible to reflect this feature in the printed version of the manuscript.

Example 2 refers to a possible direct connection between the mushroom body and the fan-shaped body ("raising the question whether the two memory centers are directly connected"). Some of the neurons directly connecting these 2 neuropils (and possible pathways for visual information in addition to reference 17), have been described already, in Li et al., 2020 (December 2020, https://doi.org/10.7554/eLife.62576), one of the recent papers based on the hemibrain dataset. Could the authors please rephrase?

We rephrased the paragraph and referenced the paper.

Author details

1. Aurel A Lazar

   Department of Electrical Engineering, Columbia University, New York, United States

   Contribution

   Conceptualization, Resources, Formal analysis, Supervision, Funding acquisition, Investigation, Methodology, Writing - original draft, Project administration, Writing - review and editing, Conceived the study and FlyBrainLab software architecture. Developed comparative models of the central complex. Developed comparative models of the early olfactory system.

   For correspondence

   aurel@ee.columbia.edu

   Competing interests

   No competing interests declared

   Additional information

   The authors’ names are listed in alphabetical order.

   "This ORCID iD identifies the author of this article:" 0000-0003-4261-8709

2. Tingkai Liu

   Department of Electrical Engineering, Columbia University, New York, United States

   Contribution

   Conceptualization, Software, Formal analysis, Validation, Investigation, Visualization, Methodology, Writing - original draft, Writing - review and editing, Conceived the study and FlyBrainLab software architecture. Developed the FlyBrainLab platform. Developed user-side libraries. Developed comparative models of the early olfactory system.

   Competing interests

   No competing interests declared

   Additional information

   The authors’ names are listed in alphabetical order.

   "This ORCID iD identifies the author of this article:" 0000-0003-3075-7648

3. Mehmet Kerem Turkcan

   Department of Electrical Engineering, Columbia University, New York, United States

   Contribution

   Conceptualization, Software, Formal analysis, Validation, Investigation, Visualization, Methodology, Writing - original draft, Writing - review and editing, Conceived the study and FlyBrainLab software architecture. Developed the FlyBrainLab platform. Developed user-side libraries and utility libraries. Developed comparative models of the central complex. Developed comparative models of the early olfactory system.

   Competing interests

   No competing interests declared

   Additional information

   The authors’ names are listed in alphabetical order.

   "This ORCID iD identifies the author of this article:" 0000-0001-9273-7293

4. Yiyin Zhou

   Department of Electrical Engineering, Columbia University, New York, United States

   Contribution

   Conceptualization, Software, Formal analysis, Funding acquisition, Validation, Investigation, Visualization, Methodology, Writing - original draft, Project administration, Writing - review and editing, Conceived the study and FlyBrainLab software architecture. Developed the FlyBrainLab platform. Updated the server-side components of the existing FFBO architecture. Developed comparative models of the central complex.

   Competing interests

   No competing interests declared

   Additional information

   The authors’ names are listed in alphabetical order.

   "This ORCID iD identifies the author of this article:" 0000-0003-4618-4039

• 2,761

  Page views

• 295

  Downloads

• 6

  Citations

Article citation count generated by polling the highest count across the following sources: Crossref, PubMed Central, Scopus.