pdaSpecView

for example a modulation depth or maximum modulation speed of a modulator. These are just for quick information for users. Typical values are insertion loss, modulation speed and so on. Use the subspec field to categorize the item within a bigger group, for example having insertion loss for TE and TM specified seperately. See PDABBDEFINITION.py for many options.
Use subspec0..4 to mark up details of a specification, for example the related xsection or a polarization etc.

Structure

This element does not have elements. The attributes are shown below, in a sorted per type fashion.

<pdaSpecView  lsl="..."  name="..."  stddev="..."  subspec0="..."  subspec1="..."  subspec2="..."  subspec3="..."  subspec4="..."  unit="..."  usl="..." ... > ... </pdaSpecView>

XSD

The schema file can be downloaded or viewed at xPDK_Base.

Details

Type pdaExpression


Expression need to be commonly evaluated by many software, so having a restricted set of math / types and so on is key. In PDAFlow lib2/expr there is a yacc/lex parser available with some unit support as well as double / complex expressions. An alternative is tinyexpr, but this is more restrictive, so may be very unhandy for things like waveguide model expressions.

lsl

Lower Specification Limit: see Statistical Process Control for details. Basically the lower expected limit of the spec before alerts go off. Type pdaExpression documentation:
Expression need to be commonly evaluated by many software, so having a restricted set of math / types and so on is key. In PDAFlow lib2/expr there is a yacc/lex parser available with some unit support as well as double / complex expressions. An alternative is tinyexpr, but this is more restrictive, so may be very unhandy for things like waveguide model expressions.

name

stddev

Standard deviation; in case statistical information is available, it is often handy to also mark that down. Type pdaExpression documentation:
Expression need to be commonly evaluated by many software, so having a restricted set of math / types and so on is key. In PDAFlow lib2/expr there is a yacc/lex parser available with some unit support as well as double / complex expressions. An alternative is tinyexpr, but this is more restrictive, so may be very unhandy for things like waveguide model expressions.

subspec0

A see base docu.

subspec1

A see base docu.

subspec2

A see base docu.

subspec3

A see base docu.

subspec4

A see base docu.

unit

Type pdaUnit documentation:
The use of units is strongly recommended to ensure that values are consistent between provider and user of data. The XSD schema allows a series of "basic units" with a * and / them. A basic unit uses the standard prefixes qryzafpnumckMGTPEZYRQ followed by its type and an optional ^. So a unit can be something like 1/cm*3kV/m^3/degree*dB
A few additional names are added. You can use them with the common prefixes.

usl

Upper Specification Limit: see Statistical Process Control for details. Basically the upper expected limit of the spec before alerts go off. Type pdaExpression documentation: