(1) Overview

Introduction

Compartmental analysis is a methodology used to investigate the fluxes and accumulation of matter and energy in compartmented systems []. It is used to model phenomena from a diverse breadth of areas, including pharmacokinetics [, ], geography [], ecology [, ], oncology [, ], physiology [, , , ], and even building design []. This broad utility is facilitated by the uniform theory compartmental analysis is built upon, and the systematic modelling methods it provides [].

In plant physiology, compartmental analysis by tracer efflux (CATE) is one of several radioisotope methods used to trace the movement of substances across plant cell membranes and between plant organs. However, CATE can be used to do this non-invasively, which is unusual due to the structural and functional complexity of plant systems [, ]. In addition, although mathematically demanding and labour-intensive compared to other radioisotope methodologies, CATE can provide a more comprehensive view of the multiplex of unidirectional fluxes and compartmented concentrations of the traced substance []. Currently, a three-compartment model consisting of surface film, cell wall, and cytosol (in order of decreasing rapidity of exchange) is generally accepted for use with CATE under short-term labelling scenarios [, , , , , , ], although it may not be valid under certain experimental conditions (e.g., high substrate concentrations, at which transport is governed by low-affinity systems) [, , ].

CATE involves measuring the kinetics of tracer release from labelled plant systems to the external solution. Typically, the procedure involves first “loading” plants with an appropriate radioisotope, by immersing roots of intact plants in radioactive solution long enough to achieve significant accumulation of radioisotope in the cytosol of the root cells, but short enough that potentially confounding fluxes from the vacuole remain unlabelled [, , , ]. After this, labelled plants are transferred to “efflux funnels” [, ] where they are “washed”, or eluted of radioactivity by exposure to sequential aliquots of non-radioactive nutrient solution. In each aliquot, solution exchange with labelled roots takes place over a prescribed time interval, after which the aliquot is removed (via a drainage clip attached to the efflux funnel), and immediately replaced with the next aliquot of non-radioactive solution. After the elution series is complete, plant organs are harvested and radioactivity in plant organs and eluates is measured. The pattern of tracer release from the three-compartment system takes the form of a compound exponential [] consisting of three release phases/compartments, and can be modelled by the equation

At=A1ek1t+A2ek2t+A3ek3t,

In which At is the rate of total tracer release, An is the maximal tracer released from each compartment, and kn is the rate constant for each compartment (i.e., the linearized slopes of declining tracer release found using semi-logarithmic transformation of data; see Figure 4). For a visual representation of a typical CATE procedure, see Coskun et al. (2014) [].

To enable the rapid extraction of CATE parameters, vaCATE was developed to extend the functionality of an internal laboratory tool that consisted of a Visual Basic macro embedded in an Excel file. It improves upon the macro in several key areas: improved statistical analysis, the inclusion of a curve-peeling procedure that allows more rapidly exchanging compartments to be analysed, and error checking and handling. While there are a variety of software applications available for compartmental analysis (e.g., SAAM II [], PKSolver [], TopFit [], to list a few), most are commercially-available and/or specialized for pharmacokinetics. In contrast, vaCATE is available for free, was developed specifically for use with CATE, and its open-source licensing agreement allows for modification of the underlying software architecture if non-commercial use in other applications is desired.

Implementation and architecture

Written in Python, vaCATE was constructed to allow users to easily manipulate and extract CATE parameters from large datasets. This is done through a front-end graphical user interface (GUI) implemented using wxPython and matplotlib, and a back-end implemented using xlsxwriter, xlrd, and numpy.

Initial Set-Up

After opening vaCATE, users are greeted by a menu dialog asking them to either analyse CATE data or generate a CATE template file (Figure 1). Users must format their data using a generated CATE template file before they are able to conduct an analysis using vaCATE. An example of a completed template file is given in Figure 2 (and in the ‘Examples’ folder where vaCATE was cloned/installed). In this file, each individual CATE replicate is allocated its own column (from column ‘C’ onwards) with specific parameters input according to row labels in columns ‘A’ and ‘B’. All of the information indicated by the labels in rows ‘1’ through ‘7’ is required. Of note, row 6 (‘G-factor’) allows users to apply instrument-specific corrections to account for inaccuracies in radioactivity measurements due to internal geometries of the detecting equipment [, ].

Figure 1 

Initial menu dialog presented to the user.

Figure 2 

Example of a completed CATE template file. Cells containing ‘…’ are used to indicate that the spread-sheet contains data below what is presented in the figure. Note that completion of the ‘Vial #’ column under cell ‘A8’ is optional.

Under cell ‘B8’ (Figure 2), the time at which each eluate was removed is entered in descending order (from the first one taken onwards). It should be noted that eluate times are represented as decimal fractions of a minute (e.g., 1 minute and 30 seconds is represented as 1.5 minutes). This sequence of elution times is used for every CATE replicate in the file. If different elution schedules are used in the same dataset then a separate CATE template file should be prepared for each schedule. Within the columns allocated to each CATE replicate, eluate radioactivities are entered next to their corresponding elution times (found under cell ‘B8’; Figure 2). In this way, data from CATE replicates sharing the same elution schedule are processed simultaneously.

Once the user’s dataset has been entered into the CATE template file, the data can be analysed by clicking on the ‘Analyze CATE Data’ button (Figure 1). Users have the option to ‘Automatically Analyze’ the data in the CATE template file (default option; Figure 1), which conducts an objective regression using the last 8 eluates (see Types of Regression Models section below). If this feature is disabled by deselecting the corresponding checkbox then no analysis is conducted when the initial dynamic preview of the data is presented (Figure 4).

Experiment and Analysis Object Instantiation

Once a correctly filled-out CATE template file is selected for analysis, Excel.grab_data() retrieves the data from the template file and returns an Experiment object (Figure 3). The ‘analyses’ attribute of this Experiment object (Experiment.analyses) contains a list of Analysis objects; one Analysis object is created for each CATE replicate found in the template file. In turn, the ‘run’ attribute of each Analysis object (Analysis.run) points to a Run object which contains the immutable data for that CATE replicate. This is the data that does not depend on the type of analysis that will eventually be done (e.g., the shoot/root weight, the elution times, etc.; see Figure 3 for complete set of parameters).

Figure 3 

General architecture of vaCATE’s back-end. Modules are represented by white boxes, objects by orange boxes, object attributes by blue boxes, and methods/functions by green boxes. Forward slashes (‘/’) in attribute names are used to indicate the different forms that exist (e.g., obj_x/y_start means that both obj_x_start and obj_y_start attributes exist). Custom objects created by vaCATE can be assumed to belong to the Objects module. Note that this figure is meant to represent a general overview, and not necessarily the sequence in which data is processed.

Dynamic Preview of Data

Experiment objects are then loaded into a wx. Frame object for display in the graphical user interface (Figure 4). The name of the current CATE replicate being previewed and its run number relative to the larger data set are displayed in the title bar. Below that, three labelled graphs display a preview of the data extracted from the three phases of the compartmental analysis. In the navigation bar below that, the first four buttons from the left allow users to manipulate how the data is displayed in the preview window, and the following ‘left arrow’ and ‘right arrow’ buttons allow users to change which CATE replicate is displayed. The final ‘floppy disk’ button allows users to output the current analysis of the dataset to an Excel (.xlsx) file.

Figure 4 

Window displaying the current analysis applied to the data set. This allows users to dynamically change and preview analyses before export to an Excel (.xlsx) file.

The areas labelled ‘Objective Regression’ and ‘Subjective Regression’ allow users to define and implement their own objective and subjective regressions, respectively (see Types of Regression Models section below). User-defined regressions can be implemented by filling in the appropriate fields in either area and pressing the corresponding ‘Draw Objective/Subjective Regression’ button. Below this is the ‘Propagate Regression’ button, which helpfully allows users to apply currently-input regression settings to every CATE replicate being analysed. Finally, the area labelled ‘Regression Parameters’ contains the data extracted from compartmental analysis of phases that have been, or can be, defined.

Types of Regression Models

Compartmental analysis of data with vaCATE can be done using either objective or subjective regression models. The objective regression model is conducted as described in Siddiqi et al. (1991) [] and Kronzucker et al. (1999) []. Briefly, a linear regression using the last n eluates from the CATE replicate is calculated (where n is the number of points specified in the ‘Number of points to use’ field; Figure 4). This is repeated with the last n + 1, n + 2, etc. eluates and successive coefficients of correlation (R2) of the regressions are compared. Once the coefficients of correlation decrease three times in a row, the eluate occurring before these three decreases is determined to be the beginning of the phase boundary. Conversely, the subjective regression model allows the user to directly define these boundaries. If the user were to subjectively set the boundaries to be the same as those defined by the objective regression model, then the output parameters of the resulting compartmental analyses would be the same. Boundaries are expressed using the elution times of the eluates (column under cell ‘B8’ in Figure 2; x-axis of any plot in Figure 4).

Users wishing to extend the functionality of vaCATE may implement their own algorithm to determine phase boundaries. All that is required of such an algorithm is the generation of tuples which would be used to set the boundaries of each phase (‘xs_p1/2/3’ attribute; Figure 3), as is the case with the subjective and objective regression models discussed above.

Note that the default analysis conducted by vaCATE if the ‘Automatically Analyze’ option is left selected (Figure 1) is an objective regression using the last 8 eluates from each CATE replicate. However, this number of points used to start the objective regression can later be set by the user in the ‘Objective Regression’ area (see Figure 4).

Compartmental Analysis of Phase Parameters

After the ‘xs_p1/2/3’ attributes of the Analysis object have been set, compartmental analysis can be conducted. This is done by calling the analyse() method on the Analysis object (Figure 3), which extracts the compartmental analysis of multiple phases in sequential order (later, slower phases before earlier, faster phases). Nesting of “if” statements restricts compartmental analysis to only valid situations (i.e., to phases that are either the slowest, or for which compartmental analysis of later, slower phases has been done), and is recommended if users are using the vaCATE software backend to independently to conduct their own compartmental analysis.

Compartmental analysis of a phase is specifically done by calling the extract_phase() function in the Operations module. The Phase objects returned from this are stored as attributes of the Analysis object (Analysis.phase3/2/1; see Figure 3). Phases for which compartmental analysis is not valid or not done (see above) are stored as blank phases (with all attributes set to empty strings).

Within the extract_phase() method, phase boundaries are converted to indices specific to the data series of the phase that is being analysed (an important error-checking mechanism; see Curve-stripping section below). These indices are used to demarcate elution times and logarithmically-expressed radioisotope release rates specific to the phase in question from the larger x- and y-series (respectively) that were passed to the method. This linear regression is used in conjunction with other data from the CATE replicate to calculate various parameters of the phase required for compartmental analysis (Table 1) [, , , , ].

Table 1

Names, descriptions and calculations of relevant parameters involved in compartmental analysis by tracer efflux (CATE). For more in-depth discussion regarding these parameters and their calculations, readers are directed to relevant works in the literature [, , , , ].

Parameter name inDescriptionCalculation

LiteratureGUI Backend†

So SASASpecific activity of loading solutionRadioactivity of loading solution (cpm/mL)
kkkRate constantslope of regression line × 2.303
to∙5 Half-Lifet05Half-life of exchange0.693/k
Ro r0Rate of radioisotope release at to Antilog of x-intecept
φco EffluxeffluxEfflux from compartment Ro/So
φnet Net FluxnetfluxNet flux(Root + shoot radioactivity)/So/root weight
φoc InfluxinfluxInfluxφco × φnet

* Graphical user interface; † of vaCATE.

Curve-stripping

Slowly-exchanging phases occur simultaneously alongside faster phases. As such, their contribution to total tracer efflux must be removed in order to isolate the faster phases. This is done using a curve-stripping method which is coded into the curvestrip() function of the Operations module (Figures 3 and 5; lines 298–335). This function is passed four parameters: the x- and y-series of the data that are to be curve-stripped and the slope and intercept of the regression line calculated from the immediately following slower phase. Using the slope and intercept, this slower phase is extrapolated into the range of the faster phase(s) that are to be curve-stripped (Figure 5; lines 315–319). The curve-stripping then occurs; that is, the antilog of this extrapolated data from the slower phase is subtracted from the antilog of the data from the faster phase(s) (Figure 5; lines 326–334). The result of this operation is then re-expressed logarithmically.

Figure 5 

The curvestrip() method in the Operations module is used to remove the effects of later, slower phases from earlier, faster phases.

Here, an important data-validation step is implemented (Figure 5; lines 330–332); subtractions that would result in negative logarithmic operations are not added to the curve-stripped x- and y-series that are to be returned. These negative-log operations occur when the extrapolated tracer efflux from the slower phase is ostensibly larger than the cumulative tracer efflux from both this phase and earlier, more rapidly-exchanging phases. While obviously impossible, such data points occasionally come about due to experimental error (CATE is an extremely labour-intensive procedure which can be prone to errors) or to resolution limitations of the detection equipment. If the problem is limited to a small number of data points (at most two), the CATE replicate in question is usually minorly affected, and remains representative of the tested conditions. As long as such problems do not consistently afflict the majority of the CATE replicates conducted, affected replicates should be included in experimental results in order to avoid wasting resources and labour.

Accounting for Shifting Data Series’

The data-validation step presented above poses some interesting challenges from a software engineering perspective. Most poignantly, data points used as boundaries for earlier, more rapidly exchanging phases may be removed. Additionally, a sufficient number of data points may be removed such that compartmental analysis is rendered impossible (i.e., the boundaries delineating a phase contain less than two data points). A discussion regarding how these challenges were dealt with is outside the scope of the current work. However, further information can be found in the ‘README.md’ file found on vaCATE’s github page.

Data Output

After regressions on the examined data set have been satisfactorily configured by the user, the current set of analyses can be exported into a spread sheet by clicking the ‘floppy disk’ button in the navigation bar (see Dynamic Preview of Data section above). The outputted spread sheet is saved under the name ‘vaCATE Output – (YYYY_MM_DD).xlsx’ in the same folder that the data was read from.

Quality control

To ensure vaCATE operates as expected, results from four CATE experiments in rice (Oryza sativa), encompassing over 90 replicates, were calculated by hand twice, using phase boundaries as determined by both objective and subjective regression.

The results from manual calculations were used to test every possible parameter determined by vaCATE. Each CATE replicate was subjected to over 60 individual tests (using the unittests module; see Tests.py).

Furthermore, 24 ‘edge cases’ were manually constructed to specifically test situations that were likely to create errors in vaCATE. These situations included, but were not limited to: phases missing data points that corresponded to phase boundaries, phases missing sufficient data points as to render CATE impossible, efflux traces in which objective regression is impossible (i.e., in which the coefficient of correlation never decreases three times in a row; see Types of Regressions section), etc. These ‘edge cases’ were subject to the same testing process that is described above, and are named according to the situation they are testing.

All of the test cases can be found in the ‘Tests’ folder where vaCATE was installed or cloned, and are already formatted according to the CATE template file requirements. To see if the software is working, a user should simply select a test file for analysis with vaCATE, after which they should see a preview dialog (similar to Figure 4). This, in turn, should create an output Excel file and close upon selection of the ‘floppy disc’ button. If the user selects a file titled ‘Test_Multirun1.xlsx’ from one of these folders to be analysed by vaCATE then the resultant output Excel file can be directly compared to an provided example output file found in the same folder that the data was read from.

(2) Availability

Operating system

vaCATE has been tested on Windows 7, 8.1, and 10.

Programming language

Python 2.7.5. Compatibility with Python 3 has not been tested.

Additional system requirements

Any system capable of running the operating systems on which vaCATE has been tested (i.e., Windows 7/8.1/10) should be capable of running vaCATE.

Dependencies

When running vaCATE from the source code, the following dependencies are required for Windows 7:

  • Python version 2.7.5.
  • matplotlib (version 1.3.1/1.5.3). Used for creating figures displayed by GUI.
  • numpy (version 1.8.2). Used for mathematical calculations.
  • wx (version 2.8.12.1/3.03). Used to create GUI.
  • xlrd (version 0.9.2). Used to read Excel files.
  • xlsxwriter (version 0.6.5). Used to create Excel files.

When testing vaCATE, the following dependencies are required:

  • nose (version 1.3.7).
  • nose-parameterized (version 0.5.0).

When cloning the vaCATE repository, the above dependencies can be installed using the included ‘requirement.txt’ file by running the ‘pip install –r requirements.txt’ command inside command prompt. We recommend that this command be run inside a virtual environment, in line with current industry best practises. When vaCATE is installed and run using the executable setup file, the above dependencies are automatically installed.

List of contributors

The integration of matplotlib and wx was initially implemented using a template created by Eli Bendersky [].

Software location

Archive

(e.g., institutional repository, general repository) (required – please see instructions on journal website for depositing archive copy of software in a suitable repository)

Name: figshare

Persistent identifier:https://doi.org/10.6084/m9.figshare.4688503.v2

Publisher: Rubens Flam-Shepherd

Version published: 1.0

Date published: 10/05/17

Code repository

Name: Github

Identifier:https://github.com/rubenflamshepherd/vaCATE

Licence: GNU General Purpose License version 3.0

Date published: 10/05/17

Language

English

(3) Reuse potential

In the presented work, vaCATE is used to automate parameter extraction from up to three phases found in compartmental analysis by tracer efflux (CATE), the task for which it was specifically written. However, vaCATE is not limited to situations where data is collected using radioisotopes. Parameters can be extracted using data from any compartmental analysis, as long as the measured substance moving into/out of compartments can be detected with sufficient temporal resolution, and the system being modelled involves up to three sequential compartments.

In the field of pharmacokinetics four or more sequential phases can occasionally be seen when conducting compartmental analysis. In this situation, users can easily utilize vaCATE’s backend to conduct/automate the analysis they require. To do this, users will need to first define phase boundaries. This can be done using the objective regression provided by vaCATE, or via a custom algorithm defined by the user (see Types of Regression Models section). Once phase boundaries have been established, parameters from the phases can be extracted by calling the extract_phase() function. For sequential phases, parameters from the last, most slowly-exchanging phase should be extracted first, and the curvestrip() function should be called on the data representing the remaining phases. After this, the process should be repeated with the next slowest phase, and so on. Both the extract_phase() and curve_strip() functions can be found in the Operations module.