This document pertains generally, but not by way of limitation, to circuit supply systems that provide a regulated output, and more particularly, to amplifier system systems that use digital to analog converters to provide a regulated output over a large dynamic range.
Amplifier systems can be used to as a circuit supply to provide a direct current (DC) output. These systems can be useful for example in automatic test equipment (ATE). It can be desirable for circuit supply in a test environment to have a large dynamic range. One approach to increase the dynamic range of ATE is to transition the ATE between multiple operating modes using digital to analog converters (DACs). However, using DACs in closed loop regulated supplies can cause glitching, which is undesirable.
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.
The signal gains from input (VIN) to output (VOUT) are designated as GHV and GLV for the lower resolution HV range circuit path and the higher resolution LV range circuit path, respectively, where GHV>GLV. The input to output transfer functions is determined by one of the following equations, depending on the state of the gain select switch and assuming the forward gain GF is substantially unity:
V
OUT (HV Range)
=V
IN
G
HV,
V
OUT (LV Range)
=V
IN
G
LV.
The input VIN can be normalized so that: 0V≤VIN≤1V.
However, even for only those output voltages common to both the HV and LV ranges, for a constant input voltage (VA) there will be an aberration at the output when the switch is changed between circuit paths. This is true for all operating points except the one where the two graphs intersect (at VIN 0V for the example of
The transfer function of the overall LV range is now:
V
OUT
=V
IN
G
LV
+V
X
G
X,
where gain GX may be chosen arbitrarily.
The feedback amplifier (FA) automatically adjusts input voltage VIN to the appropriate voltage so that the output (VOUT) is moved toward the desired target signal VTARGET. The amplifier system is in steady state when the output (VOUT) is held at, or near (e.g., within an error margin), the desired target signal VTARGET. The switch SW allows the amplifier system to realize the gain GHV without the GHV amplifier. With the switch in the upper setting (as shown in
The auxiliary signal gain GX and the LV signal gain GLV of the GX and GLV amplifier circuits can be adjustable. With the switch SW in the HV low-resolution mode (as shown in
In the examples of
The closed loop architectures in
The glitch energy of a glitch generated by a DAC can be defined as the net integral area of the worst-case glitch voltage waveform over time minus the endpoint adjusted step transition of the DAC.
Segmented DACs are implemented as a combination of multiple DAC architectures to obtain better linearity characteristics. Segmented DACs, which usually include both binary-weighted (LSB) and unary-weighted (MSB) segments, also require synchronous switching of multiple branches, and hence are also prone to glitches usually especially during MSB segment transitions. In segmented DACs, the high-energy glitches typically repeat periodically across the DAC code range depending on the number of MSB segments present.
In the multi-DAC systems of
If the glitch energy characteristics of a DAC (e.g., a main DAC) for all different code transitions are known a priori from previous measurements, then the DAC codes could be stored with their glitch characteristics in memory. Because the control circuit knows the current steady state of the amplifier system, the control circuit can avoid loading DAC codes with high-glitch code transitions near the steady state. Some examples of this glitch characteristic data include glitch magnitude (e.g., peak to peak magnitude), positive glitching magnitude, negative glitching magnitude, total or net glitch energy, positive glitch energy, negative glitch energy. A system's response may be optimized using a combination of these metrics. This glitch characteristic data may also be transformed or compressed to reduce memory requirements and reduce the data processing time or power in loading the appropriate DAC codes.
This many-to-one DAC code approach can also be used to avoid glitches at for a “black box” DAC in which the high-glitch code transitions may not be known or the characteristic glitch data may not be available. For example, the magnitude and sign of the DAC code corrections applied by the control circuit may be monitored while the control loop of the amplifier system is trying to settle the output at or near the steady state target. As the control loop reaches steady state near VOUT≈VTARGET, under normal conditions, the control circuit may update the DACIN code with small increments or decrements (e.g., one or two LSBs) to compensate for gradual changes e.g., due to noise, drift, etc. If loading a new set of DAC codes does not result in a reduction in glitch energy at the DAC analog output, another set of DAC codes can be loaded (e.g., from memory) and the glitch energy at the DAC analog output can be rechecked.
This monitoring may be performed in the digital domain (or software domain) and may be performed using the control circuit as part of a code-adjusting algorithm, or the monitoring may be performed using a separate monitoring circuit included in an ASIC, FPGA, microcontroller, or a processor (e.g., a microprocessor). A high glitch flag signal can be raised in the digital domain when a code update is detected that updates more than a predetermined threshold (e.g., threshold number NTHRESHOLD of LSBs) at steady state. For example, in
Other methods to detect a high glitch transition condition can be used. In some examples, the analog output of the DAC or the system output can be monitored to detect glitches. A high glitch condition may be detected by glitches that exceed a specified glitch peak threshold (in either volts or amps). In other examples, a high glitch condition can be detected by glitches that exceed a specified glitch energy (e.g., Volt-seconds or Amp-seconds). A high glitch flag signal can be raised when the control circuit detects a high glitch transition that exceeds a specified threshold transition. The high glitch threshold transition may be specified as a number of LSBs or in volts or amps. In some examples, a population-based analysis can be used. Combinations of DAC codes and target values can be tracked. Worst-case combinations can be tracked (e.g., through machine learning) to identify which DAC Code versions are likely to result in a high glitch transition condition for a given target value. The high glitch threshold transition can be adaptive based on the design of the system or machine learning algorithm of the system.
The size of the set of DAC codes which the glitch mitigation can be used for (the sub-population to be mitigated) is limited by the redundancy or contingency built into the design to enable avoiding of code(s). Hence, whilst the analysis can identify codes to be mitigated against, usually the worst-case codes, the DAC design needs to ensure there's sufficient contingency in place to address the anticipated worst case needs. In some applications, there may be particular codes or code region(s) of the transfer function which are more important in the final use case and hence glitch mitigation may be prioritized from such region(s) as part of this foresaid analysis.
When a high-glitch flag is raised, the code or codes for the DACs may be changed to a different code or codes where the steady state DAC code or codes are sufficiently far away from a high glitch transition so that a high glitch does not occur in steady state. This predetermined threshold NTHRESHOLD to cause a code update may be varied. In some examples, when a high-glitch flag is raised, an offset voltage is introduced in the loop such that the control circuit allows the main DAC or DACs in the loop to settle at one or more DAC codes sufficiently far away from the high-glitch transitions. The offset may be introduced at any point in the loop using analog means (e.g., an opamp based adder circuit) or may be introduced to the DAC codes directly in the digital domain. In addition, the reference level of one or more main DACs may be adjusted to create an offset effect or to change gain.
The glitch characteristic data may be stored in memory and may be used to calculate the amount of offset needed for a given high-glitch DAC code transition according to a pre-defined function, optimization, approximation, or machine learning algorithm. The glitch characterization technique may be implemented as foreground calibration when the system is idle or as a background calibration while the system is operational. A foreground calibration may be done during system manufacture. A foreground calibration may also be done by the user (e.g., as part of system reset or a calibration procedure). The amplifier system may adaptively adjust offset amounts as it encounters new high-glitch code transitions during operation. The glitch characterization technique may also be used to respond to a change in load of the amplifier system that results in a new steady state that is near a high glitch transition.
For instance, if VOFFSET=+ΔV is applied, the transfer function shifts to the upper VOFFSET=+ΔV line. The control loop will reduce the value of
to maintain VOUT≈VTARGET. As shown in
The peak amplitude of the glitches is relevant in closed loop applications as the glitching can show up directly as a glitch waveform or ripple at the output (VOUT) in accordance with the frequency response of the control loop of the amplifier system. In addition, if the glitch waveform at the output is sampled by the ADC, it may also cause instability in the control loop and cause additional undesirable ringing or oscillatory response at the output.
As noted previously herein, the glitch energy can be defined as the net integral area of the glitch waveform. In some applications, depending on the aperture window of the feedback ADC, the glitch energy may be more critical in terms of the response of the control circuit than the glitch peak magnitude. In other words, the control circuit may not respond significantly to a glitch waveform with low energy but high magnitude (e.g., a narrow glitch) if the ADC has a sufficiently wide aperture window due to the averaging effect. Consequently, depending on the system, it may be favorable to reduce glitch magnitude, glitch energy or both for a given application. An advantage of the glitch self-characterization and calibration techniques described herein is that the DAC code updates that are used for characterization rely on the response to DAC glitches of the ADC (e.g., the ADC 606 of
For instance, the DACX code could be incremented to force VX to increase by offset ΔVX and DACIN code could be decremented to force VIN to decrease by ΔVX*GX/GLV such that VOUT=GX*VX+GLV*VIN is maintained. The amount of offset may be controlled (e.g., using another DAC to add an adjustable offset (VOFFSET) to the summing node). Also, the offset value could be increased gradually, or using successive-approximation or other more complex search algorithms, until both DACs are comfortably in the glitch-free code space. After the offset in code space is introduced between the two DACs, the control circuit 2502 would allow the control loop to control both DACs while maintaining the fixed offset. In this way, both DACs will settle at a code region that is far away from the high-glitch boundaries to minimize ripple in the output. When the system receives an update to VTARGET the control circuit 2502 may bring the DAC codes together first before letting the loop settle to the new target VOUT value.
Regarding the LV high-resolution mode operation of the amplifier system of
As described previously herein regarding the amplifier system of
For the system architectures of
The multiple DAC architectures in the examples of
so that VOUT=VTARGET can be maintained. Therefore, the control loop will converge at a DACIN code far away from a high glitch code boundary.
At block 2730 in
At block 2740, if an offset list is available, the control circuit applies an offset to the control loop. The offset can be applied in different ways. For instance, the system can include an analog adder or subtractor circuit to apply the offset (voltage offset or current offset) to the summing node of the system as in the example of
When the DAC codes are set, the control loop of the system steers the output of the system toward the steady state output target (e.g., VOUT≈VTARGET). The control circuit may make small changes (e.g., one or two LSBs) that are less than the threshold to the DACIN code to compensate for small changes in conditions. The code updates are monitored and at block 2750 if the changes are less than the threshold (NTHRESHOLD LSBs), the control circuit continues to monitor the system stability and a glitch flag is not raised or activated.
If a main DAC code change is needed that is greater than the NTHRESHOLD LSBs, then a high-glitch flag signal is asserted or activated. At 2760, when a high-glitch code transition is encountered, the DAC codes can be recorded in memory. The control circuit (or dedicated monitoring circuit) also may record the sign magnitude of the glitch at a given transition based on peak or average code updates observed at steady state. Subsequently, a pre-determined offset value may be applied by the control circuit when a previously recorded high-glitch transition condition is expected. The pre-determined offset value may be used as part of a starting approximation to find a new steady state for the system.
At block 2770, the amount of offset to be applied for a given transition may be fixed or continuously updated based on an optimization algorithm or machine learning (ML) algorithm. For example, the amplifier system can observe DAC codes and from the DAC codes and detected glitching, the system can determine where the glitches are in the DAC codes and how much energy the glitches have. The system can deduce that the current DAC code space is in a high glitching condition and can apply one or both of DAC code changes and offsets to settle the main DAC or DACs away from the instability. Thus, the amplifier system can self-characterize the current system conditions.
At block 2780, the system may calculate the amount of offset needed as function of glitch magnitude, glitch sign, and DAC code and updates the offset list. The process returns to block 2740 to apply the calculated offset and returns to monitoring the system stability.
The glitch mitigation methods described herein up to this point can operate in the background without disrupting the normal operation of the system for an extended period. The glitch mitigation methods can detect when the control loop settles near a high-glitch DAC code transition and can capture information on the sign and relative magnitude of a glitch based on the DAC code updates made by the control circuit at steady state. The control circuit then may apply an offset with fixed amplitude or varying amplitude calculated by the amplifier system as a function of the characterized glitch parameters.
If a writable memory is available in the amplifier system, the control circuit or a dedicated monitoring circuit may record the high-energy glitch codes with relative magnitudes together with sign information. Other key artifacts may be recorded to enable efficient glitch mitigation. The amount of offset applied for a given code transition can be made proportional or inversely proportional to the relative magnitude and the sign of the glitch, and the offset may be continuously updated as the system encounters new code transitions with high glitches.
Alternatively, a system-level foreground calibration may be devised which may be run at power-up, when the system is idle and not operational, or periodically during system operation (e.g., where the operating conditions such as temperature, power dissipation, or load, have changed significantly). The result of the calibration is an offset list that can be stored in memory and loaded when configuring the amplifier system.
At 2810, the corresponding target measure ADC code is set for a VTARGET value). At 2820, the system records DAC glitch magnitude and sign information in memory at each code transition based on the magnitude and direction of DAC code updates required at steady state. Only the glitches with magnitude (or energy) that are more than a set threshold (NTHRESHOLD) may be recorded to save memory space.
Once the high-energy DAC code transitions with sign and magnitude information are captured and recorded, at block 2830 the system may calculate the amount of offset that should be applied for each case during normal operation. The amount of offset can be calculated as a function of glitch codes, glitch magnitude and sign of the glitch. This way, all the relevant glitch characteristics could be determined for a system with multiple DACs without any glitch characterization data available beforehand. The system may also take advantage of previously characterization data during normal operation and/or to complete a faster system characterization.
At block 2840, the calculated offsets are stored in memory. This offset list is then available for loading into the control circuit or separate monitoring circuit of the system to shift the DAC code away from high-glitch transitions. An advantage of the system foreground calibration is that the system can methodically avoid high-glitch code transition during normal operation by applying predetermined offsets that are based on glitch information (e.g., glitch characteristic data) stored in memory.
The glitch mitigation process can involve machine learning as part of a process to identify DAC code changes when a high glitch transition condition is detected. Glitches from the DAC Code transitions is a negative attribute of the system and minimizing is desirable. The glitching optimization can be a minimization exercise. In machine learning, minimizing the glitches can be determined by optimizing a Loss Function or Cost Function. The Loss Function can be a combination of glitching attributes, and the goal of the machine learning is minimizing the attributes.
Population-based analysis can be used to determine which DAC code sets are desired and which are to be avoided in DAC code changes. Glitch performance of an amplifier system can have a multi-modal distribution with low-glitch codes grouped differently than high-glitch codes. The distribution may be DAC architecture dependent or system design dependent. For instance, multi-stage DACs may tend to have multi-modal patterns, while ladder DACs do not tend to have discrete sub-stages and thus may have different code distributions and may not exhibit a clearly multi-modal distribution. The optimization algorithm can analyze the glitching performance to determine glitch transitions that should be avoided. The energy or magnitude of the DAC glitches can be characterized or quantified. Code contingency can be performed on the worst glitches characterized by the system to maintain stable output. The characterized glitch data can be stored. A contingent DAC codeset can be chosen according to the previously recorded DAC glitch data. The code transitions may be limited to the codes available to the system. Glitch data analysis can be used to determine the DAC codeset for which the glitching is to be mitigated, thus avoiding potentially mitigating against code changes where the impact is not significant.
At block 2915, a control circuit of the amplifier system identifies that the first set of DAC codes includes a DAC code transition (or multiple DAC code transitions) associated with a high glitch condition and the high glitch DAC code transition is used, or will be used, to set the system output to the target output. At block 2920, the control circuit changes to operating the DAC circuits using a second set of DAC codes. The second set of DAC codes sets the output to the same target output, or substantially the same target output, as the first set of DAC codes. However, the second set of DAC codes does not include the DAC code transition associated with the high glitch condition. Thus, the glitch energy at the output is reduced.
The final codeset choice may be hardware constrained. The optimization algorithm may use knowledge of the DAC architecture in the analysis (e.g., certain code or bit transitions have a repeatable pattern throughout the codeset). Contingent DAC codesets can be determined based on knowledge of the design of the system. Contingent codesets may also be included to address unknown artifacts that may occur in the system (e.g., due to parasitics).
The glitch mitigation techniques described herein make use of the closed-loop setting, allowing the DACs to settle at different DAC codes while maintaining a target output voltage or current. The techniques provide glitch self-characterization as well as background and foreground calibration for closed-loop DAC glitch mitigation.
Example 1 includes subject matter (such as a method of feedback control of an amplifier system) comprising driving multiple amplifier circuits using at least one digital-to-analog converter (DAC) circuit to set a system output of the amplifier system; operating the at least one DAC circuit using a first set of DAC codes to set the system output to a steady state target output; detecting a high glitch condition at an output of the at least one DAC circuit when using the first set of DAC codes; and changing to operating the at least one DAC circuit using a second set of DAC codes to set the system output to substantially the same steady state target output, wherein operating the at least one DAC circuit using the second set of DAC codes reduces glitch energy at the output of the least one DAC circuit.
In Example 2, the subject matter of Example 1 optionally includes detecting a high-energy glitch transition that is greater than a threshold glitch transition when operating the at least one DAC circuit using the first set of DAC codes.
In Example 3, the subject matter of one or both of Examples 1 and 2 optionally includes identifying that the first set of DAC codes includes a DAC code transition associated with the high glitch condition when setting the system output to the steady state target output.
In Example 4, the subject matter of one or any combination of Examples 1-3 optionally includes setting the system output to the steady state target output using a control loop that includes a feedback circuit path; and adding an offset to the control loop to operate the at least one DAC circuit using the second set of DAC codes.
In Example 5, the subject matter of Example 4 optionally includes adding a programmable offset to the control loop using another DAC circuit.
In Example 6, the subject matter of one or any combination of Examples 1-5 optionally includes applying an output of the at least one DAC circuit to an input of a first amplifier circuit and an input of a second amplifier circuit of the multiple amplifier circuits when operating the amplifier system in a first mode; and applying the output of the at least one DAC circuit to the input of the first amplifier circuit and applying an output of another DAC circuit to the input of the second amplifier circuit in a second mode, wherein the second mode has a lower voltage output than the first mode.
In Example 7, the subject matter of one or nay combination of Examples 1-6 optionally includes driving multiple DAC channels, wherein each DAC channel includes a main DAC and an amplifier circuit, and the amplifier circuits of the DAC channels have different signal gain; operating the main DAC circuits of the DAC channels using the first set of DAC codes and summing outputs of the DAC channels to set the system output; and using a control loop to set the system output to the steady state target output and to change to operating the main DAC circuits using the second set of DAC codes to reduce ripple of the system output caused by the multiple DAC channels.
In Example 8, the subject matter of Example 7 optionally includes detecting a high-energy glitch transition that is greater than a threshold glitch transition when operating the at least one DAC circuit using the first set of DAC codes; determining an offset using a magnitude of the high-energy glitch transition and current DAC code; and selecting a set of DAC codes as the second set of DAC codes using the determined offset.
In Example 9, the subject matter of one or any combination of Examples 1-8 optionally includes updating a DAC code of the at least one DAC circuit using DAC code values selected from the first set of DAC codes to set the system output to the steady state target output; detecting when the DAC code of the at least one DAC circuit settles near a high-glitch DAC code transition when setting the system output to the steady state target output; and updating the DAC code of the at least one DAC circuit using DAC code values selected from the second set of DAC codes in response to the detecting.
Example 10 includes subject matter (such as an amplifier system) or can optionally be combined with one or any combination of Examples 1-9 to include such subject matter, comprising at least one digital to analog converter (DAC) circuit, wherein setting a DAC code in the at least one DAC circuit sets an output of the at least one DAC circuit; multiple amplifier circuits including inputs connected to the output of the at least one DAC circuit; a feedback circuit path connected to a system output of the amplifier system; and a control circuit connected to the at least one DAC circuit and the feedback circuit path. The control circuit is configured to operate the at least one DAC circuit using a first set of DAC codes to set the system output to a steady state output target; and change to operating the at least one DAC circuit using a second set of DAC codes to maintain the same steady state output target and to reduce ripple at the system output caused by the at least one DAC circuit.
In Example 11, the subject matter of Example 10 optionally includes a control loop that includes the feedback circuit and the control circuit; and a control circuit configured to detect a high glitch transition of the first set of DAC codes that is greater than a threshold glitch transition; and add an offset to the control loop to change to the selecting the DAC code from the second set of DAC codes.
In Example 12, the subject matter of Example 11 optionally includes another DAC circuit to add the offset to the control loop; and a control circuit configured to set the offset according to a magnitude of the high glitch transition and one or more DAC codes values corresponding to the high glitch transition.
In Example 13, the subject matter of one or both of Examples 11 and 12 optionally includes a summing node connected to outputs of the multiple amplifier circuits; multiple DAC circuits; and inputs of the multiple amplifier circuits are connected to the outputs of the multiple DAC circuits to form multiple DAC channels and the outputs of the multiple amplifier circuits are connected to the summing node. The control circuit is optionally configured to update DAC codes of the multiple DAC circuits to maintain the steady state output target; and add the offset to the summing node to change to selecting the DAC codes from the second set of DAC codes.
In Example 14, the subject matter of one or any combination of Examples 11-13 optionally includes a first amplifier circuit and a second amplifier circuit, and the at least one DAC circuit includes a first DAC circuit connected to an input of the first amplifier circuit and a second DAC circuit connected to an input of the second amplifier circuit. The control circuit is optionally configured to update the DAC codes of both the first DAC circuit and the second DAC circuit to apply an equal DAC output to the first amplifier circuit and the second amplifier circuit to set the system output to the steady state output target in a first mode; and update the DAC code of only the first DAC circuit to set the system output to the steady state output target in a second mode, wherein the second mode has a lower output voltage range than the first mode.
In Example 15, the subject matter of one or any combination of Examples 10-14 optionally includes a switch circuit and multiple amplifier circuits that include a first amplifier circuit and a second amplifier circuit, and the at least one DAC circuit includes a first DAC circuit and a second DAC circuit. The output of the first DAC circuit is connected to an input of the first amplifier circuit. The switch circuit is configured to connect the output of the first DAC circuit to an input of the second amplifier circuit in a first mode; and connect the output of the second DAC circuit to the input of the second amplifier circuit in a second mode, wherein the second mode has a lower voltage output range than the first mode.
In Example 16, the subject matter of one or any combination of Examples 10-15 optionally includes a system memory and a control circuit configured to sweep a DAC code of the at least one DAC code over a specified range of DAC code values; store DAC glitch characteristic data for DAC code transitions in the system memory; and detect the high glitch transition using the stored DAC glitch magnitudes for the DAC code transitions.
In Example 17, the subject matter of one or any combination of Examples 10-16 optionally includes a feedback circuit path that includes an analog-to-digital converter (ADC) circuit operatively coupled to the system output; and a control circuit configured to set the DAC code of the at least one DAC circuit to set a system output current to a steady state target output current.
In Example 18, the subject matter of one or any combination of Examples 10-17 optionally includes a sense impedance at the system output; a feedback circuit path that includes an analog-to-digital converter (ADC) circuit operatively coupled to the sense impedance; and a control circuit configured to set the DAC code of the at least one DAC circuit to set a system output current to a steady state target output current.
Example 19 includes subject matter (such as a power supply system having closed loop control) or can optionally be combined with one or any combination of Examples 1-18 to include such subject matter, comprising multiple digital to analog converter (DAC) channels, each DAC channel including a DAC circuit connected to an input of an amplifier circuit; a summing node connected to outputs of the amplifier circuits of the DAC channels to provide a system output; and control circuit operatively coupled to the DAC channels and the system output. The control circuit is configured to update the DAC circuits of the DAC channels with DAC codes to adjust the system output to a steady state target output in a steady state, wherein the DAC codes are selected from a first set of DAC codes; detect when the DAC codes selected from the first set of DAC codes result in a glitch condition at outputs of the DAC circuits in the steady state; and change to selecting the DAC codes from a second set of DAC codes that maintain the same steady state target output and reduce glitching at the outputs of the DAC circuits.
In Example 20 the subject matter of Example 19 optionally includes a control circuit configured to determine a control loop offset according to a glitch magnitude of the high-glitch DAC code transitions; and add the control loop offset to the summing node to change to the selecting the DAC codes from the second set of DAC codes.
These non-limiting examples can be combined in any permutation or combination. The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the invention can be practiced. These embodiments are also referred to herein as “examples.” All publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. Method examples described herein can be machine or computer-implemented at least in part.
This application claims priority to U.S. Provisional Application Ser. No. 63/376,467, filed Sep. 21, 2022, which is incorporated by reference herein in its entirety.
Number | Date | Country | |
---|---|---|---|
63376467 | Sep 2022 | US |