The Display driver allows you to manage Display instances via simple and portable APIs.
inst.$name = 'CONFIG_Display_{num}'; | // Name |
inst.displayType = 'UART'; | // Display Type |
inst.lcdSize = 128; | // LCD Size |
inst.uartBufferSize = 1024; | // UART Buffer Size |
inst.enableANSI = false; | // Enable ANSI |
inst.maxPrintLength = 256; | // Maximum Print Length |
inst.mutexTimeout = 'Never Timeout'; | // Mutex Timeout |
inst.mutexTimeoutValue = 1; | // Mutex Timeout Value |
inst.baudRate = 115200; | // Baud Rate |
.$name = 'CONFIG_Display_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_Display_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.displayType = 'UART'
]
Valid options include the following:
'UART' |
| |
'LCD' |
| |
'Host' |
|
.lcdSize = 128
]
.uartBufferSize = 1024
]
.enableANSI = false
]
.maxPrintLength = 256
]
.mutexTimeout = 'Never Timeout'
]
Valid options include the following:
'Never Timeout' |
| |
'Never Wait' |
| |
'Custom' |
| - Custom number of RTOS ticks |
.mutexTimeoutValue = 1
]
.baudRate = 115200
]
Valid options include the following:
1200 |
| |
2400 |
| |
4800 |
| |
9600 |
| |
19200 |
| |
38400 |
| |
57600 |
| |
115200 |
| |
230400 |
| |
460800 |
| |
921600 |
|
The ADC driver allows you to manage an Analog to Digital peripheral via simple and portable APIs.
inst.$name = 'CONFIG_ADC_{num}'; | // Name |
inst.referenceVoltage = 'VDD'; | // (MSP432P4 only) Reference Voltage |
inst.externalReferenceVoltage = 3300000; | // (MSP432P4 only) External Reference Voltage |
inst.resolution = '14 Bits'; | // (MSP432P4 only) Resolution |
.$name = 'CONFIG_ADC_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_ADC_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.referenceVoltage = 'VDD'
]
Specifies the ADC's reference voltage source.
Valid options include the following:
'VDD' |
| |
'1.2V' |
| |
'1.45V' |
| |
'2.5V' |
| |
'External' |
| - Select this option if you are supplying an external reference voltage to the device. "The external reference voltage can be specified using the External Reference Voltage configuration option. |
'External Buffered' |
| - Select this option if you are supplying a buffered external reference voltage to the device. "The external reference voltage can be specified using the External Reference Voltage configuration option. |
.externalReferenceVoltage = 3300000
]
Specifies the external reference voltage in microvolts. This value can only be modified when the Reference Voltage is configured as External or External Buffered. Otherwise, this value is read only and indicates the internal voltage used in microvolts.
.resolution = '14 Bits'
]
Valid options include the following:
'8 Bits' |
| |
'10 Bits' |
| |
'12 Bits' |
| |
'14 Bits' |
|
The ADCBuf driver allows you to sample and convert analog signals at a specified frequency. The resulting samples are placed in a buffer provided by the application.
inst.$name = 'CONFIG_ADCBUF_{num}'; | // Name |
inst.channels = 1; | // (MSP432P4 only) Channels |
inst.clockSource = 'ADC'; | // (MSP432P4 only) Clock Source |
inst.enableDMA = true; | // (MSP432P4 only) Enable DMA |
inst.triggerSource = 'Timer'; | // (MSP432P4 only) Trigger Source |
inst.timerDutyCycle = 50; | // (MSP432P4 only) Timer Duty Cycle |
inst.timerCaptureCompare = 1; | // (MSP432P4 only) Timer Capture Compare |
inst.interruptPriority = '7'; | // (MSP432P4 only) Interrupt Priority |
.$name = 'CONFIG_ADCBUF_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_ADCBUF_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.channels = 1
]
.clockSource = 'ADC'
]
The frequency of the clock sources are configured per Power Performance Level configured in the Power Module.
Valid options include the following:
'ADC' |
| |
'SYSOSC' |
| |
'ACLK' |
| |
'MCLK' |
| |
'SMCLK' |
| |
'HSMCLK' |
|
.enableDMA = true
]
.triggerSource = 'Timer'
]
Valid options include the following:
'Timer' |
| |
'Auto' |
|
.timerDutyCycle = 50
]
.timerCaptureCompare = 1
]
Valid options include the following:
1 |
| |
2 |
|
.interruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The Capture driver allows you to detect and time edge triggered events on a GPIO pin.
inst.$name = 'CONFIG_CAPTURE_{num}'; | // Name |
inst.clockSource = 'SMCLK'; | // (MSP432P4 only) Clock Source |
inst.clockDivider = 2; | // (MSP432P4 only) Clock Divider |
inst.interruptPriority = '7'; | // (MSP432P4 only) Interrupt Priority |
.$name = 'CONFIG_CAPTURE_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_CAPTURE_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.clockSource = 'SMCLK'
]
The frequency of the clock sources are configured per Power Performance Level configured in the Power Module.
Valid options include the following:
'ACLK' |
| |
'SMCLK' |
| |
'External TXCLK' |
| |
'Inverted External TXCLK' |
|
.clockDivider = 2
]
The Clock Source will be divided by this value before being used by the timer peripheral
Valid options include the following:
1 |
| |
2 |
| |
3 |
| |
4 |
| |
5 |
| |
6 |
| |
7 |
| |
8 |
| |
10 |
| |
12 |
| |
14 |
| |
16 |
| |
20 |
| |
24 |
| |
28 |
| |
32 |
| |
40 |
| |
48 |
| |
56 |
| |
64 |
|
.interruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The DMA module provides support to other drivers that need to allocate exclusive access to a DMA resource to support CPU-less peripheral data transfers. There is no user API for this module. See Driver configurations reference for more information.
DMA.dmaErrorFunction = 'dmaErrorFxn'; | // DMA Error Function |
DMA.interruptPriority = '7'; | // Interrupt Priority |
.dmaErrorFunction = 'dmaErrorFxn']
.interruptPriority = '7']
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The GPIO driver allows you to manage General Purpose I/O resources via simple and portable APIs. GPIO pin behavior is configured statically, but can also be reconfigured at runtime.
GPIO.interruptPriority = '7'; | // Interrupt Priority |
GPIO.optimizeCallbackTableSize = false; | // Optimize Callback Table Size |
inst.$name = 'CONFIG_GPIO_{num}'; | // Name |
inst.mode = 'Input'; | // Mode |
inst.outputType = 'Standard'; | // Output Type |
inst.outputStrength = 'Medium'; | // Output Strength |
inst.initialOutputState = 'Low'; | // Initial Output State |
inst.pull = 'None'; | // Pull |
inst.interruptTrigger = 'None'; | // Interrupt Trigger |
inst.callbackFunction = 'NULL'; | // Callback Function |
inst.comment = ''; | // Comment |
.interruptPriority = '7']
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
.optimizeCallbackTableSize = false]
This option causes the GPIO driver tables to be sorted so that all GPIOs that trigger interrupts appear first in the GPIO table. This allows the table of GPIO callbacks, which is also indexed by the GPIO index, to be substantially shorter then the table of all GPIOs.
However, this also means that calls to GPIO_setCallback()
must never be made to GPIOs whose callbacks are configured as the empty string (which is shown as '<a callback is never needed>' in the GUI).
.$name = 'CONFIG_GPIO_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_GPIO_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.mode = 'Input'
]
The mode configuration parameter is used to determine the initial state of GPIO, eliminating the need to configure the GPIO pin at runtime prior to using it.
Valid options include the following:
'Input' |
| - This GPIO is always used for input |
'Output' |
| - This GPIO is always used for output |
'Dynamic' |
| - This GPIO is dynamically reconfigured at runtime using the GPIO APIs This mode indicates that the application will dynamically configure the GPIO at runtime using the GPIO APIs. As a result, it's assumed that this GPIO requires an entry in the table of GPIO callback functions; see Optimize Callback Table Size. |
.outputType = 'Standard'
]
Valid options include the following:
'Standard' |
| |
'Open Drain' |
|
.outputStrength = 'Medium'
]
Valid options include the following:
'High' |
| |
'Medium' |
| |
'Low' |
|
.initialOutputState = 'Low'
]
This specifies if an output will be driven high or low after GPIO_init().
Valid options include the following:
'High' |
| |
'Low' |
|
.pull = 'None'
]
Valid options include the following:
'None' |
| |
'Pull Up' |
| |
'Pull Down' |
|
.interruptTrigger = 'None'
]
This parameter configures when the GPIO pin interrupt will trigger. Even when this config is set, interrupts are not enabled until
GPIO_enableInt()
is called at runtime
Valid options include the following:
'None' |
| |
'High' |
| |
'Low' |
| |
'Falling Edge' |
| |
'Rising Edge' |
| |
'Both Edges' |
|
.callbackFunction = 'NULL'
]
If you need to set the callback at runtime, set this configuration parameter
to 'NULL' and call GPIO_setCallback()
with the name of the function you
want to be triggered.
If this config is not set, GPIO assumes that no callback will ever be set for
this GPIO and, as a result, no space will be allocated to save the address of
the callback; thus, it's important to never use GPIO_setCallback()
on a
GPIO for which this config is empty.
This function is of type GPIO_CallbackFxn
,
it's called in the context of a hardware ISR, and it's passed
a single parameter: the index of the GPIO that triggered the interrupt.
Example: Creating an input callback.
.comment = ''
]
The I2C driver provides a portable application interface to access peripherals on an I2C bus.
inst.$name = 'CONFIG_I2C_{num}'; | // Name |
inst.maxBitRate = 0; | // Maximum Bit Rate |
inst.ignoreUnusedAddressConflicts = false; | // Ignore Unused Address Conflicts |
inst.addressChecks = 'Fail'; | // Address Checks |
inst.speedChecks = 'Fail'; | // Speed Checks |
inst.clockSource = 'SMCLK'; | // (MSP432P4 only) Clock Source |
inst.interruptPriority = '7'; | // (MSP432P4 only) Interrupt Priority |
.$name = 'CONFIG_I2C_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_I2C_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.maxBitRate = 0
]
This parameter determines the value of a 'maximum bitrate' symbol declared in the generated ti_drivers_config.h
file: {bus_name}_MAXBITRATE
, where {bus_name} is the name of this bus instance. This symbol is used to portably open the bus at a speed that's likely to work.
If this configuration parameter is set to zero, the maximum speed for this instance is the maximum speed supported by the slowest attached slave. If no slave devices are attached, the maximum bit rate is 100 Kbps.
For example, if an I2C instance named SENSORS
is defined in SysConfig, the following snippet always opens it at an appropriate speed.
#include "ti_drivers_config.h" // defines I2C id SENSORS
// initialize optional I2C bus parameters
I2C_Params params;
I2C_Params_init(¶ms);
params.bitRate = SENSORS_MAXBITRATE;
// Open I2C bus for usage
I2C_Handle i2cHandle = I2C_open(SENSORS, ¶ms);
By default, SysConfig triggers an error in the event that the declared maximum speed of an attached slave is less then this value. You can disable this error by setting the speedChecks configuration parameter to either 'Warn'
or 'Remark'
.
Note: The maximum bit rate for an I2C bus is a function of the electrical capacitance and resistance on the I2C signal lines and the speed supported by the slowest slave. Even if all devices on the bus are capable of supporting the specified bit rate, you may need to lower it if the electrical characteristics of your hardware imply large bus signal rise-times. This can be caused by long wires, which increase the capacitance of a circuit.
.ignoreUnusedAddressConflicts = false
]
.addressChecks = 'Fail'
]
By default, SysConfig triggers an error if two or more devices in this bus have the same address. You can override this error by setting this configuration parameter to either 'Warn'
or 'Remark'
.
Valid options include the following:
'Fail' |
| - Trigger an error if two or more devices in the bus have the same address |
'Warn' |
| - Warn if two or more devices on the bus have the same address |
'Remark' |
| - Emit a remark if two or more devices on the bus have the same address |
.speedChecks = 'Fail'
]
By default, SysConfig triggers an error if a slave device on the bus has a maximum speed below the maximum bit rate specified for the bus. You can override this error by setting this configuration parameter to either 'Warn'
or 'Remark'
.
Valid options include the following:
'Fail' |
| - Trigger an error if the bus speed exceeds a slave's maximum speed |
'Warn' |
| - Warn if the bus speed exceeds any slave's maximum speed |
'Remark' |
| - Emit a remark if the bus speed exceeds a slave's maximum speed |
.clockSource = 'SMCLK'
]
The frequency of the clock sources are configured per Power Performance Level configured in the Power Module.
Valid options include the following:
'ACLK' |
| |
'SMCLK' |
|
.interruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The I2C Slave driver allows you to send and recieve I2C transfers from an I2C master.
inst.$name = 'CONFIG_I2CSLAVE_{num}'; | // Name |
inst.slaveAddress = 32; | // (MSP432P4 only) Slave Address |
inst.interruptPriority = '7'; | // (MSP432P4 only) Interrupt Priority |
.$name = 'CONFIG_I2CSLAVE_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_I2CSLAVE_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.slaveAddress = 32
]
.interruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The NVS driver allows you to read, write, and erase non-volatile memory regions via simple and portable APIs.
inst.$name = 'CONFIG_NVS_{num}'; | // Name |
inst.nvsType = 'Internal'; | // NVS Type |
.$name = 'CONFIG_NVS_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_NVS_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.nvsType = 'Internal'
]
Valid options include the following:
'Internal' |
| - Normal CPU directly addressable flash memory. |
'External' |
| - SPI Flash. Not directly addressable flash memory. |
'RAM' |
| - Region is in CPU directly addressable RAM. Typically used to emulate flash memory while developing applications that use real flash memory. This avoids wearing out device flash during software development. |
The Power driver facilitates the transition of the MCU from active states to one of the sleep states and vice versa. The Power driver enables the other driver modules to minimize power consumption. In addition, applications can set or release power constraints to prevent the MCU from transitioning into a particular sleep state.
Power.enablePolicy = true; | // (MSP432P4 only) Enable Policy |
Power.policyFunction = 'PowerMSP432_sleepPolicy'; | // (MSP432P4 only) Policy Function |
Power.policyCustomFunction = 'customPolicyFxn'; | // (MSP432P4 only) Policy Custom Function |
Power.policyInitFunction = 'PowerMSP432_initPolicy'; | // (MSP432P4 only) Policy Init Function |
Power.policyInitCustomFunction = 'customPolicyInitFxn'; | // (MSP432P4 only) Policy Init Custom Function |
Power.enablePinParking = false; | // (MSP432P4 only) Enable Pin Parking |
Power.resumeShutdownHookFunction = ''; | // (MSP432P4 only) Resume Shutdown Hook Function |
Power.initialPerformanceLevel = 2; | // (MSP432P4 only) Initial Performance Level |
Power.enablePerformanceLevels = true; | // (MSP432P4 only) Enable Performance Levels |
Power.customPerformanceLevels = 0; | // (MSP432P4 only) Custom Performance Levels |
Power.advancedConfiguration = false; | // (MSP432P4 only) Advanced Configuration |
Power.clockSystemCallback = ''; | // (MSP432P4 only) Clock System Callback |
Power.clockSystemInterruptPriority = '7'; | // (MSP432P4 only) Clock System Interrupt Priority |
Power.enableHFXTClock = false; | // (MSP432P4 only) Enable HFXT Clock |
Power.bypassHFXT = false; | // (MSP432P4 only) Bypass HFXT |
Power.hfxtFrequency = 48000000; | // (MSP432P4 only) HFXT Frequency |
Power.enableLFXTClock = false; | // (MSP432P4 only) Enable LFXT Clock |
Power.bypassLFXT = false; | // (MSP432P4 only) Bypass LFXT |
Power.lfxtDriveLevel = 0; | // (MSP432P4 only) LFXT Drive Level |
.enablePolicy = true]
If enabled, the policy function will be invoked once for each pass of the idle loop.
In addition to this static setting, the Power Policy can be dynamically enabled and disabled at runtime, via the Power_enablePolicy() and Power_disablePolicy() functions, respectively.
.policyFunction = 'PowerMSP432_sleepPolicy']
When enabled, this function is invoked in the idle loop, to opportunistically select and activate sleep states.
Two reference policies are provided:
In addition to this static selection, the Power Policy can be dynamically changed at runtime, via the Power_setPolicy() API.
Valid options include the following:
'PowerMSP432_sleepPolicy' |
| - A simple policy that will put the device in either the PowerMSP432_SLEEP state (unless there is a constraint prohibiting this), or CPU wait for interrupt (WFI). |
'PowerMSP432_deepSleepPolicy' |
| - An agressive policy that checks constraints and optionally chooses PowerMSP432_DEEPSLEEP_1, PowerMSP432_DEEPSLEEP_0, PowerMSP432_SLEEP, or WFI, in that order of preference. |
'Custom' |
| - Custom policies can be written, and specified via the Policy Custom Function configuration. |
.policyCustomFunction = 'customPolicyFxn']
.policyInitFunction = 'PowerMSP432_initPolicy']
This is an optional policy initialization function that will be called during application startup, during Power Manager initialization.
Valid options include the following:
'PowerMSP432_initPolicy' |
| |
'Custom' |
| - Custom initialization policies can be writtenand specified via the Policy Init Custom Function configuration. |
.policyInitCustomFunction = 'customPolicyInitFxn']
.enablePinParking = false]
Specifies if internal pull resistors should be automatically applied to input pins during PowerMSP432_DEEPSLEEP_0 and PowerMSP432_DEEPSLEEP_1.
.resumeShutdownHookFunction = '']
This function is called when the device wakes and resumes from a previous entry into either the SHUTDOWN_0 or SHUTDOWN_1 states. If this function is defined (i.e., not an empty string), it will be called during Power_init(), right before the Power driver clears the LOCKLPM5 and LOCKBKUP bits in the PMCTL1 register, to unlock I/Os and the backup domain.
.initialPerformanceLevel = 2]
Levels 0-3 are always available. Levels 4-7 are available if Custom Performance Levels are defined.
Valid options include the following:
0 |
| |
1 |
| |
2 |
| |
3 |
| |
4 |
| |
5 |
| |
6 |
| |
7 |
|
.enablePerformanceLevels = true]
If enabled, the performance scaling feature will be enabled for the application. The Initial Performance Level will be established during Power Manager initialization.
See the Performance Level Configuration for more information.
.customPerformanceLevels = 0]
See the Performance Level Configuration for more information.
Valid options include the following:
0 |
| |
1 |
| |
2 |
| |
3 |
| |
4 |
|
.advancedConfiguration = false]
.clockSystemCallback = '']
The function specified will be configured for catching Clock System (CS) interrupts. If left empty, interrupts from the CS will not be enabled.
.clockSystemInterruptPriority = '7']
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
.enableHFXTClock = false]
If enabled, the high frequency crystal (HFXT) clock pin will be configured for HFXT function.
.bypassHFXT = false]
If enabled, the high frequency crystal (HFXT) pin will be configured for HFXT bypass.
.hfxtFrequency = 48000000]
The source is specified via an enumerated value from cs.h, for example CS_48MHZ, CS_24MHZ, etc..
Valid options include the following:
1000000 | 1 MHz | |
1500000 | 1.5 MHz | |
3000000 | 3 MHz | |
4000000 | 4 MHz | |
6000000 | 6 MHz | |
8000000 | 8 MHz | |
12000000 | 12 MHz | |
16000000 | 16 MHz | |
24000000 | 24 MHz | |
32000000 | 32 MHz | |
40000000 | 40 MHz | |
48000000 | 48 MHz |
.enableLFXTClock = false]
If enabled, the low frequency crystal (LFXT) clock pin will be configured for LFXT function.
.bypassLFXT = false]
If enabled, the low frequency crystal (LFXT) pin will be configured for LFXT bypass.
.lfxtDriveLevel = 0]
The source is specified via an enumerated value from cs.h, for example: CS_LFXT_DRIVE3, CS_LFXT_DRIVE2, etc.
Valid options include the following:
0 |
| - CS_LFXT_DRIVE0 |
1 |
| - CS_LFXT_DRIVE1 |
2 |
| - CS_LFXT_DRIVE2 |
3 |
| - CS_LFXT_DRIVE3 |
The PWM driver allows you to generate Pulse Width Modulated signals via simple and portable APIs.
inst.$name = 'CONFIG_PWM_{num}'; | // Name |
inst.clockSource = 'SMCLK'; | // Clock Source |
.$name = 'CONFIG_PWM_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_PWM_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.clockSource = 'SMCLK'
]
The frequency of the clock sources are configured per Power Performance Level configured in the Power Module.
Valid options include the following:
'ACLK' |
| |
'SMCLK' |
|
The RTOS module reserves device resources that are required by low-level RTOS layers that must directly access device resources. It also provides a means for other system software to determine the low-level RTOS used by TI-Drivers to provide timeout and mutex services.
The SD driver provides a simple interface to perform basic operations on SD cards.
.$name = 'CONFIG_SD_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_SD_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.useFatFS = false
]
When enabled, the SDFatFS driver interface will be accessible by the application.
The SPI driver provides a portable application interface to control onboard Serial Peripheral Interfaces (SPI).
inst.$name = 'CONFIG_SPI_{num}'; | // Name |
inst.mode = 'Three Pin'; | // Mode |
inst.defaultTxBufferValue = '~0'; | // Default TX Buffer Value |
inst.minDmaTransferSize = 10; | // Min DMA Transfer Size |
inst.duplex = 'Full'; | // Duplex |
inst.dmaInterruptPriority = '7'; | // DMA Interrupt Priority |
.$name = 'CONFIG_SPI_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_SPI_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.mode = 'Three Pin'
]
In Three Pin mode, the user is responsible for controlling the slave select line.
Valid options include the following:
'Three Pin' |
| |
'Four Pin SS Active Low' |
| |
'Four Pin SS Active High' |
|
.defaultTxBufferValue = '~0'
]
Value sent when a TX buffer is not specified. This value must be provided in hexadecimal format; 0 and ~0 also acceptable inputs.
.minDmaTransferSize = 10
]
.duplex = 'Full'
]
In a typical SPI transfer, both participants transmit and receive at the same time (full duplex) but in some situations only one side will ever transmit and the other side may only need to receive. In these cases some pins can stay unassigned. If full duplex is not required, the user may select the role of this SPI.
Valid options include the following:
'Full' |
| |
'Master TX Only' |
| |
'Master RX Only' |
| |
'Slave TX Only' |
| |
'Slave RX Only' |
|
.dmaInterruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The Timer driver allows you to manage a Timer peripheral via simple and portable APIs.
inst.$name = 'CONFIG_TIMER_{num}'; | // Name |
inst.interruptPriority = '7'; | // Interrupt Priority |
inst.timerType = '16 Bits'; | // (MSP432P4 only) Timer Type |
inst.clockSource = 'ACLK'; | // (MSP432P4 only) Clock Source |
.$name = 'CONFIG_TIMER_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_TIMER_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.interruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
.timerType = '16 Bits'
]
Valid options include the following:
'32 Bits' | Timer32 | |
'16 Bits' | Timer_A |
.clockSource = 'ACLK'
]
The frequency of the clock sources are configured per Power Performance Level configured in the Power Module.
Valid options include the following:
'ACLK' |
| |
'SMCLK' |
| |
'EXTERNAL TXCLK' |
| |
'INVERTED EXTERNAL TXCLK' |
|
The UART driver provides device independent APIs for reading and writing to the UART peripherals.
inst.$name = 'CONFIG_UART_{num}'; | // Name |
inst.dataDirection = 'Send and Receive'; | // Data Direction |
inst.errorCallbackFunction = ''; | // Error callback function |
inst.baudRates = 115200; | // Baud Rates |
inst.clockSource = 'Any'; | // (MSP432P4 only) Clock Source |
inst.ringBufferSize = 32; | // (MSP432P4 only) Ring Buffer Size |
inst.bitOrder = 'LSB_FIRST'; | // (MSP432P4 only) Bit Order |
inst.interruptPriority = '7'; | // (MSP432P4 only) Interrupt Priority |
.$name = 'CONFIG_UART_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_UART_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.dataDirection = 'Send and Receive'
]
Valid options include the following:
'Send and Receive' |
| |
'Send Only' |
| |
'Receive Only' |
|
.errorCallbackFunction = ''
]
.baudRates = 115200
]
Valid options include the following:
1200 |
| |
2400 |
| |
4800 |
| |
9600 |
| |
19200 |
| |
38400 |
| |
57600 |
| |
115200 |
| |
230400 |
| |
460800 |
| |
921600 |
|
.clockSource = 'Any'
]
If 'Any' is selected, an appropriate clock source will be auto selected. For maximum portability to other devices, it is recommended that this option be left in it's default state of 'Any'.
The frequency of the clock sources are configured per Power Performance Level configured in the Power Module.
Valid options include the following:
'Any' |
| |
'ACLK' |
| |
'SMCLK' |
|
.ringBufferSize = 32
]
The ring buffer serves as an extension of the FIFO. If data is received when UART_read() is not called, data will be stored in the ring buffer. The size can be changed to suit the application.
.bitOrder = 'LSB_FIRST'
]
Valid options include the following:
'MSB_FIRST' |
| |
'LSB_FIRST' |
|
.interruptPriority = '7'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
The Watchdog driver allows you to configure the system watchdog. A watchdog timer is used to reset the system if it has become unresponsive. Parameters such as reset behavior and the callback function can be configured at runtime.
inst.$name = 'CONFIG_WATCHDOG_{num}'; | // Name |
inst.period = 1000; | // Period |
inst.interruptPriority = '1'; | // (MSP432P4 only) Interrupt Priority |
.$name = 'CONFIG_WATCHDOG_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_WATCHDOG_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.period = 1000
]
Valid options include the following:
65536000 |
| |
4096000 |
| |
256000 |
| |
16000 |
| |
1000 |
| |
250 |
| |
15.625 |
| |
1.953125 |
|
.interruptPriority = '1'
]
This configuration allows you to configure the hardware interrupt priority.
Valid options include the following:
'7' | 7 - Lowest Priority | |
'6' |
| |
'5' |
| |
'4' |
| |
'3' |
| |
'2' |
| |
'1' | 1 - Highest Priority |
inst.$name = 'CONFIG_BUTTON_{num}'; | // Name |
inst.autoHwConfig = true; | // Use Provided Button Configuration |
inst.hwConfig = 'Active Low No Pull'; | // Button Configuration |
.$name = 'CONFIG_BUTTON_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_BUTTON_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.autoHwConfig = true
]
When this setting is enabled, the board specific settings will be used to determine the button's hardware configuration. This will provide the correct configuration most of the time. If the button hardware has been modified, this setting should be disabled and the user should manually set the correct hardware configuration.
.hwConfig = 'Active Low No Pull'
]
Specify whether the button is connected to ground or Vcc when pushed, and whether there is an external pull up/down network attached. If a 'no pull' setting is selected, internal pull settings will be used. e.g. 'Active High Pull Down' should be set for a button that has a pull down resistor connected and is connected to Vcc when pushed. 'Active Low No Pull' should be set for a button that has no pull up/down and is connected to ground when pushed.
Valid options include the following:
'Active Low Pull Up' |
| |
'Active Low No Pull' |
| |
'Active High Pull Down' |
| |
'Active High No Pull' |
| |
'None' |
|
inst.$name = 'CONFIG_LED_{num}'; | // Name |
inst.dimmable = false; | // Dimmable |
.$name = 'CONFIG_LED_{num}'
]
This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. It can be set to any globally unique name that is also a valid C/C++ identifier.
The SysConfig tooling ensures that all names defined in a configuration are unique. When instances are first created, SysConfig gives them a default name, CONFIG_LED_
, that's made unique by appending a numeric id. If you provide a name, it's checked against all other instance names in the configuration and, if another instance has the same name, an error is triggered.
Note: since not all names are added to ti_drivers_config.h, it's possible that some names will not be allowed even though they do not actually collide in the generated files.
.dimmable = false
]
The user may configure an LED to be driven by a GPIO instance or a PWM instance, however, brightness control requires a PWM.
inst.$name = 'undefined{num}'; | // Name |
inst.referenceSource = 'VDD'; | // Reference Source |
inst.referenceVoltage = 3300000; | // Reference Voltage |
inst.inputSource = 'External Pin'; | // Input Source |
inst.mode = 'Non Differential'; | // Mode |
.$name = 'undefined{num}'
]
This name is concatenated to the end of the name Name specified in the ADCBuf module configuration above.
.referenceSource = 'VDD'
]
Valid options include the following:
'VDD' |
| |
'1.2V' |
| |
'1.45V' |
| |
'2.5V' |
| |
'External' |
| |
'External Buffered' |
|
.referenceVoltage = 3300000
]
.inputSource = 'External Pin'
]
Valid options include the following:
'External Pin' |
| |
'Internal Temperature' |
| |
'Internal Battery' |
|
.mode = 'Non Differential'
]
Valid options include the following:
'Non Differential' |
| |
'Differential' |
|
MSP432 performance levels used by the Power manager.
inst.dcoFrequency = 3000000; | // DCO Frequency |
inst.customDcoFrequency = 3500000; | // Custom DCO Frequency |
inst.mclk = 3000000; | // MCLK |
inst.mclkSource = 'DCO'; | // MCLK Source |
inst.mclkDivider = 1; | // MCLK Divider |
inst.hsmclk = 3000000; | // HSMCLK |
inst.hsmclkSource = 'DCO'; | // HSMCLK Source |
inst.hsmclkDivider = 1; | // HSMCLK Divider |
inst.smclk = 3000000; | // SMCLK |
inst.smclkDivider = 1; | // SMCLK Divider |
inst.aclk = 32768; | // ACLK |
inst.aclkSource = 'REFO'; | // ACLK Source |
inst.aclkDivider = 1; | // ACLK Divider |
inst.bclk = 32768; | // BCLK |
inst.bclkSource = 'REFO'; | // BCLK Source |
inst.activeState = 'LDO'; | // Active State |
inst.coreVoltageLevel = 'VCORE0'; | // Core Voltage Level |
inst.flashWaitStates = 0; | // Flash Wait-States |
inst.enableFlashBuffer = false; | // Enable Flash Buffer |
.dcoFrequency = 3000000
]
Specifies a list of nominal center frequencies to use for the DCO. If a Custom frequency is required, configure the desired frequency using the Custom DCO Frequency configurable.
Valid options include the following:
0 | Custom | - Specify a custom frequency for the DCO. You can specify the custom frequency using the Custom Center Frequency configurable. |
1500000 |
| - 1 MHz to 2 MHz |
3000000 |
| - 2 MHz to 4 MHz |
6000000 |
| - 4 MHz to 8 MHz |
12000000 |
| - 8 MHz to 16 MHz |
24000000 |
| - 16 MHz to 32 MHz |
48000000 |
| - 32 MHz to 64 MHz |
.customDcoFrequency = 3500000
]
.mclk = 3000000
]
Master Clock (MCLK) is used by the CPU and peripheral module interfaces. The clock source can be configured using the MCLK Source configurable.
.mclkSource = 'DCO'
]
Valid options include the following:
'DCO' |
| |
'HFXT' |
| |
'LFXT' |
| |
'VLO' |
| |
'REFO' |
| |
'MODOSC' |
|
.mclkDivider = 1
]
Valid options include the following:
1 |
| |
2 |
| |
4 |
| |
8 |
| |
16 |
| |
32 |
| |
64 |
| |
128 |
|
.hsmclk = 3000000
]
The Subsystem Master Clock (HSMCLK) is software selectable by individual peripheral modules.
.hsmclkSource = 'DCO'
]
Specifies the HSMCLK source. The Low-Speed Subsytem Master Clock (SMCLK) uses the same clock source as HSMCLK.
Valid options include the following:
'DCO' |
| |
'HFXT' |
| |
'LFXT' |
| |
'VLO' |
| |
'REFO' |
| |
'MODOSC' |
|
.hsmclkDivider = 1
]
Valid options include the following:
1 |
| |
2 |
| |
4 |
| |
8 |
| |
16 |
| |
32 |
| |
64 |
| |
128 |
|
.smclk = 3000000
]
SMCLK can be divided independently from HSMCLK. SMCLK is limited in frequency to half the rated maximum frequency of HSMCLK. SMCLK is software selectable by individual peripheral modules.
.smclkDivider = 1
]
SMCLK can be divided independently from HSMCLK. SMCLK is limited in frequency to half the rated maximum frequency of HSMCLK. SMCLK is software selectable by individual peripheral modules.
Valid options include the following:
1 |
| |
2 |
| |
4 |
| |
8 |
| |
16 |
| |
32 |
| |
64 |
| |
128 |
|
.aclk = 32768
]
ACLK is software selectable by individual peripheral modules. ACLK is restricted to maximum frequency of operation of 128 kHz.
.aclkSource = 'REFO'
]
ACLK is software selectable by individual peripheral modules. ACLK is restricted to maximum frequency of operation of 128 kHz.
Valid options include the following:
'LFXT' |
| |
'VLO' |
| |
'REFO' |
|
.aclkDivider = 1
]
ACLK is software selectable by individual peripheral modules. ACLK is restricted to maximum frequency of operation of 128 kHz.
Valid options include the following:
1 |
| |
2 |
| |
4 |
| |
8 |
| |
16 |
| |
32 |
| |
64 |
| |
128 |
|
.bclk = 32768
]
BCLK is used primarily in the backup domain and is restricted to a maximum frequency of 32.768 kHz
.bclkSource = 'REFO'
]
BCLK is used primarily in the backup domain and is restricted to a maximum frequency of 32.768 kHz
Valid options include the following:
'LFXT' |
| |
'REFO' |
|
.activeState = 'LDO'
]
Active states refer to any power state in which CPU execution is possible. Two core voltage level settings are supported: VCORE0 and VCORE1. See the Core Voltage Level configurable for more on core voltage levels. Three active modes are associated with each core voltage level. The various active modes allow for optimal power and performance across a broad range of application requirements. The core voltage can be supplied by either a low dropout (LDO) regulator or a DC/DC (DCDC) regulator.
Low Frequency (LF) active states are useful for low-frequency operation. The low-frequency active states limit the maximum frequency of operation to 128 kHz. The application must not perform flash program or erase operations or any change to SRAM bank enable or retention enable configurations while in low-frequency active states. This allows the power management system to be optimized to support the lower power demands in these operating states. Low-frequency active states are based on LDO operation only.
Valid options include the following:
'LDO' |
| - Low Dropout |
'DCDC' |
| - DC/DC Regulator |
'LF' |
| - Low Frequency |
.coreVoltageLevel = 'VCORE0'
]
The Power Supply System (PSS) uses an integrated voltage regulator to produce a secondary core voltage (VCORE) from the primary voltage that is applied to the device (VCC). In general, VCORE supplies the CPU, memories, and the digital modules, while VCC supplies the I/Os and analog modules. The VCORE output is maintained using a dedicated voltage reference. VCORE voltage level is programmable to allow power savings if the maximum device speed is not required. Modifying this configurable will impact the max frequencies available for the MCLK, HSMCLK, and SMCLK.
Valid options include the following:
'VCORE0' |
| |
'VCORE1' |
|
.flashWaitStates = 0
]
The flash controller is configurable in terms of the number of memory bus cycles it takes to service any read command. This allows the CPU execution frequency to be higher than the maximum read frequency supported by the flash memory. If the bus clock speed is higher than the native frequency of the flash, the access is stalled for the configured number of wait states, allowing data from the flash to be accessed reliably.
See the device data sheet for CPU execution frequency and wait-state requirements.
.enableFlashBuffer = false
]
When read buffering is enabled, the flash memory always reads an entire 128-bit line irrespective of the access size of 8, 16, or 32 bits. The 128-bit data and its associated address is internally buffered by the flash controller, so subsequent accesses (expected to be contiguous in nature) within the same 128-bit address boundary are serviced by the buffer. Hence, the flash accesses see wait-states only when the 128-bit boundary is crossed, while read accesses within the buffer's range are serviced without any bus stalls. If read buffering is disabled, accesses to the flash bypasses the buffer, and the data read from the flash is limited to the width of the access (8, 16, or 32 bits). Each bank has independent settings for the read buffering. In addition, within each bank, the application has independent flexibility to enable read buffering for instruction and data fetches. Read buffers are bypassed during any program or erase operation by the controller to ensure data coherency.
inst.regionBase = 0; | // Region Base |
inst.regionSize = 4096; | // Region Size |
inst.sectorSize = 4096; | // Sector Size |
.regionBase = 0
]
NOTE: This setting has no effect when using the GCC toolchain. The linker script must be manually modified if the region must be at a specific location. See the nvsinternal example README file for details.
.regionSize = 4096
]
.sectorSize = 4096
]
inst.regionBase = 0; | // Region Base |
inst.regionSize = 4096; | // Region Size |
inst.sectorSize = 4096; | // Sector Size |
inst.verifyBufferSize = 0; | // Verify Buffer Size |
inst.statusPollDelay = 100; | // Status Poll Delay |
.regionBase = 0
]
.regionSize = 4096
]
.sectorSize = 4096
]
.verifyBufferSize = 0
]
.statusPollDelay = 100
]
inst.regionType = 'Generated'; | // Region Type |
inst.regionBase = 0; | // Region Base |
inst.regionSize = 4096; | // Region Size |
inst.sectorSize = 4096; | // Sector Size |
.regionType = 'Generated'
]
Specifies the type of region used.
Valid options include the following:
'Generated' |
| - An internal flash region is automatically generated. |
'Pointer' |
| - Provide a pointer to the memory location of a predefined internal flash region. |
.regionBase = 0
]
NOTE: This setting has no effect when using the GCC toolchain. The linker script must be manually modified if the region must be at a specific location. See the nvsinternal example README file for details.
.regionSize = 4096
]
.sectorSize = 4096
]
SysConfig configuration scripts consist of a sequence of assignments to configuration parameters defined by the modules used in an application. There are two types of assignments: assignments to module-level configuration parameters (that apply to all instances of the module) and assignments to instance-level configuration parameters (which are specific to the instance alone). All configuration parameters have a default value that's used in the event that it's not explicitly set in the configuration script.
Synopsis lines of the form
MOD.paramName = defaultValue
|
Similarily,
inst.paramName = defaultValue
|
For example, the following is a snippet of a SysConfg script that configures the GPIO module and a GPIO instance.


Esc Close Quick Bar
Esc
Alt + (1 -> 6) Open Quick Bar Tab
Alt + (1 -> 6)
Alt + Q Enable Quick Bar Configure Mode
Alt + Q
Please enter your email and password to continue
Don't have an account? Create Account
Enter your email to recover your password


Clawpack (“Conservation Laws Package”) is a collection of finite volume methods for linear and nonlinear hyperbolic systems of conservation laws. Clawpack employs high-resolution Godunov-type methods with limiters in a general framework applicable to many kinds of waves.
The Clawpack 5.4.0 suite has been installed into the DesignSafe Jupyter Hub environment. It is available for use with Python2 both from the command-line and in Jupyter notebooks. If using python2 from the terminal, you'll want to use the binaries located in '/opt/conda/envs/python2/bin'.
An example GeoClaw notebook in Jupyter can be seen by navigating to 'community / Jupyter Notebooks / Workspace Application Sample Notebooks / GeoClaw' and opening 'GeoClaw_topotools_example.ipynb', and can be previewed and copied to your own space from here.
More documentation on Clawpack can be found at www.clawpack.org.


The BiobankCloud is a platform-as-a-service (PaaS) for the storage and analysis of digitized
genomic data. The platform provides secure storage and efficient analysis of large amounts of biomedical
data as well as the inter-connection of Biobanks.
Definitions
User – the data owner acting as the controller, the legally responsible party who uploads the data on the platform.
BiobankCloud platform – the processor who processes the data on behalf of the controller
Ethics board or auditor – party who is entrusted to monitor the processing conducted on
the platform on behalf of the platform or on the user.
Legal basis for processing:
The law applicable to the processing of data is the law that applies in the country where the
user is established, no matter where the data is processed.
The user undertakes to strictly follow a research protocol and only act
within the limits of any given consent, alternatively any other legal ground within the applicable law,
for example a permission from an ethical review board to allow re-use of previously consented data.
In order to secure the abovementioned, the user is to provide evidence of research approval for each study
processed within the platform, according to the forms set out in the platform.
SRPA: Standard Research Project Approval
SIAC: Standard Information About Consent
SINC: Standard Information on Non-Consented data
Secrecy clause:
All personal data acquired by the Platform from the user shall only be used for the purposes of
this agreement and shall not be further processed or disclosed without the consent of the user.
This does not preclude the platform from allowing access to auditing services under this agreement,
or any legally binding requests for disclosure of personal data.
Transparency:
All processing of the data within the BioBankCloud platform is conducted by the
platform itself. If any subcontractors will be involved in the future, the BiobankCloud Platform
undertakes to inform the user in writing. If the user does not want to continue using the BiobankCloud
Platform services under these conditions, the platform will take care to end its services under controlled forms,
as set out in point 13. Termination of the contract.
Changes in the Services:
If in the future changes will be made in the service that requires the installation of new software, libraries or
hardware devices on the users systems, the BiobankCloud will inform the user about this, and in particular about its
implications from a data protection and data security point of view.
The user agrees to provide the data subjects with information on where the data is being processed, in the event the
data subject would want his/her data erased or changed.
Purpose binding:
The platform will process the data in accordance with the instructions of the user. The user instructs the platform to:
a) provide the services, including detection, prevention and resolution of security and technical issues, and
b) respond to customers support requests.
The platform will only process the data of the user in accordance with this agreement and will not
process the data for any other purposes.
Data minimization:
The access to data within the platform is restricted in accordance to different roles
established within the platform. The user may allocate different degrees of access the data depending on
which role a person acting within the platform is being attributed.
Other than the user, roles are attributed to the platform as an administrator and to ethics board or auditor
who may monitor the processing conducted on the platform on behalf of the user or the platform.
Retention periods:
When uploading data to the platform, the user shall define a period of time under which the data is to be stored (retention period).
The retention period should not be longer than necessary to conduct the storing and analyzing needed.
If the user has not taken action to remove the data when the retention period has elapsed, the platform will contact
the user and request that this is done. The user may prolong the retention period, but only if this is in accordance with
applicable law. If the user does not either remove the data or prolong the retention period, the platform shall take action to
remove the data from the platform. The user will be given due notice before any data is removed.
Geographical limitations of processing the data:
All processing of data within the platform will take place within the geographical area of EEA, namely the 28 Member
States of the EU (Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany,
Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia,
Spain, Sweden, United Kingdom) and Iceland, Liechtenstein and Norway.
Data security:
The platform ensures that the technical security measures and organizational measures governing the processing of the data within
the platform is to be carried out in accordance to high safety standards.
The platform ensures to keep the data of the user separated from all other users, within a secured space with limited access.
The user is obligated to handle all security credentials with care and must not under any circumstances share them with others.
The user and the platform are mutually obligated to immediately report any deviations from the proper functioning of the platform.
Accountability:
The user is to provide full contact information, including name of responsible person and his/her affiliation. The user agrees
to keep the information updated.
All processing of data within the cloud is to be recorded. The user and the platform are obligated to cooperate fully in order to ensure
the fulfillment of this task.
An audit organ, either internal or external, may access the recordings of the processing. Both the user and the platform may require a report
from the audit organ to ensure that all processing of the data has been carried out in accordance with this agreement.
Portability:
The data model representing metadata about biobank, samples and studies is based on MIABIS 2.0, which ensures interoperability with data
collected within the BBMRI-ERIC.
Modification of the agreement:
The platform may not unilaterally change or amend any of the terms of this agreement. All proposed changes to the agreement must be presented
before the user in due time and cannot enter into force until accepted by the user.
The platform is to inform the user of all changes in form of amendments, improvements and updates of the technical functioning of the platform.
Any changes that may involve a change in the terms of this agreement must be accepted by the user before being implemented, as set out above.
Termination of the services or agreement:
The user may at any time remove his/her data from the platform.
The user may terminate the agreement unilaterally at any time. The platform is to ensure that all data has been removed from the platform,
including safety copies.
If the user does not abide by his/her obligations under this agreement, the platform may unilaterally terminate the agreement. The user will
be given notice of the platforms intention in due time. If the breach is not of a serious nature, the user may be given the opportunity to rectify the breach.
Information on processing of data collected for auditing purposes will be stored within the platform for a reasonable time after the agreement
has been terminated.


My name is George Madiarov and this ... is my masterpiece!! ( :D ) Html + css only. I'm looking forward to be a really good front-end engeneer. I really want!!


Privacy Policy
A Sharp Systems is committed to providing quality services to you and this policy outlines our ongoing obligations to you in respect of how we manage your Personal Information. We have adopted the Australian Privacy Principles (APPs) contained in the Privacy Act 1988 (Cth) (the Privacy Act). The NPPs govern the way in which we collect, use, disclose, store, secure and dispose of your Personal Information. A copy of the Australian Privacy Principles may be obtained from the website of The Office of the Australian Information Commissioner at www.aoic.gov.auWhat is Personal Information and why do we collect it?
Personal Information is information or an opinion that identifies an individual. Examples of Personal Information we collect include: names, addresses, email addresses, phone and facsimile numbers. This Personal Information is obtained in many ways including [interviews, correspondence, by telephone and facsimile , by email, via our website, from your website, from media and publications, from other publicly available sources, from cookies] and from third parties. We don’t guarantee website links or policy of authorised third parties. We collect your Personal Information for the primary purpose of providing our services to you, providing information to our clients and marketing. We may also use your Personal Information for secondary purposes closely related to the primary purpose, in circumstances where you would reasonably expect such use or disclosure. You may unsubscribe from our mailing/marketing lists at any time by contacting us in writing. When we collect Personal Information we will, where appropriate and where possible, explain to you why we are collecting the information and how we plan to use it.Sensitive Information
Sensitive information is defined in the Privacy Act to include information or opinion about such things as an individual's racial or ethnic origin, political opinions, membership of a political association, religious or philosophical beliefs, membership of a trade union or other professional body, criminal record or health information.Sensitive information will be used by us only:
- For the primary purpose for which it was obtained
- For a secondary purpose that is directly related to the primary purpose
- With your consent; or where required or authorised by law.
Third Parties
Where reasonable and practicable to do so, we will collect your Personal Information only from you. However, in some circumstances we may be provided with information by third parties. In such a case we will take reasonable steps to ensure that you are made aware of the information provided to us by the third party.Disclosure of Personal Information Your Personal Information may be disclosed in a number of circumstances including the following:
- Third parties where you consent to the use or disclosure; and
- Where required or authorised by law.


| Overview | Module | Use | Devguide | Index |
| Services' Summary | Interfaces' Summary | Properties' Summary | Services' Details | Interfaces' Details | Properties' Details |
| service Shape |
|
| Exported Interfaces - Summary | |
| ::com::sun::star::beans::XPropertySet | handles all the properties of this instance. |
| XShape | This gives you the size and position of this Shape and lets you change it. You can use getShapeType to determine what kind of shape this is. |
| ::com::sun::star::lang::XComponent | is used for lifetime control of this Shape. |
| XShapeDescriptor | The XShapeDescriptor tells you what kind of Shape this instance is. |
| XGluePointsSupplier | This interfaces gives access to an optional container of glue points. To have unique ids you should query the returned interface for ::com::sun::star::container::XIdentifierContainer. (details) |
| ::com::sun::star::beans::XTolerantMultiPropertySet |
| Properties' Summary | |
| long ZOrder |
[ OPTIONAL ] is used to query or change the ZOrder of this Shape. |
| short LayerID |
[ OPTIONAL ] This is the ID of the Layer to which this Shape is attached. |
| string LayerName |
[ OPTIONAL ] This is the name of the Layer to which this Shape is attached. |
| boolean Visible |
[ OPTIONAL ] If this is false, the Shape is not visible on screen outputs. Please note that the Shape may still be visible when printed, see Printable. |
| boolean Printable |
[ OPTIONAL ] If this is false, the Shape is not visible on printer outputs. |
| boolean MoveProtect |
[ OPTIONAL ] With this set to true, this Shape cannot be moved interactively in the user interface. |
| string Name |
[ OPTIONAL ] This is the name of this Shape. |
| boolean SizeProtect |
[ OPTIONAL ] With this set to true, this Shape may not be sized interactively in the user interface. |
| ::com::sun::star::style::XStyle Style |
[ OPTIONAL ] this property lets you get and set a style for this shape. |
| HomogenMatrix3 Transformation |
[ OPTIONAL ] this property lets you get and set the transformation matrix for this shape. The transformation is a 3x3 homogen matrix and can contain translation, rotation, shearing and scaling. |
| ::com::sun::star::container::XNameContainer ShapeUserDefinedAttributes |
[ OPTIONAL ] this property stores xml attributes. They will be saved to and restored from automatic styles inside xml files. |
| long NavigationOrder |
[ OPTIONAL ] this property stores the navigation order of this shape. If this value is negative, the navigation order for this shapes page is equal to the z-order. |
| Exported Interfaces - Details | |
::com::sun::star::beans::XPropertySet
|
|
XShape
|
|
::com::sun::star::lang::XComponent
|
|
XShapeDescriptor
|
|
XGluePointsSupplier
|
|
::com::sun::star::beans::XTolerantMultiPropertySet
|
| Properties' Details | |
ZOrder
|
|
LayerID
|
|
LayerName
|
|
Visible
|
|
Printable
|
|
MoveProtect
|
|
Name
|
|
SizeProtect
|
|
Style
|
|
Transformation
|
|
ShapeUserDefinedAttributes
|
|
NavigationOrder
|
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


No. of instances of A:
No. of instances of B:
No. of instances of C:

Allocation
A
B
C
P1
P2
P3
P4
P5
Max
A
B
C
P1
P2
P3
P4
P5
Need
A
B
C
P1
P2
P3
P4
P5
Available
A
B
C
Safe Process Sequence :


GISFaces™ is an Enterprise GIS mapping component for JavaServer Faces (JSF).
The underlying GIS mapping engine used is the ESRI® ArcGIS API For JavaScript.
Any ArcGIS layer or raw data, local or online, can be used in the maps you build.
All of these example maps are built with publicly available layers and data.
Best of all, no prior GIS programmer or analyst experience is necessary to start integrating GIS maps into your enterprise applications.
2D and 3D map views are available.
Map layer types supported include CSV, Feature, GeoJSON, GeoRSS, Graphics, Imagery, Integrated Mesh, KML, Map Image, Point Cloud, ArcGIS Portal, Scene, Stream, Tile, Vector Tile, and WMS.
All layers automatically display the feature attribute table on selection.
Java event handlers for map interaction include basemap selection, map click, map extent, feature selection, geo-location, graphic editing.
The map widgets displayed are search, zoom in/out, pan/orientation, compass, basemap, layer list, legend, geo-location tracking, full screen, 2d/3d toggle, and coordinate transformations.
Layers are built in Java code using an extensive object model.


Striped Table
Here is a subtitle for this table
| Investor | Sector | Subsector | Quantity in Millions USD |
|---|---|---|---|
| Zhuhai Port Holdings, State Construction Engin... | Transport | Shipping | 1620 |
| State Power Investment | Energy | Coal | 1480 |
| ZTE | Energy | Alternative | 1440 |
| Power Construction Corp | Energy | Coal | 1190 |
| China Mobile | Telecom | Telecom | 720 |
| China Energy Engineering | Energy | Hydro | 360 |
| Alibaba | Finance | Banking | 330 |
| Three Gorges | Energy | Alternative | 220 |
| Sinomach | Energy | Energy | 150 |
| Shandong Ruyi | Textile | Textiles | 120 |
Table on Plain Background
Here is a subtitle for this table
| ID | Name | Salary | Country | City |
|---|---|---|---|---|
| 1 | Dakota Rice | $36,738 | Niger | Oud-Turnhout |
| 2 | Minerva Hooper | $23,789 | Curaçao | Sinaai-Waas |
| 3 | Sage Rodriguez | $56,142 | Netherlands | Baileux |
| 4 | Philip Chaney | $38,735 | Korea, South | Overland Park |
| 5 | Doris Greene | $63,542 | Malawi | Feldkirchen in Kärnten |
| 6 | Mason Porter | $78,615 | Chile | Gloucester |


{% load staticfiles %}
Cannot contact job analysis server. Continue waiting or stop?
Current job is running. Submit a new one or continue?


package main
import "fmt"
func main() {
var x [][]int = [][]int{
{1, 2, 3, 4, 5},
{6, 7, 8, 9, 10},
{11, 12, 13, 14, 15},
{21, 22, 23, 24, 25},
{30, 31, 32, 33, 34},
}
fmt.Println("Slice 'x' elements are:\n", x)
}
Slice 'x' elements are:
[[1 2 3 4 5] [6 7 8 9 10] [11 12 13 14 15] [21 22 23 24 25] [30 31 32 33 34]]
In this program, we initialize the slice i.e. 'x'
And then print all the elements of the slice 'x' as an output.


Types of Anime Fans
The Ones Who Have A Life/The Casual
These sorts of anime fans have somewhat prioritized and put anime in the backseat, but still enjoy the occasional show if they have time. They are healthiest type of anime fan, and have found their life/anime balance.
The Collector
This sort of anime fan spends large amounts of money on anime merchandise they can't afford. Comes hand in hand with college debt. This type should not be left alone at any sort of convention, EVER.
The Hype Beast
Watches anime soley for the excitement and not for the plot, which is highly annoying for the Intellectuals. They solely enjoy trending shonen anime, and will not stop spewing hype once you get them started.
The Intellectual
The Intellectual feels that they have the greatest/most superior taste in anime, and finds the Hype Beast to have extremely trash taste. They really like to use the word "plot". Do not try to argue with them, unless you would like to be bashed for a couple of hours.


The visible range is limited in this demo:
- minimum visible date is limited to 2012-01-01 using option
min
- maximum visible date is limited to 2012-12-31 using option
max
- visible interval is limited to a minimum of 24 hours using option
intervalMin
- visible interval is limited to a maximum of about 3 months using option
intervalMax


Below is a list of commands you can run from your terminal to access the machines in your cluster. Node commands are provided for troubleshooting purposes; general cluster functions should be run from the master (for multi-master clusters, any master will suffice).


OpenDcd - An Open Source WFST based Speech Recognition Decoder
OpenDcd a lightweight and portable WFST based speech decoding toolkit written in C++. OpenDcd provides a set of tools for decoding, cascade construction and hypothesis post- processing. The focus of the toolkit is to provide a foundation for research into new decoding methods that can be deployed. Through the use of C++ templates the core decoder can be configured and extended in many ways. For example selecting different on-the-fly composition or lattice generation strategies. The core engine has detailed profiling, logging and analysis methods that make it highly for deployement in production systems. The toolkit makes used of OpenFst for representing and manipulating the models. It is distributed as an open source project with an Apache Licence.
For more information see the main documentation site, and the tutorial for installing the OpenDcd and decoding using the Librispeech corpus and models from kaldi-asr.og.
Quick Installation Guide
git clone https://github.com/opendcd/opendcd.git
cd src/bin
make
Kaldi Conversion Quick Start
For Kaldi model converion and decoding a working Kaldi installation and set of acoustic and language models and features from generated from a Kaldi egs/s5 script are required. The following example is based on the output of Kaldi WSJ training run.
Graph construction, the scripts directory contains The Kaldi language directory, we re-use the existing Kaldi lexicon and LM.
cd $OPENDCD/scripts
export KALDI_ROOT=/home/opendcd/tools/kaldi-trunk
./makeclevel.sh \
$KALDI_ROOT/egs/wsj/s5/data/lang_test_bg_5k \
$KALDI_ROOT/egs/wsj/s5/exp/tri2a \
$KALDI_ROOT/egs/wsj/s5/exp/ocd_tri2a \
$KALDI_ROOT
See egs directory contains example script for showing how to convert a Kaldi WSJ setup
Brief Overview
The first release includes the following features:
- Standalone lightweight decoder core
- Kaldi file format compatible or ptionally build against Kaldi
- Post-processing tools
- OpenFst and Kaldi Interop Tools
Decoder:
- Customizable transition model for custom user and transition models
- Direct decoding on different weight semiring
- On-the-fly decoding using lookahead composition
- Lattice generation
- Switchable STL implementations. Use different implementations such EASTL or RDESTL, or mix optimized containers such as Google sparse hash.
- Powerful registration mechanism for adding user defined acoustic models and or lattice generation strategies
Cascde construction:
- Script to efficiently build and convert models from a Kaldi lang directory
Results post-processing:
-
farfilter
Apply the command to every in FST in the FAR archive -
latticetofar
Convert Kaldi Table to OpenFst FAR archive -
fartolattice
Convert an OpenFst FAR archive to Kaldi Table
Kaldi Interoperability:
- Write results in Kaldi Lattice table format
- More information on optionally building against Kaldi
- Convert Kaldi tree to optimized decoding structure
More Information
- A getting start guide for running OpenDcd on Ec2 using the Librispeech models
- Ongoing introdutory slides can be found here. These are updated infrequently.


{% extends template.self %}
{% block description %}{{ page.description | default("GoCD is an open source continuous delivery server that helps organizations increase productivity and deliver high quality software through automation.") }}{% endblock %}
{% block head %}
{% endblock %}


{{- partial "head.html" . -}}
The link to buy packs is not available yet. Please join our telegram group for updates.


|
Panda3D
|
This is the preferred interface for loading shaders for the TextNode system. More...
Static Public Member Functions | |
| static | addShader (const Filename filename, Shader shader) |
| Adds the indicated already-loaded shader to the pool. More... | |
| static int | garbageCollect () |
| Releases only those shaders in the pool that have a reference count of exactly 1; i.e. More... | |
| static bool | hasShader (const Filename filename) |
| Returns true if the shader has ever been loaded, false otherwise. More... | |
| static | listContents (Ostream out) |
| Lists the contents of the shader pool to the indicated output stream. More... | |
| static const Shader | loadShader (const Filename filename) |
| Loads the given filename up into a shader, if it has not already been loaded, and returns the new shader. More... | |
| static | releaseAllShaders () |
| Releases all shaders in the pool and restores the pool to the empty state. More... | |
| static | releaseShader (const Filename filename) |
| Removes the indicated shader from the pool, indicating it will never be loaded again; the shader may then be freed. More... | |
| static bool | verifyShader (const Filename filename) |
| Loads the given filename up into a shader, if it has not already been loaded, and returns true to indicate success, or false to indicate failure. More... | |
| static | write (Ostream out) |
| Lists the contents of the shader pool to the indicated output stream. More... | |
This is the preferred interface for loading shaders for the TextNode system.
It is similar to ModelPool and TexturePool in that it unifies references to the same filename.
Adds the indicated already-loaded shader to the pool.
The shader will always replace any previously-loaded shader in the pool that had the same filename.
|
static |
Releases only those shaders in the pool that have a reference count of exactly 1; i.e.
only those shaders that are not being used outside of the pool. Returns the number of shaders released.
|
static |
Returns true if the shader has ever been loaded, false otherwise.
|
static |
Lists the contents of the shader pool to the indicated output stream.
Loads the given filename up into a shader, if it has not already been loaded, and returns the new shader.
If a shader with the same filename was previously loaded, returns that one instead. If the shader file cannot be found, returns NULL.
|
static |
Releases all shaders in the pool and restores the pool to the empty state.
|
static |
Removes the indicated shader from the pool, indicating it will never be loaded again; the shader may then be freed.
If this function is never called, a reference count will be maintained on every shader every loaded, and shaders will never be freed.
|
static |
Loads the given filename up into a shader, if it has not already been loaded, and returns true to indicate success, or false to indicate failure.
If this returns true, it is guaranteed that a subsequent call to load_shader() with the same shader name will return a valid Shader pointer.
|
static |
Lists the contents of the shader pool to the indicated output stream.


Class MathMatrixVector
- java.lang.Object
-
- com.zetkoofficial.mathlib.matrixvector.helper.MathMatrixVector
-
public final class MathMatrixVector extends java.lang.Object
This is the helper class for the matrixvector package.- Author:
- ZetkoOfficial
-
-
Constructor Summary
Constructors Constructor Description MathMatrixVector()
-
Method Summary
Modifier and Type Method Description static Matrix
mathAbsElements(Matrix m)
Does the absolute value operation on every element of the Matrix.static Vector
mathAbsElements(Vector v)
Does the absolute value operation on every element of the Vector.static Matrix
mathAdd(Matrix m1, Matrix m2)
Does addition between elements of both Matrices of the same index.static Vector
mathAdd(Vector v1, Vector v2)
Does addition between elements of both Vectors of the same index.static Matrix
mathCustomFunction(Matrix m, java.util.function.Function<java.lang.Double,java.lang.Double> function)
Does a custom operation on every element of the Matrix.static Vector
mathCustomFunction(Vector v, java.util.function.Function<java.lang.Double,java.lang.Double> function)
Does the custom operation on every element of the Vector.static Matrix
mathDivide(Matrix m1, Matrix m2)
Does division between elements of both Matrices of the same index.static Vector
mathDivide(Vector v1, Vector v2)
Does division between elements of both Vectors of the same index.static double
mathDot(Vector v1, Vector v2)
Calculates the dot product of Vectors.static double
mathLength(Vector v)
Calculates the length of the Vector.static Matrix
mathMultiply(Matrix m1, Matrix m2)
Calculates the product of Matrices.static Vector
mathMultiply(Vector v1, Vector v2)
Does multiplication between elements of both Vectors of the same index.static Matrix
mathMultiplyElements(Matrix m1, Matrix m2)
Does multiplication between elements of both Matrices of the same index.static Matrix
mathSigmoid(Matrix m)
Does the sigmoid operation on every element of the Matrix.static Vector
mathSigmoid(Vector v)
Does the sigmoid operation on every element of the Vector.static Matrix
mathSigmoidPrime(Matrix m)
Does the sigmoid prime operation on every element of the Matrix.static Vector
mathSigmoidPrime(Vector v)
Does the sigmoid prime operation on every element of the Vector.static Matrix
mathSubtract(Matrix m1, Matrix m2)
Does subtraction between elements of both Matrices of the same index.static Vector
mathSubtract(Vector v1, Vector v2)
Does subtraction between elements of both Vectors of the same index.
-
-
-
Method Detail
-
mathSigmoid
public static Matrix mathSigmoid(Matrix m)
Does the sigmoid operation on every element of the Matrix.- Parameters:
m
- The Matrix- Returns:
- The result Matrix
-
mathSigmoidPrime
public static Matrix mathSigmoidPrime(Matrix m)
Does the sigmoid prime operation on every element of the Matrix.- Parameters:
m
- The Matrix- Returns:
- The result Matrix
-
mathAbsElements
public static Matrix mathAbsElements(Matrix m)
Does the absolute value operation on every element of the Matrix.- Parameters:
m
- The Matrix- Returns:
- The result Matrix
-
mathCustomFunction
public static Matrix mathCustomFunction(Matrix m, java.util.function.Function<java.lang.Double,java.lang.Double> function)
Does a custom operation on every element of the Matrix.- Parameters:
m
- The Matrixfunction
- The IFunction which holds the custom operation- Returns:
- The result Matrix
-
mathAdd
public static Matrix mathAdd(Matrix m1, Matrix m2)
Does addition between elements of both Matrices of the same index.- Parameters:
m1
- The first Matrixm2
- The second Matrix- Returns:
- The result Matrix
-
mathSubtract
public static Matrix mathSubtract(Matrix m1, Matrix m2)
Does subtraction between elements of both Matrices of the same index.- Parameters:
m1
- The first Matrixm2
- The second Matrix- Returns:
- The result Matrix
-
mathMultiplyElements
public static Matrix mathMultiplyElements(Matrix m1, Matrix m2)
Does multiplication between elements of both Matrices of the same index.- Parameters:
m1
- The first Matrixm2
- The second Matrix- Returns:
- The result Matrix
-
mathDivide
public static Matrix mathDivide(Matrix m1, Matrix m2)
Does division between elements of both Matrices of the same index.- Parameters:
m1
- The first Matrixm2
- The second Matrix- Returns:
- The result Matrix
-
mathMultiply
public static Matrix mathMultiply(Matrix m1, Matrix m2)
Calculates the product of Matrices.- Parameters:
m1
- The first Matrixm2
- The second Matrix- Returns:
- The result Matrix
-
mathSigmoid
public static Vector mathSigmoid(Vector v)
Does the sigmoid operation on every element of the Vector.- Parameters:
v
- The Vector- Returns:
- The result Vector
-
mathSigmoidPrime
public static Vector mathSigmoidPrime(Vector v)
Does the sigmoid prime operation on every element of the Vector.- Parameters:
v
- The Vector- Returns:
- The result Vector
-
mathAbsElements
public static Vector mathAbsElements(Vector v)
Does the absolute value operation on every element of the Vector.- Parameters:
v
- The Vector- Returns:
- The result Vector
-
mathCustomFunction
public static Vector mathCustomFunction(Vector v, java.util.function.Function<java.lang.Double,java.lang.Double> function)
Does the custom operation on every element of the Vector.- Parameters:
v
- The Vectorfunction
- The IFunction which holds the custom operation.- Returns:
- The result Vector
-
mathLength
public static double mathLength(Vector v)
Calculates the length of the Vector.- Parameters:
v
- The Vector- Returns:
- The length of the Vector.
-
mathAdd
public static Vector mathAdd(Vector v1, Vector v2)
Does addition between elements of both Vectors of the same index.- Parameters:
v1
- The first Vectorv2
- The second Vector- Returns:
- The result Vector
-
mathSubtract
public static Vector mathSubtract(Vector v1, Vector v2)
Does subtraction between elements of both Vectors of the same index.- Parameters:
v1
- The first Vectorv2
- The second Vector- Returns:
- The result Vector
-
mathMultiply
public static Vector mathMultiply(Vector v1, Vector v2)
Does multiplication between elements of both Vectors of the same index.- Parameters:
v1
- The first Vectorv2
- The second Vector- Returns:
- The result Vector
-
mathDivide
public static Vector mathDivide(Vector v1, Vector v2)
Does division between elements of both Vectors of the same index.- Parameters:
v1
- The first Vectorv2
- The second Vector- Returns:
- The result Vector
-
-


A single content area with multiple panels, each associated with a header in a list.
Displays collapsible content panels for presenting information in a limited amount of space.
Select a date from a popup or inline calendar.
Provide contextual feedback messages for typical user actions with the handful of available and flexible alert messages.
Use this module whenever you need a call to action.


NYC yellow cabs and green cabs are great – you just need to flag them down. They all take credit cards, and most trips between the weekend’s venues in Brooklyn will cost around $10 – $20. A cab from JFK or LaGuardia airport will cost about $60 to most places in Manhattan and Brooklyn (Newark airport will be a bit more expensive via cab).
Another good option is Uber or Lyft car services. The cost is similar to a normal cab, but you can request a car to come directly to you, and track its location through the app. We suggest downloading the apps and setting up an account ahead of time.
NYC’s subway system, the MTA, is great. Each ride is $2.75, and you can buy cards in the station vending machines. We suggest filling it with a dollar amount if you’re planning on sharing the card. A 7-day unlimited option may be a better deal if you’re riding the train a lot, but you’ll have to wait 20 min between swipes (not so helpful for sharing).The lines and stops that are most relevant to our wedding locations are:
Franklin St, Brooklyn
Franklin St, Brooklyn
Greenpoint Ave, Brooklyn
7th Ave, Brooklyn
Grand Army Plaza, Brooklyn
7th Ave, Brooklyn
*Important note: Most subway construction and delays occur on the weekends. Allow for additional travel time and download the app NextStop on iPhone to get train maps, schedules, and status updates in your pocket. Google Maps has subway directions, but doesn’t account for delays in the total travel time estimate.


Data science
Manipulation de donnée
misc
Other articles
My first post
What does your post talk about? Write here.
read more
links
Pelican
Python.org
Jinja2
You can modify those links in your config file
social
You can add links in your config file
Another social link


Uh oh, your browser does not support modern technologies. Visit
https://whatbrowser.org/
to learn more.
Lake Shore Gold Corp.
Bell Creek Ore Processing Plant
Open Overlay
Close


Mixologist of Code and Words. Developer, Blogger and Customer Care Specialist.
Writing SEO-optimized content, technical and non-technical. Researching best keywords for better search engines' ranking for each article and customer
Contacting possible partners, selling the product and keeping their interest high in the partnership. Handling all the aspects of Social presence of employee as a Social Media Manager for the Italian market
Developed the cryptographic backend for the browser add-on Openfaux with Python language
Main Italian translator for the DuckDuckGo's interface from english to italian
Understanding customer needs and providing solutions to reported issues, selling and repairing computer hardware, set up software, upgrading computer components and software when necessary. Sales assisting.
Worked on multiple private projects, involving the use of Python and Go languages
1 month course of professional bartending and mixology
Learnt C programming language, OOP concepts using the Python programming language
Studied Windows Operating System and history of the Unix-based Operating Systems as Linux, MacOs and Bsd
Obtained a deep understanding of the TCP/IP and server/client protocols (SSH, FTP, HTTP(S), SMTP, POP3, IMAP, Telnet)
Apart from computer-related stuff, I enjoy reading, primarily fantasy and historical books, inventing new recipes, mixing drinks and being interested in anything that's art.
I do love to keep myself updated on what's going on in the software and technology world. I can live very frugally but can't live without music and a trip to the beach in summer. In my spare time I like to relax trying new cafés in town or blogging about my experiences.


THIS PAGE IS STILL UNDER CONSTRUCTION
Sorry for the inconvenience but we’re performing some maintenance at the moment. If you need to you can always contact us, otherwise this page will be available shortly!
— The Team
Sorry for the inconvenience but we’re performing some maintenance at the moment. If you need to you can always contact us, otherwise this page will be available shortly!
— The Team


united-airlines
Businessmodel of United Airlines
Customer Segments
United has a mass market business model, with no significant differentiation between customer segments. The company targets its offering at all consumers who want to take plane flights.
Value Proposition
United offers four primary value propositions: innovation, accessibility, cost reduction, and brand/status.
The company has embraced innovation from the start. Its groundbreaking firsts include:
- Introducing air-to-ground radio, improving flight safety and communication
- Introducing stewardesses, who originated as in-flight registered nurses, to airlines
- Introducing the Boeing 247, which enabled non-stop flight across the U.S. for the first time
- Introducing flight simulators with visual, motion, and sound cues for training pilots
- Becoming the first U.S airline to complete WiFi installations on its international fleet
- Becoming the first airline to offer Personal Device Entertainment (PDF) as an alternative The company creates accessibility by providing a wide variety of options. All of its domestic hubs are located in large population and business centers. This hub-and-spoke format enables it to transport customers between a high number of desinations with more frequent service than if each route were handled directly. It also enables United to add service to a new destination from a large number of cities using a limited number of aircraft. The company also creates accessibility by catering to special travel needs among passengers. It provides tailored services for customers with disabilities, children traveling alone, pregnant travelers, customers requiring extra seating, passengers with animals, senior travelers, customers with peanut allergies, and customers with various specific dietary needs.
The company reduces costs in a variety of ways, which include the following
- United Specials – last-minute getaway deals
- Offers through MileagePlus, the company’s frequent flyer program
- Promotional certificates toward air travel purchase that can be redeemed online
- Car rental offers offering discounts as high as 40% through United’s partner Hertz
- Discounts for U.S. veterans and their family members The company has established a powerful brand due to its success. It maintains the world’s most comprehensive route network, with gateways to Asia and Australia, Europe, Latin America, Africa, and the Middle East and non-stop or one-stop service from almost anywhere in the U.S. It serves 340 destinations, including 212 domestic and 127 international (with 54 countries in its reach). It experiences 5,000 daily departures on average, and transported 140 million passengers in 2015 through over 1.5 million flights. It operates the most fuel-efficient fleet among U.S. network carriers. Lastly, it has won a number of honors, including recognition by Global Traveler for having the Best Frequent Flyer Bonus Program and Best Overall Frequent Flyer Program for 12 years in a row.
Channels
United’s main channels are its website, mobile app, online travel agencies, and traditional travel agencies. The company promotes its offering through its social media pages, advertising, and participation in trade shows and conferences.
Customer Relationships
United’s customer relationship is primarily of a personal assistance nature. The company transports passengers to their destinations via plane and provides various services on each flight.
That said, there is a self-service component. The company’s various distribution channels enable consumers to purchase tickets on their own. Also, its website features a “Travel Resources” section that includes airport terminal maps, fleet specifications, how-to-guides, a currency converter, and answers to frequently asked questions.
The site also features a newsletter with updates, promotions, and tips, and an “Operational Status” section that includes information on current flight status and travel advisories. Lastly, it operates United University, which provides a continuing education program that features online courses for travel agency employees in operations and account management.
Key Activities
United’s business model entails designing and developing its services for its customers.
Key Partners
United maintains the following types of partnerships:
- United Express Partners – Airlines that support the company’s route network through the U.S. and Canada, operating a wide range of aircraft. Specific partners include Cape Air, ExpressJet, GoJet Airlines, Mesa Airlines, Republic Airlines, Shuttle America, SkyWest Airlines, and Trans States Airlines.
- Star Alliance Partners – Members of Star Alliance, the world’s largest airline alliance of which United is a founding member. It provides service to more than 190 countries through 28 member firms. Specific partners are Adria Airways, Aegean Airlines, Air Canada, Air China, Air India, Air New Zealand, All Nippon Airways (ANA), Asiana Airlines, Austrian Airlines, Avianca, Avianca Brasil, Brussels Airlines, Copa Airlines, Croatia Airlines, EGYPTAIR, Ethiopian Airlines, EVA Air, LOT Polish Airlines, Lufthansa, SAS Scandinavian Airlines, Shenzhen Airlines, Singapore Airlines, South African Airways, SWISS, TAP Portugal, THAI Airways International, and Turkish Airlines. ### Key Resources
United’s main resources are its physical resources. As of December 2015 it operated 720 mainline planes, with plans to add 21 new Boeing aircraft and six Airbus aircraft in the coming year. The company also depends on human resources in the form of travel agents, pilots, flight attendants, and other flight personnel.
Cost Structure
United has a cost-driven structure, aiming to minimize expenses through significant automation and low-price value propositions. Its biggest cost driver is likely cost of services, a variable expense. Other major drivers are in the areas of sales/marketing and transaction expenses, both fixed costs.
Revenue Streams
United has three revenue streams:
- Ticket Revenues – Revenues generated from sales of tickets to passengers for flight
- Cargo Revenues – Revenues generated from sales of flights for cargo transport
- Other Operating Revenues – Revenues generated from miscellaneous sources, including advertising solutions offered to brands and third-party businesses


UX & Information Architecture study - 2018
Car Configurator - Hyundai.com Website
Hyundai Motors Europe needed an advanced car configurator function that considers all of the different European regulations and drives higher conversions. Moreover, despite different requirements of local marketers all over the Europe, only one standardized of car configurator had to be launched to provide unified brand images across Europe.
My role
Business analyst and Information architecture
Tools
AEM(Adobe experience manager), Adobe Analytics, Java, Jira, Codebeamer and MS office suite
Research
Gather
Define
Deliver


Notes on implementing RELAX NG
This page contains pointers to documents describing various aspects
of implementing RELAX
NG.
The following are available:
- a description of how to implement
validation using an algorithm based on the idea of a derivative; this
corresponds to the algorithm implemented in Jing
- notes on how to handle the tricky
parts of simplifying the full syntax into simple syntax,
specifically how to deal with
grammar
,
define
, ref
and parentRef
- a note on how to detect
whether two name classes overlap
For some background on implementing validation of schemas in XML,
see Taxonomy of XML Schema Languages using Formal Language
Theory.
James Clark