Method, medium and system for processing custom field formula

The formula editor and data model implemented by computers provide intuitive interfaces and multi-stage calculations, solving the problems of complexity and error risks of custom field definitions, and improving the scalability of custom fields in laboratory analysis instruments and readability.

CN118946934APending Publication Date: 2024-11-12WATERS TECH IRELAND LIMITED IE
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028193.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-01-18
Filing Date
2023-01-18
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When users define custom fields in laboratory analysis instruments, it is difficult to visualize what they are doing and it is prone to errors. It is difficult to verify errors when analyzing formulas in the prior art, and the custom fields are poorly scalable.

Method used

Using a computer-implemented method, a visual interface is provided through the formula editor, allowing users to build a collection of custom fields as interconnected nodes, store them as data models, support dynamic definition and multi-stage calculations, and provide tree views and mathematical representations for easy visualization. and troubleshooting to reduce the risk of errors.

Benefits of technology

Implement more intuitive custom field definitions, reduce error risk, improve custom fields scalability and readability, and simplify formula validation and troubleshooting.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118946934A_ABST
    Figure CN118946934A_ABST
Patent Text Reader

Abstract

Exemplary embodiments provide computer-implemented methods, media, and apparatus configured to import, create, and edit formulas for analyzing custom fields in a chemical system. The custom field may be represented as a tree structure having nodes representing operators. When the custom field is defined, it may be incorporated into the workflow of the analytical chemistry system. Dependencies within the custom field may be identified, and the custom field may be incorporated into the workflow at an appropriate workflow stage. A range of the custom field may be determined to define on which elements of the data collection the custom field operates. Various visualization options are described that allow the custom field to be displayed and / or edited in different ways.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 300,397, filed on January 18, 2022. The entire disclosure of that application is hereby incorporated herein by reference. Background Art

[0003] Laboratory analytical instruments are devices used to qualitatively and / or quantitatively analyze samples. They are typically used in a laboratory setting as part of an analytical chemistry system for scientific research or testing. Such devices can measure the chemical composition of a sample, determine the amount of a component in a sample, and perform similar analyses. Examples of laboratory analytical instruments include mass spectrometers, chromatographs, titrators, spectrometers, elemental analyzers, particle size analyzers, rheometers, thermal analyzers, etc.

[0004] When a laboratory analytical instrument generates data, it may store the data in a data structure, such as a table. The data structure may include fields that store the values ​​of variables. For example, a field may be a column in a table that represents the value of a particular measurement in a number of different samples or experiments. Summary of the invention

[0005] In some cases, users may wish to define their own custom fields based on fields defined by the laboratory analytical instrument or experiment, or based on other custom fields (or a combination of both). For example, one of the fields in the data may store the amount of a component detected in a sample. A user may wish to know the average amount of a component detected in a group of samples, and therefore may define a custom field that performs this calculation.

[0006] In practice, defining custom fields often involves performing detailed calculations using complex mathematical formulas. In these cases, it can be difficult for users to visualize what they are doing, and it is relatively easy to make mistakes when defining custom field formulas. Therefore, exemplary embodiments are directed to improved techniques for defining formulas for custom fields that provide improved visualization, represent custom field formulas in a more intuitive manner, and allow more complex custom fields to be defined with a reduced risk of errors.

[0007] Example embodiments may include a computer-implemented method, as well as a non-transitory computer-readable medium storing instructions for performing the method, a device configured to perform the method, and the like.

[0008] In one embodiment, data from a laboratory analytical instrument may be accessed. The data may be organized into one or more fields. The data may represent information captured by a laboratory analytical instrument to analyze a sample (e.g., identifying the components of the sample, the amount of the components, the purity and / or potency of the sample, etc.). A field may be a grouping of values ​​for one or more specific variables, e.g., a field may be conceptualized as a vector representing a collection of data elements of the same type.

[0009] Laboratory analytical instruments can be associated with analytical methods encoded in workflows. An analytical method can represent a set of steps performed in a specific order to analyze data. It can involve the specification of an algorithm to be executed during analysis and the values ​​used to parameterize the algorithm. A method can be, for example, a sequence of steps used to confirm the identity, quality, purity, and potency of a sample being tested. A workflow can capture a specific method in an analytical chemistry system and allow the method to be executed on one or more computers.

[0010] A request may be received to define custom fields for use in a stage of a workflow. A custom field may be a field that contains values ​​that are not directly or explicitly measured by a laboratory analytical instrument. A custom field may be derived from other fields (whether explicitly measured by a laboratory analytical instrument or other custom fields) and / or constants, among other possibilities.

[0011] In order to define custom fields, the interface can display a formula editor workspace, which includes a list of one or more fields of data, a list of available operators, and a formula editor. An operator can accept one or more inputs (which can be, for example, an array of data values, such as a vector or matrix) called operands, manipulate the input, and generate output. An operator can be, for example, a vector operator that treats a field as a set and returns a scalar or subset of the set. An operator can also or alternatively be a vectorized operator that is applied to the elements of the operands and returns a vector of the same size as one or both of the operands. An operator can be an arithmetic operator or a logical operator as well as other types.

[0012] The formula editor may include one or more interactive placeholders configured to accept operators or operands. A placeholder may represent an empty node in which an operator or operand may be placed, respectively. A selection of one of the available operators may be received, and the selected operator may be incorporated into a custom field in place of the placeholder. Alternatively or in addition, a selection of one of the one or more fields may be received, and the selected field may be incorporated into a custom field in place of the placeholder.

[0013] This technique for building custom field formulas is different from conventional techniques, which typically rely on parsing the formula as it is entered. In such conventional techniques, the user types the formula into an edit box, and the entered text is parsed simultaneously to convert the typed formula into a suitable structure. When the user incorrectly types part of the formula, the structure will be incorrectly constructed. In addition, if the formula is entered with errors (e.g., missing brackets, accidental deletions, etc.), error verification may be very difficult.

[0014] The first embodiment allows formulas to be constructed as a collection of interconnected nodes without having to parse the formula during creation. This results in fewer errors and simpler validation. As described below in conjunction with the fourth and fifth embodiments, it also allows for a simpler presentation of the formula. In addition, due to the way custom fields are created, nodes can be stored as data models or object models. Therefore, custom fields are more easily scalable than traditional parsing-based techniques.

[0015] The custom field thus created can be associated with a stage of a workflow, wherein the association makes the custom field accessible to the workflow. When the workflow runs, it can access the custom field and perform the calculation defined by the custom field's formula.

[0016] In a second embodiment, the value of a custom field may be calculated during the stage of the workflow with which it is associated. This allows custom fields to be defined dynamically. For example, a custom field may depend on fields that are calculated at several stages of a workflow. When a custom field is created, the latest stage of the workflow that generated the fields required by the custom field may be selected as the associated stage, and the custom field may be calculated during that stage. This allows custom fields to depend on data calculated at multiple different workflow stages.

[0017] For example, when a custom field is created or modified, the stage processor can process the custom field. To process the custom field, the stage processor can: collect all custom field calculations in the processing stage; sort the calculations by dependency; resolve the constants in each formula as scalars; loop through the analyzed injections or components according to the defined scope of each calculation (see the third embodiment below) to retrieve the fields used in the calculation and fill all nodes using the same field; calculate the results of each node from bottom to top; fill the final result of the custom field; and fill any error or warning codes of the custom field.

[0018] In a third embodiment, the analytical method can measure one or more injections into a laboratory analytical instrument, each injection comprising one or more components. For example, the injection can be a specific sample injected into a laboratory analytical instrument for measurement by the laboratory analytical instrument. The sample can be separated into various components by the laboratory analytical instrument. The components can be, for example, molecules, compounds, elements, etc.

[0019] A scope for a custom field may be received, where the scope specifies that the custom field calculation should be applied to all components in each injection, each component in all injections, or all components in all injections. By determining the scope of a custom field in this manner, the user can define which elements in the operands will be used to calculate the custom field. This provides a greater degree of control over custom fields than has traditionally been available.

[0020] In a fourth embodiment, a selection of a tree view interface element may be received. In response, a custom field may be displayed as a tree including a set of nodes representing operators and a set of leaf nodes representing operands. This provides an easy-to-read view of a custom formula, which allows a user to more effectively visualize and troubleshoot the formula. Because the formula is defined and represented as a set of nodes representing operators, it can be quickly and efficiently converted into a tree view.

[0021] In a fifth embodiment, a selection of a formula renderer interface element may be received. In response, a custom field may be displayed in a formula renderer view in mathematical notation. This provides a more formal view of the custom field. Due to the structure of the custom field (represented as a tree including a set of nodes), the formula may be efficiently and correctly rendered, particularly when the formula includes one or more division operators (specifically in the case of multiple division operators). Portions of the mathematical notation may be foldable (based on the tree structure of the custom field) to simplify the formula view and allow the user to troubleshoot the custom field.

[0022] In a sixth embodiment, a text representation of a custom field may be displayed in a text box in the interface. The text box may be configured to receive a pasted formula from a clipboard, but may also be configured to not allow editing of the formula in the text box. This enforces the underlying tree structure of the custom field, which provides the advantages described above. Allowing the user to paste (but not edit) the formula in the edit box provides a degree of backward compatibility for custom fields generated in an environment based on parsing. The formula pasted into the text box may be converted into a tree structure by identifying the operators in the formula and recursively defining the operands of these operators.

[0023] As in the fifth embodiment, the text representation in the sixth embodiment may be collapsed based on the tree structure to improve readability.

[0024] In a seventh embodiment, a cursor may be displayed at a position in the text box corresponding to the current editing action of the custom field. For example, the cursor position may be analyzed after the formula is converted to a node. Depending on where the cursor is located in the corresponding tree structure of the custom field, the interface may present different options:

[0025] When an empty node is selected, an operator, field, or constant can be added / inserted to the empty node.

[0026] A formula from another custom field can also be inserted into an empty node.

[0027] When the body of a non-empty node is selected, it can be replaced by another (compatible) operator, field or constant. A formula from another custom field can also be inserted into the node. Non-empty nodes can also be deleted or cleared.

[0028] • When the beginning of a non-empty node is selected, an operator may be inserted to the left of the node, and the original node then becomes the right operand of the newly inserted operator.

[0029] • When the end of a non-empty node is selected, an operator may be inserted to the right of the node, and the original node then becomes the left operand of the newly inserted operator.

[0030] The seventh implementation allows the user to interact with the textual representation of the custom fields, but also retains the advantages of representing the custom fields as a tree.

[0031] Unless otherwise stated, it is contemplated that each embodiment can be used alone to achieve the advantages specifically noted above. It is also contemplated that the embodiments described above (and elsewhere herein) can be used in any combination to achieve further synergistic effects. Other technical features will be readily apparent to those skilled in the art from the following figures, descriptions, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the figure numeral that first introduces that element.

[0033] Figure 1 An example of a mass spectrometry system according to an exemplary embodiment is shown.

[0034] Figure 2 Depicted is an exemplary interface for a workflow builder including workflow steps, transitions, and visualizations associated with each step, according to an exemplary embodiment.

[0035] Figure 3 An example of a custom field tree structure is shown according to one embodiment.

[0036] Figure 4 An exemplary custom field editor interface is shown according to one embodiment.

[0037] Figure 5 A custom field setup wizard is shown according to one embodiment.

[0038] Figure 6 An exemplary operator / operand selector is shown according to one embodiment.

[0039] Fig. 7A An example of a presentation view is shown herein according to one embodiment.

[0040] Figure 7B An example of a presentation view is shown herein according to one embodiment.

[0041] Fig. 8A An example of a mathematical representation view according to one embodiment is shown.

[0042] Figure 8B An example of a mathematical representation view according to one embodiment is shown.

[0043] Fig. 9 An example of a mathematical representation view according to one embodiment is shown.

[0044] Fig.10 Exemplary custom field formula logic is shown according to one embodiment.

[0045] Fig.11 An exemplary computer system architecture is depicted that can be used to practice the exemplary embodiments described herein. DETAILED DESCRIPTION

[0046] To aid understanding, a series of examples will first be presented before describing a detailed description of the underlying implementation. It should be noted that these examples are merely illustrative, and the present invention is not limited to the embodiments shown.

[0047] Reference is now made to the accompanying drawings, in which like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding thereof. However, novel embodiments may be practiced without these specific details. In other cases, well-known structures and devices are shown in the form of block diagrams for ease of description thereof. It is intended to cover all modifications, equivalents, and substitutes consistent with the claimed subject matter.

[0048] In the drawings and accompanying description, the names "a", "b", and "c" (and similar designations) are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value of a=5, the complete set of components 122, shown as components 122-1 through 122-a, may include components 122-1, 122-2, 122-3, 122-4, and 122-5. The embodiments are not limited in this context.

[0049] These and other features will be described in more detail below with reference to the accompanying drawings.

[0050] For purposes of illustration, FIG. 1 is a schematic diagram of an analytical chemistry system 100 that may be used in conjunction with the techniques herein. Figure 1 A specific type of device is depicted in a specific liquid chromatography / mass spectrometry (LCMS) configuration, but one of ordinary skill in the art will appreciate that different types of chromatography devices (eg, MS, tandem MS, etc.) may also be used in conjunction with the present disclosure.

[0051] The sample 102 is injected into the liquid chromatograph 104 via the injector 106. The pump 108 can pump the sample through the chromatography column 110 to separate the mixture into component parts according to the retention time through the chromatography column.

[0052] The output from the chromatographic column is input into a mass spectrometer 112 for analysis. Initially, the sample is desolvated and ionized by a desolvation / ionization device 114. Desolvation can be any desolvation technique, including, for example, a heater, a gas, a combination of a heater and a gas, or other desolvation techniques. Ionization can be achieved using any ionization technique, including, for example, electrospray ionization (ESI), atmospheric pressure chemical ionization (APCI), matrix-assisted laser desorption (MALDI), or other ionization techniques. The ions produced by the ionization are sent into a collision cell 118 by a voltage gradient being applied to an ion guide 116. The collision cell 118 can be used to transfer ions (low energy) or to fragment ions (high energy).

[0053] A different technique can be used, where an alternating voltage can be applied across the collision cell 118 to induce fragmentation. Spectra are collected of the precursor at low energy (no collision) and of the fragments at high energy (products of collision).

[0054] The output of the collision cell 118 is input to a mass analyzer 120. The mass analyzer 120 can be any mass analyzer, including a quadrupole, a time of flight (TOF), an ion trap, a magnetic sector mass analyzer, and a combination thereof. The detector 122 detects ions emitted from the mass analyzer 122. The detector 122 can be integrated with the mass analyzer 120. For example, in the case of a TOF mass analyzer, the detector 122 can be a microchannel plate detector that counts ion intensities (i.e., counts incident ions).

[0055] The raw data repository 124 can provide permanent storage for storing ion counts for analysis. For example, the raw data repository 124 can be an internal or external computer data storage device, such as a disk, a flash-based storage device, etc. The analysis 126 analyzes the stored data. The data can also be analyzed in real time without being stored in the storage medium 124. In real-time analysis, the detector 122 passes the data to be analyzed directly to the analysis 126, rather than first storing it in permanent storage.

[0056] Collision cell 118 performs fragmentation of precursor ions. Fragmentation can be used to determine the primary sequence of peptides and subsequently identify the origin protein. Collision cell 118 comprises a gas, such as helium, argon, nitrogen, air or methane. When charged precursors interact with gas atoms, the collisions produced can fragment the precursors by decomposing the precursors into the resulting fragment ions. This fragmentation can be achieved by switching the voltage in the collision cell between a low voltage state (e.g., low energy, <5V) and a high voltage state (e.g., high energy or elevated energy, >15V). High voltage and low voltage can be referred to as high energy and low energy, because high voltage or low voltage is used, respectively, to give kinetic energy to ions.

[0057] Various protocols may be used to determine when and how to switch voltages for such MS / MS acquisitions.After data acquisition, the resulting spectra may be extracted from the raw data repository 124 and displayed and processed by post-acquisition algorithms in analysis 126.

[0058] Metadata describing various parameters related to data collection may be generated with the raw data. This information may include the configuration of the liquid chromatograph 104 or mass spectrometer 112 (or other chromatographic device that collected the data), which may define the data type. An identifier (e.g., a key) of a codec configured to decode the data may also be stored as part of the metadata and / or with the raw data. The metadata may be stored in a metadata catalog 130 in the document repository 128.

[0059] Analysis 126 may operate according to a workflow that describes a scientific method, process, or algorithm for analyzing data. A workflow may describe how to parameterize hardware, standardize output, process data, etc. Analysis 126 may provide visualization of data to the analyst at each of the workflow steps and allow the analyst to generate output data by performing processing specific to the workflow step. Workflows may be generated and retrieved via a client browser 132. As analysis 126 executes the steps of a workflow, it may read raw data from a data stream located in a raw data repository 124. As analysis 126 executes the steps of a workflow, it may generate processed data stored in a metadata catalog 130 in a document repository 128; alternatively or in addition, the processed data may be stored in different locations specified by a user of analysis 126. It may also generate audit records that may be stored in an audit log 134.

[0060] The example embodiments described herein may be executed at, among other locations, the client browser 132 and the analysis 126 . Fig.11 One example of a device suitable for use as analysis 126 and / or client browser 132 and various data storage devices is depicted in FIG.

[0061] Figure 2 Depicted are examples of the manner in which a workflow may be displayed in a user interface of a workflow builder (eg, as may be displayed on a client browser 132 as previously described).

[0062] In the user interface, a set of steps 202a-202g are arranged in sequence. The user may be provided with a set of steps that may be arranged in the interface or may be selected from a number of pre-generated templates. The user may be allowed to move steps in sequence, although the workflow builder may enforce the relative ordering of certain steps (e.g., requiring that the integrate peak step 202c be performed before the calibrate step 202e).

[0063] Some or all of these steps may be separated by transitions 204a to 204c. Transitions may be associated with directions (e.g., allowing movement in a forward direction, a reverse direction, or a forward and reverse direction in sequence). An application implementing a workflow may enforce transitions by only allowing movement in the workflow as indicated by the transitions. At each transition, the application may enforce changes in data management; responsibility for data may change from a user group associated with the step before the transition to a user group associated with the step after the transition. The application may require a signature from a user group that waives and / or acquires data access rights.

[0064] Each of steps 202a to 202g can be associated with one or more pages that define different configurations for the step (e.g., configuration and arrangement of visual elements, settings for steps and / or visual elements, etc.). The workflow builder can receive a selection of one of steps 202a to 202g via a user interface, and in response, can display images of pages that can be used with the selected step. These images can show different configurations and arrangements of visual elements for the step. Upon receiving a selection of an image associated with one of the pages, the system can associate the page with the selected step. The page can define instructions on how to arrange and configure visual elements / steps. An application that implements the workflow can retrieve page definitions and apply these page definitions to configure the visual elements / steps implemented by the application. Figure 2 Examples of pages 206a through 206g that have been selected for and associated with each of steps 202a through 202g are provided.

[0065] The data output by analytical chemistry system 100 can be stored in a table and organized into fields, which represent the values ​​of specific measurements in multiple different samples or experiments. More generally, a field can be a collection of data elements of the same type. Custom fields can be used at different stages in a workflow. Custom fields can define user-specified formulas that can be used in the processing performed by the workflow. In some embodiments, a user can use a keyboard to manually enter a custom field during data acquisition or in a method editor.

[0066] In some analytical chemistry systems, fields (including custom fields) can be interpreted as vectors. When a vector contains only one element, the field becomes a scalar. Custom fields are defined by formulas that operate on other fields, constants, and operators to produce user-specified results.

[0067] Operators can be divided into two types: vector operators and vectorized operators. Vector operators (or functions) treat the fields they operate on as sets and return a scalar or a subset of the set (e.g., summary statistics functions). Examples of vector operators include counting the number of valid data points in a field, averaging data points, calculating the standard deviation or variance of a field, determining the maximum or minimum element of a field, returning an element at a given index, etc. Vectorized operators are those in which the operator is applied to the elements of the operands and returns a vector of the same size as at least one of the operands. For example, using the addition operand "+", the formula "a+b" requires that fields "a" and "b" are vectors of the same size, or one of them is a scalar:

[0068] (1) If a and b are vectors of the same size, then a+b={a[i]+b[i]},

[0069] (2) If a is a scalar, then a+b={a+b[i]},

[0070] (3) If b is a scalar, then a+b={a[i]+b}, or

[0071] (4) If a and b are both vectors but of different sizes, then a+b=invalid (empty).

[0072] The operands of the operator can be:

[0073] Constants as scalars

[0074] As another field of a vector

[0075] As another operator for nested operations

[0076] In a custom field, the elements in the vector are determined by the scope of the calculation and the object containing the data elements of the field to which the field is associated.

[0077] For example, consider an experiment involving injecting a compound containing three components (A, B, and C) into an analytical chemistry system and then measuring the amount of each component detected. The analytical chemistry system may generate data in a table with a field called "amount", where "amount" may be a vector defined by the following formula:

[0078] = {amount[i]}, where i is the component index

[0079] For each experimental run, the amount of each component can be measured where another sample of the compound is injected into the analytical chemistry system.

[0080] The following table shows an example of data collected during three injections of a compound:

[0081]

[0082] Consider a calculation for a custom field called AvgAmount, which computes the average of its operand (in this case, the Amount field). The scope applied to the calculation can change the result stored in the custom field (and / or the size or other characteristics of the field).

[0083] For example, by default, the calculation can be performed for each injection. In this case:

[0084] For injection 1, volume = {1, 2, 3}, AVG (volume) = 2

[0085] For injection 2, volume = {4, 5, 6}, AVG (volume) = 5

[0086] For injection 3, volume = {7, 8, 9}, AVG (volume) = 8

[0087] Another possible scope is "Every component in sample". In this scope, the calculation is performed for each component in all 3 injections:

[0088] For component A, amount = {1, 4, 7}, AVG (amount) = 4

[0089] For component B, amount = {2, 5, 8}, AVG (amount) = 5

[0090] For component C, amount = {3, 6, 9}, AVG (amount) = 6

[0091] Another possible scope is "all components in sample", in which case a single calculation is performed for all components in all 3 injections:

[0092] ·Amount = {1, 2, 3, 4, 5, 6, 7, 8, 9}, AVG (amount) = 6 (amount) = 5

[0093] The following table depicts another example showing how the range set for the calculation of the peak custom field affects the results. Consider the peak calculation AvgArea = AVG(Area) for the following data:

[0094]

[0095] When the scope is Default, the calculation is performed for each channel in each injection:

[0096] For channel 1 in injection 1, area = {1, 2}, AVG(area) = 1.5

[0097] For channel 2 in injection 1, area = {3, 4}, AVG(area) = 3.5

[0098] For channel 1 in injection 2, area = {5, 6}, AVG(area) = 5.5

[0099] For channel 2 in injection 2, area = {7, 8}, AVG(area) = 7.5

[0100] For channel 1 in injection 3, area = {9, 10}, AVG(area) = 9.5

[0101] For channel 2 in injection 3, area = {11, 12}, AVG(area) = 11.5

[0102] When the scope is set to "Every channel in sample", the calculation is performed for each channel of all 3 injections:

[0103] For channel 1 in 3 injections, area = {1, 2, 5, 6, 9, 10}, AVG(area) = 5.5

[0104] For channel 2 in 3 injections, area = {3, 4, 7, 8, 11, 12}, AVG(area)

[0105] =7.5

[0106] When the scope is set to "All channels in all samples", the calculation is performed for all channels in all 3 injections:

[0107] For all channels in all 3 injections, the area

[0108] ={1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12}, AVG(area)=6.5

[0109] The available scopes may depend on the fields used to organize the data.

[0110] The formula for a custom field can have a recursive tree structure of "nodes". Each "node" can contain an operator and its operands. Each operand can contain nested nodes. Figure 3 An example of representing a formula as a tree structure consisting of nodes is depicted. In this example, any non-leaf node can represent an operator 302a, ..., 302c. A leaf node can represent an operand 304a, ..., 304e. The leaf node itself can represent a nested tree (in this case, operand 304a is a nested tree including an operator 302c that operates on operands 304d, 304e.

[0111] According to an exemplary embodiment, a recursive tree structure can be used as an example to construct a custom field formula. Figure 3 , build the formula from top to bottom in the following steps:

[0112] Add node operator 1.

[0113] Attach node operator2 to the first operand of operator1.

[0114] Fill the operand of operator 2 with a constant or a field.

[0115] Attach node operator3 to the second operand of operator2.

[0116] Fill the operand of operator 3 with a constant or a field.

[0117] • More nodes can be attached to the operand of a nested node.

[0118] In the tree structure, each node can be a recursive structure of the following style:

[0119] Node Type {

[0120] Public string ID;

[0121] Public string Op;

[0122] public List<Node> operands;}

[0123] You can use representations such as Figure 3 ), a tree structure is graphically constructed in the tree view. The tree structure can also be constructed in the formula editor view, where new nodes are defined to include placeholder operators and operands. The user can select elements from a list of available operators and operands to fill in the placeholders, as in Figure 4 In the interface shown in .

[0124] The exemplary interface is divided into several different components. The workflow stage viewer 402 shows an overview of the different stages of the workflow used in processing analytical chemistry data and highlights the currently active stage. The rest of the interface may differ depending on which workflow stage is currently active - in this example, the "identify components" stage is selected, and therefore options appropriate for that stage are displayed.

[0125] For example, the interface includes an injection viewer 404 showing injections run as part of the experiment, and a component viewer 406 showing components identified in the injections. In some embodiments, the user may be able to change the view to show peaks corresponding to components or raw chromatographic data.

[0126] When a user defines a custom field for data, the custom field may be shown in the interface. The user may select the selected custom field 408 (e.g., from a drop-down menu) to edit in the interface. Upon selection, custom field settings 410 for the custom field may be displayed; some of the options for these settings are shown in the Figure 5 Shown in.

[0127] The custom field editor 412 may allow a user to edit a custom field using placeholders. When a new custom field is defined, the custom field may initially be populated with a single interactive placeholder, which is a generic representation that may be replaced by specific operators and / or operands. As operators are added to replace existing placeholders, new placeholders may be added (depending on how many operands the added operator accepts), allowing the custom field formula to grow dynamically. For example, Figure 4 A placeholder operand 418 and a placeholder operator 420 are shown.

[0128] Users can interact with placeholders in a variety of ways. For example:

[0129] • It can be edited directly for the user to enter a constant.

[0130] It accepts drag and drop of operators or operands for the user to add or replace nodes corresponding to placeholders. The workspace contains an available operator list 416 and an available field list 414, which respectively show the operators and fields that can be used for calculations. The listed operators or fields can be dragged and dropped onto the placeholders in the above view. Once an operator or field is dragged and dropped onto an existing placeholder to create a child node, a placeholder is immediately created in the view for the operand of the newly added operator or field.

[0131] The user can mouse over a placeholder which displays a tooltip. When a placeholder is replaced by a node containing an operator or operand, the node remains interactive (e.g., accepts new values ​​as in the example above) and mouseovering the placeholder displays a description of the operator or operand.

[0132] Double-clicking a placeholder / node expands or collapses the node in the formula editor or other related views

[0133] Incomplete nodes may be highlighted as errors.

[0134] When a custom field formula is built in the formula editor, the resulting tree can be validated by applying conversion rules. When the first node is added for a custom field, the conversion rules may require that the return type from the new node should match or be convertible to the data type of the custom field. When a nested node is added to an operand of a parent node, the conversion rules are applied so that the return type from the nested node should match or be convertible to the expected type of the operand.

[0135] When replacing an existing node with a new "same" node, all existing operands may be maintained without interrupting existing branches. An "same" node may be a node with the same number and type of operands. For example, a binary arithmetic operator in a branch may be replaced by another binary arithmetic operator without interrupting the existing branch.

[0136] When an existing node is replaced by a new node with a valid return type but the number and type of operands do not match, the existing branch may be interrupted. When an existing node is replaced by the same operator but different operands (e.g., optional arguments), the existing operands of the same type may be maintained.

[0137] When an existing node is deleted, the branch may be broken and the entire formula may become invalid until the operands from which it was separated are filled again with constants, fields, or new nodes.

[0138] Additional tabs may allow the user to switch between different views of the formula editor. For example, a tree view tab may allow the formula to be viewed and edited in a tree view (see, e.g., Figure 3 )

[0139] Figure 5 An example of a wizard for customizing field settings is depicted. The wizard may be displayed in the formula editor interface, or displayed separately as a pop-up window. For example, the wizard allows definition of various field identifiers 502 for the field, such as the name of the field, a short name of the field to be displayed in the interface, and / or a brief description of the field.

[0140] Field type 504 describes the format of the field (e.g., the type of data structure into which the members of the field will fit). Field type 504 can therefore determine many other settings. Changing the type can cause the backend to refresh to provide a different list of fields that can be used for calculations. Some examples of types include a "component" type representing the components of a sample, a "peak" type that is a calculated value, a "sample" type representing an injected sample, etc.

[0141] Additionally, the wizard may include a scope setting 506, allowing the scope of the calculation of the field to be defined as described in detail above.

[0142] Figure 6 An example of an operator and field picker 600 is shown, which shows the available operators and fields and may allow a user to select or drag and drop items into the formula editor. The operator and field picker 600 may be displayed in the formula editor interface, or displayed separately as a pop-up window.

[0143] The operator and field picker 600 may include an available operator list 602, which lists the different operators that may be incorporated into the node. The available operators may depend on which operators are supported by the environment hosting the analytical chemistry system.

[0144] Constant input box 604 may allow a user to enter a value using a keyboard, wherein the value will be used as a constant in the custom field formula. Available fields list 606 displays the different fields that can be used as operands for the custom field.

[0145] The formula can optionally be viewed in a text-based mode, such as Fig. 7A and Figure 7B . The text representation view 700 may include a text box 702 that displays a text-based representation of a custom field formula.

[0146] The text box 702 may be read-only, so that the user cannot edit the formula in the text box 702 (which may destroy the tree structure representing the custom field formula, and this may be an error-prone way to edit the custom field). However, the text box 702 may allow the user to copy and paste the custom field. For example, a traditional custom field formula may be copied into the text box 702, which causes the system to parse the custom field formula and convert it into a tree structure representation.

[0147] When building the tree structure, the parser may apply precedence and associativity rules to define the parser grammar for "infix" notation. An example of such precedence and associativity rules is as follows:

[0148] Parentheses take precedence over all other operators.

[0149] The operator ^ (exponentiation) takes precedence over the arithmetic operators / , *, -, and +.

[0150] · Binary operators * and / take precedence over - and +.

[0151] The unary operator - takes precedence over the binary operators - and +.

[0152] • The operator ^ is right-associative, whereas all other operators are left-associative.

[0153] Use priority climbing.

[0154] For example, the first three rules tell us the following formula:

[0155] a^b*c^d+e^f / g^(h+i)

[0156] is parsed into the following tree:

[0157] +(*(^(a,b),^(c,d)), / (^(e,f),^(g,+(h,i))))

[0158] However, the last rule tells us that using the priority climbing rule, abc is parsed as -(-(a, b), c) instead of -(a, -(b, c)), while a^b^c is parsed as ^(a, ^(b, c)) instead of ^(^(a, b), c). 1.7.7

[0160] The text box 702 may display a cursor position 704 representing the currently selected position within the custom field formula. Although the user may not be able to directly edit the custom field formula at the cursor position 704 in the text box 702, the text box 702 may still be interactive. For example, the cursor node identifier 706 may display the data of the node that exists at the location of the cursor position 704. Optionally, the user may interact with the node using the text box 702 (e.g., by double-clicking at the cursor position 704) to collapse or expand the node.

[0161] For example, Figure 7B Depicted is the text representation view 700 after a user has interacted with the text box 702 at the cursor position 704, causing collapsed text 708 to be displayed in place of the text representation of the node at the cursor position 704. Double-clicking the collapsed text 708 may cause the text to expand back to the original text box. Fig. 7A 's view.

[0162] When a node is selected in the text representation view 700, additional options may be presented in the cursor node identifier 706. Although the user may not be able to edit the node in the text box 702, the options in the cursor node identifier 706 may include:

[0163] When an empty node is selected, you can add / insert operators, fields, or constants to the empty node (e.g., using Figure 6 A formula from another custom field can also be inserted into an empty node.

[0164] When the body of a non-empty node is selected, it can be replaced by another (compatible) operator, field or constant. A formula from another custom field can also be inserted into the node. Non-empty nodes can also be deleted or cleared.

[0165] • When the beginning of a non-empty node is selected, an operator may be inserted to the left of the node, and the original node then becomes the right operand of the newly inserted operator.

[0166] • When the end of a non-empty node is selected, an operator may be inserted to the right of the node, and the original node then becomes the left operand of the newly inserted operator.

[0167] Another type of view is Fig. 8A 800 of the formula renderer 800. In this example, the custom field formula is depicted as a mathematical equation using the equation renderer. The user can view the text representation view 700 in a similar manner, such as by collapsing the selected node into Figure 8B Collapse node 802 is shown to interact with the formula renderer 800.

[0168] The formula renderer view helps create and edit complex formulas, especially those that include multiple division operators. For example, Fig. 9 A particularly complex formula 900 including four division operators is depicted. In a different view, such as in a text representation view, the operands of the division operator would depend on the number and position of parentheses, which could be complex and clutter the interface. With the formula renderer view, the operation of the nested division operators is easier to discern.

[0169] Fig.10 1 is a flow chart depicting an exemplary custom field formula logic 1000 for performing a computer-implemented method according to an exemplary embodiment. The logic may be embodied as instructions stored on a computer-readable medium, the instructions being configured to be executed by a processor. The logic may be implemented by a suitable computing system configured to perform the actions described below.

[0170] Processing begins at block 1002; for example, processing may begin when a user runs a software application that includes functionality for defining custom field formulas.

[0171] In block 1004, the system may receive access data. The data may be analytical chemistry data generated by one or more laboratory analytical instruments in an analytical chemistry system. The data may be organized into one or more fields.

[0172] In block 1006, the system may display a formula editor workspace such as Figure 4 The formula editor workspace may provide one or more options for creating or editing custom fields for the data accessed at block 1004. The options displayed in the formula editor workspace may depend on the fields in the data and / or the operators and functions supported by the analytical chemistry system.

[0173] In block 1008, the system can receive a request to define a custom field. For example, the system can detect a request from a user to create a new custom field or load an existing custom field for viewing and / or editing.

[0174] In block 1010 , the system may receive a selection of an interface view for viewing and / or editing a custom field formula.

[0175] If the selection is for the formula editor view, then in block 1012, the system may display a window similar to Figure 4 (If no selection is made, the system may optionally default to this view.) If the selection is for a tree view, then at block 1014 the system may select a view similar to Figure 3The custom field formula is represented as a tree in the tree view depicted in FIG. If the selection is for math, then at box 1016, the system may display a window similar to Fig. 8A and Figure 8B A view of the mathematical representation depicted in .

[0176] If the selection in block 1010 is a selection of a text representation view, then in block 1018 the system may display a view similar to Fig. 7A and Figure 7B The text representation of the custom field formula depicted in . The text representation can be displayed in a text box; optionally, as described above in conjunction with Fig. 7A and Figure 7B As described, in block 1020 , the system may receive a pasted formula in a text box and may parse the pasted formula in block 1022 .

[0177] In block 1024, the system may receive a selection of a node in the currently displayed interface view. The node may be an existing node or an interactive placeholder. As described above, when a node is selected, different types of interactions may be performed. For example,

[0178] When an empty node is selected, you can add / insert operators, fields, or constants to the empty node (e.g., using Figure 6 A formula from another custom field can also be inserted into an empty node.

[0179] When the body of a non-empty node is selected, it can be replaced by another (compatible) operator, field or constant. A formula from another custom field can also be inserted into the node. Non-empty nodes can also be deleted or cleared.

[0180] • When the beginning of a non-empty node is selected, an operator may be inserted to the left of the node, and the original node then becomes the right operand of the newly inserted operator.

[0181] • When the end of a non-empty node is selected, an operator may be inserted to the right of the node, and the original node then becomes the left operand of the newly inserted operator.

[0182] For brevity, the remainder of the flowchart assumes that the selected node is an empty interactive placeholder (eg, the first scenario described above). One of ordinary skill in the art will appreciate that the depicted custom field formula logic 1000 can be easily modified to account for other scenarios described above.

[0183] In block 1026, the system may receive a selection of an operator or operand that should replace the interactive placeholder (block 1028). For example, the system may display a list of available operators, and the user may select one of the operators in the list to have the selected operator replace the placeholder in the custom field. When an operator is selected, a new interactive placeholder representing the operand of the operator may be generated and displayed in the selected view. In another example, the system may display a list of available fields or other operands, and the user may select one of the fields / operands in the list to replace the interactive placeholder.

[0184] In decision block 1030, the system determines whether more interactions remain to be processed. For example, if the user selects another node (or the same node as the previously edited node), processing can return to block 1024 and the system can edit the newly selected node. If the user selects another interface view, processing can return to block 1010 and the system can display the custom field being edited in the new view.

[0185] Before or after the interaction is completed, the system can identify the scope of the custom field formula in block 1032. For example, the user can specify the scope in the settings interface (see, e.g. Figure 4 and Figure 5 ).

[0186] Once the custom field is edited, the system may associate the custom field with a specific workflow stage of the analytical chemistry system in block 1034. The custom field may have been created in an interface specifically associated with a specific stage of the workflow, which may make certain fields available for the custom field (see, e.g., Figure 4 ). In some embodiments, associating a custom field with a workflow stage may involve: processing the custom field with a stage processor in block 1036.

[0187] To process custom fields, a stage handler can perform the following actions:

[0188] Collect all custom field calculations during the processing phase.

[0189] Some custom fields depend on other custom and non-custom fields. Therefore, the calculation of fields should be ordered according to their dependencies.

[0190] Resolve the constants in each formula as scalars.

[0191] Cycle through the injections or components of the experiment based on the "scope" of each calculation to retrieve the fields used as vectors in the calculation and populate all nodes that use the same fields.

[0192] · Calculate the result of each node from bottom to top.

[0193] Any error or warning codes that populate custom fields.

[0194] Processing may then proceed to completion block 1038 and terminate.

[0195] although Fig.10 Specific actions are depicted as being performed in a specific order, but the embodiments are not limited to Fig.10 It is contemplated that more, fewer, or different logic blocks may be implemented. Similarly, it is contemplated that Fig.10 The actions may be performed in an order different from the order shown.

[0196] Fig.11 An example of a system architecture and data processing device that can be used to implement one or more illustrative aspects described herein in a standalone and / or networked environment is shown. Various network nodes such as data server 1110, web server 1106, computer 1104, and laptop computer 1102 can be interconnected via a wide area network (WAN) 1108 (such as the Internet). Other networks can also or alternatively be used, including a private intranet, an enterprise network, a LAN, a metropolitan area network (MAN), a wireless network, a personal network (PAN), etc. Network 1108 is for illustrative purposes and can be replaced by fewer or more computer networks. A local area network (LAN) can have one or more topologies in any known LAN topology, and can use one or more protocols in a variety of different protocols, such as Ethernet. Device data server 1110, web server 1106, computer 1104, laptop computer 1102 and other devices (not shown) can be connected to one or more networks in the network via twisted pair, coaxial cable, optical fiber, radio waves or other communication media.

[0197] The computer software, hardware, and networks may be used in a variety of different system environments, including stand-alone, networked, remote access (also known as remote desktop), virtualized, and / or cloud-based environments, among others.

[0198] The term "network" as used herein and depicted in the accompanying drawings refers not only to a system in which remote storage devices are coupled together via one or more communication paths, but also to independent devices that may be coupled to such a system from time to time with storage capabilities. Thus, the term "network" includes not only a "physical network" but also a "content network" consisting of data residing on all physical networks that can be attributed to a single entity.

[0199] Components may include a data server 1110, a web server 1106, a client computer 1104, and a laptop computer 1102. The data server 1110 provides overall access, control, and management of databases and control software for performing one or more illustrative aspects described herein. The data server 1110 may be connected to a web server 1106, through which a user interacts with the requested data and obtains the data. Alternatively, the data server 1110 itself may act as a web server and be directly connected to the Internet. The data server 1110 may be connected to the web server 1106 via a network 1108 (e.g., the Internet), via a direct or indirect connection, or via some other network. A user may interact with the data server 1110 using a remote computer 1104, a laptop computer 1102, such as using a web browser to connect to the data server 1110 via one or more external public web sites hosted by the web server 1106. The client computer 1104, a laptop computer 1102 may be used with the data server 1110 to access data stored therein, or may be used for other purposes. For example, from a client computer 1104, a user may access the web server 1106 using an Internet browser (as is known in the art) or by executing a software application that communicates with the web server 1106 and / or data server 1110 via a computer network (such as the Internet).

[0200] The server and application can be combined on the same physical machine and retain separate virtual or logical addresses, or can reside on separate physical machines. Fig.11 Only one example of a network architecture that may be used is shown, and those skilled in the art will appreciate that the specific network architecture and data processing devices used may vary and are secondary to the functionality they provide, as further described herein. For example, the services provided by web server 1106 and data server 1110 may be combined on a single server.

[0201] Each component data server 1110, web server 1106, computer 1104, laptop computer 1102 can be any type of known computer, server or data processing device. Data server 1110 can include, for example, a processor 1112 that controls the overall operation of data server 1110. Data server 1110 can also include RAM 1116, ROM 1118, network interface 1114, input / output interface 1120 (e.g., keyboard, mouse, display, printer, etc.) and memory 1122. Input / output interface 1120 can include various interface units and drivers for reading, writing, displaying and / or printing data or files. Memory 1122 can also store operating system software 1124 for controlling the overall operation of data server 1110, control logic 1126 for instructing data server 1110 to perform various aspects described herein, and other application software 1128 that provides auxiliary, support and / or other functions that can be used in conjunction with or without the various aspects described herein. Control logic may also be referred to as data server software control logic 1126 in this article. The functionality of the data server software may refer to a combination of operations or decisions made automatically based on rules encoded into the control logic, manually by a user providing input to the system, and / or automatic processing based on user input (e.g., queries, data updates, etc.).

[0202] The memory 1122 may also store data for performing one or more aspects described herein, including a first database 1132 and a second database 1130. In some embodiments, the first database may include the second database (e.g., as a separate table, report, etc.). That is, the information may be stored in a single database, or divided into different logical, virtual or physical databases, depending on the system design. The web server 1106, computer 1104, laptop computer 1102 may have an architecture similar to or different from that described with respect to the data server 1110. Those skilled in the art will appreciate that the functionality of the data server 1110 (or web server 1106, computer 1104, laptop computer 1102) as described herein may be distributed across multiple data processing devices, for example, to distribute processing loads across multiple computers, to separate transactions based on geographic location, user access level, quality of service (QoS), etc.

[0203] One or more aspects may be embodied in computer-usable or readable data and / or computer-executable instructions, such as embodied in one or more program modules executed by one or more computers or other devices as described herein. Typically, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. These modules can be written in source code programming languages, which are then compiled for execution, or these modules can be written in scripting languages ​​such as (but not limited to) HTML or XML. Computer executable instructions can be stored on a computer-readable medium such as a non-volatile storage device. Any suitable computer-readable storage medium can be used, including hard disks, CD-ROMs, optical storage devices, magnetic storage devices, and / or any combination thereof. In addition, various transmission (non-storage) media representing data or events as described herein can be transmitted between a source and a destination in the form of electromagnetic waves propagated through a signal-conducting medium such as a metal wire, an optical fiber, and / or a wireless transmission medium (e.g., air and / or space). The various aspects described herein can be embodied as a method, a data processing system, or a computer program product. Thus, the various functions may be embodied in whole or in part in software, firmware, and / or hardware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGAs), etc. Certain data structures may be used to more efficiently implement one or more aspects described herein, and such data structures are contemplated to be within the scope of the computer-executable instructions and computer-usable data described herein.

[0204] The components and features of the devices described above may be implemented using any combination of discrete circuit systems, application specific integrated circuits (ASICs), logic gates, and / or single chip architectures. In addition, where appropriate, microcontrollers, programmable logic arrays, and / or microprocessors, or any combination of the foregoing, may be used to implement the features of these devices. It should be noted that hardware, firmware, and / or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

[0205] It should be understood that the exemplary devices shown in the above block diagrams may represent a functional descriptive example of many possible specific implementations. Therefore, the division, omission or inclusion of block functions depicted in the drawings does not mean that the hardware components, circuits, software and / or elements used to implement these functions will necessarily be divided, omitted or included in the implementation.

[0206] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.

[0207] Some embodiments may be described using the expressions "one embodiment" or "an embodiment" and their derivatives. These terms mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The appearance of the phrase "in one embodiment" in different places in the specification does not necessarily refer to the same embodiment. In addition, unless otherwise stated, the above-mentioned features are considered to be usable together in any combination. Therefore, any features discussed separately may be used in combination with each other unless it is stated that these features are incompatible with each other.

[0208] The detailed description herein may be presented in terms of program processes executed on a computer or computer network with general reference to the notations and nomenclature used herein. These program descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art.

[0209] A process is generally considered to be a self-consistent sequence of operations that brings about a desired result. These operations are those requiring physical manipulation of physical quantities. Although not required, these quantities usually take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise manipulated. In practice, it has proven convenient at times to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc., primarily for common reasons. It should be noted, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.

[0210] In addition, the manipulations performed are often referred to by terms such as adding or comparing, which are often associated with mental operations performed by a human operator. In any of the operations described herein that form a part of one or more embodiments, in most cases, such capabilities of a human operator are not necessary or desirable. Instead, these operations are machine operations. Useful machines for performing the operations of the various embodiments include general purpose digital computers or similar devices.

[0211] The expressions "coupled" and "connected," as well as their derivatives, may be used to describe some embodiments. These terms are not necessarily intended to be synonymous with each other. For example, the terms "connected" and / or "coupled" may be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

[0212] Various embodiments also relate to devices or systems for performing these operations. The device may be specially constructed for the desired purpose, or it may include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. The processes presented herein are not inherently related to a particular computer or other device. Various general-purpose machines may be used with programs written according to the teachings of this article, or it may prove convenient to construct more specialized devices to perform the desired method steps. The desired structures of various of these machines will appear in the description given.

[0213] It should be emphasized that the abstract of the present disclosure is provided so as to allow the reader to quickly determine the essence of the technical disclosure. It should be understood that the submitted abstract will not be used to interpret or limit the scope or meaning of the claims. In addition, in the aforementioned specific embodiments, it can be seen that various features can be grouped together in a single embodiment for the purpose of simplifying the present disclosure. This method of the present disclosure should not be interpreted as reflecting the intention that the claimed embodiment requires more features than the features explicitly stated in each claim. On the contrary, as reflected in the following claims, the subject matter of the present invention is less than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the specific embodiments, wherein each claim exists independently as a separate embodiment. In the appended claims, the terms "including" and "in which" are used as the colloquial English equivalents of the corresponding terms "comprising" and "wherein", respectively. In addition, the terms "first", "second", "third", etc. are used only as labels and are not intended to impose numerical requirements on their objects.

[0214] What has been described above includes examples of the disclosed architecture. Of course, it is not possible to describe every conceivable combination of components and / or methods, but one of ordinary skill in the art will recognize that many further combinations and permutations are possible. Therefore, the novel architecture is intended to encompass all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. A computer-implemented method, the computer-implemented method comprising: accessing data from a laboratory analytical instrument associated with an analytical method encoded in the workflow, the data organized into one or more fields; receiving a request to define a custom field for use in a stage of a workflow, the custom field being associated with a custom field calculation; Displaying a formula editor workspace in an interface, the workspace including a list of one or more fields of data, a list of available operators, and a formula editor including interactive placeholders; Do at least one of the following: receiving a selection of one of the available operators and incorporating the selected operator into the custom field in place of the interactive placeholder, or receiving a selection of one of the one or more fields and incorporating the selected field into the custom field in place of the interactive placeholder; as well as The custom field is associated with a stage of the workflow, the association making the custom field accessible to the workflow. 2 . The computer-implemented method of claim 1 , further comprising calculating a value of the custom field during the phase of the workflow.

3. The computer-implemented method of claim 1 , wherein the analytical method performs measurements on one or more injections into the laboratory analytical instrument, each injection comprising one or more components, and the computer-implemented method further comprises receiving a range for the custom field, the range specifying that the custom field calculation should be applied to: All components of each injection, For each component in all injections, All components in all injections, or Peaks in the data.

4. The computer-implemented method of claim 1 , further comprising: Receive selection of tree view interface element; as well as The custom field is displayed as a tree including a set of nodes representing operators and a set of leaf nodes representing operands.

5. The computer-implemented method of claim 1 , further comprising: Receive selection of a formula renderer interface element; as well as Displaying the custom field in mathematical notation in a formula renderer view.

6. The computer-implemented method of claim 1 , further comprising: A text representation of the custom field is displayed in a text box in the interface, wherein the text box is configured to receive a pasted formula from a clipboard but is configured to not allow editing of the formula within the text box. 7 . The computer-implemented method of claim 6 , further comprising displaying a cursor in the text box at a position corresponding to a current editing action of the custom field.

8. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: accessing data from a laboratory analytical instrument associated with an analytical method encoded in the workflow, the data organized into one or more fields; receiving a request to define a custom field for use in a stage of a workflow, the custom field being associated with a custom field calculation; Displaying a formula editor workspace in an interface, the workspace including a list of one or more fields of data, a list of available operators, and a formula editor including interactive placeholders; Do one or more of the following: receiving a selection of one of the available operators and incorporating the selected operator into the custom field in place of the interactive placeholder, or receiving a selection of one of the one or more fields and incorporating the selected field into the custom field in place of the interactive placeholder; as well as The custom field is associated with a stage of the workflow, the association making the custom field accessible to the workflow.

9. The computer-readable storage medium of claim 8, wherein the instructions further configure the computer to calculate a value of the custom field during the phase of the workflow.

10. The computer-readable storage medium of claim 8, wherein the analytical method performs measurements on one or more injections into the laboratory analytical instrument, each injection comprising one or more components, and wherein the instructions further configure the calculation to receive a range for the custom field, the range specifying that the custom field calculation should be applied to: All components of each injection, For each component in all injections, All components in all injections, or Peaks in the data.

11. The computer-readable storage medium of claim 8, wherein the instructions further configure the computer to: receiving a selection of a tree view interface element; and The custom field is displayed as a tree including a set of nodes representing operators and a set of leaf nodes representing operands.

12. The computer-readable storage medium of claim 8, wherein the instructions further configure the computer to: receiving a selection of a formula renderer interface element; and Displaying the custom field in mathematical notation in a formula renderer view.

13. The computer-readable storage medium of claim 8, wherein the instructions further configure the computer to display a text representation of the custom field in a text box in the interface, wherein the text box is configured to receive a pasted formula from a clipboard but is configured to not allow editing of the formula within the text box.

14. The computer-readable storage medium of claim 13, wherein the instructions further configure the computer to display a cursor in the text box at a position corresponding to a current editing action of the custom field.

15. A computing device, the computing device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the device to: accessing data from a laboratory analytical instrument associated with an analytical method encoded in the workflow, the data organized into one or more fields; receiving a request to define a custom field for use in a stage of a workflow, the custom field being associated with a custom field calculation; Displaying a formula editor workspace in an interface, the workspace including a list of one or more fields of data, a list of available operators, and a formula editor including interactive placeholders; Do one or more of the following: receiving a selection of one of the available operators and incorporating the selected operator into the custom field in place of the interactive placeholder, or receiving a selection of one of the one or more fields and incorporating the selected field into the custom field in place of the interactive placeholder; as well as The custom field is associated with the stage of the workflow, the association making the custom field accessible to the workflow.

16. The computing device of claim 15, wherein the instructions further configure the device to calculate a value of the custom field during the phase of the workflow.

17. The computing device of claim 15, wherein the analytical method performs measurements on one or more injections into the laboratory analytical instrument, each injection comprising one or more components, and wherein the instructions further configure the device to receive a range for the custom field, the range specifying that the custom field calculation should be applied to: All components of each injection, For each component in all injections, All components in all injections, or Peaks in the data.

18. The computing device of claim 15, wherein the instructions further configure the device to: receiving a selection of a tree view interface element; and The custom field is displayed as a tree including a set of nodes representing operators and a set of leaf nodes representing operands.

19. The computing device of claim 15, wherein the instructions further configure the device to: receiving a selection of a formula renderer interface element; and Displaying the custom field in mathematical notation in a formula renderer view.

20. The computing device of claim 15, wherein the instructions further configure the device to display a text representation of the custom field in a text box in the interface, wherein the text box is configured to receive a pasted formula from a clipboard but is configured to not allow editing of the formula within the text box.