Skip to content

← statistics package

PairwiseComparisons

Calculate all pairwise multiple comparisons for each factor plus optional interactions using Tukey HSD.

This method corrects for family-wise error rates. Version 0.1.0

Ports/Properties

data

A packet containing at least one signal chunk with an instance axis.

verbose name
Data
default value
None
port type
DataPort
value type
Packet (can be None)
data direction
INOUT

pairwise_stats

Pairwise multiple comparisons post-hoc statistics using Tukey HSD. The output packet will contain 1 named stream for each of the factor(s)/interaction specified.

verbose name
Pairwise Stats
default value
None
port type
DataPort
value type
Packet (can be None)
data direction
OUT

factors

List of factors (needs to be instance field names) to use for pairwise comparisons. This can be either 1 or 2 factors.

verbose name
Factors
default value
['Marker']
port type
ListPort
value type
list (can be None)

include_interaction

Include interaction pairings if 2 factors are provided. Note, this will create all pairings across each individual level for each of the given factors (e.g. 3 levels each for 2 factors would create 9C2 = 36 comparisons).

verbose name
Include Interaction
default value
True
port type
BoolPort
value type
bool (can be None)

use_caching

Enable caching.

verbose name
Use Caching
default value
False
port type
BoolPort
value type
bool (can be None)

num_procs

Number of parallel processes to use. The maximum would be the number of channels in the data. If given as -1, this will use one process per core on the system, and if given as None, this will use as many processes as there are cores in the system, divided by OMP_NUM_THREADS (or 4 if not present).

verbose name
Num Procs
default value
1
port type
IntPort
value type
int (can be None)

verbose

Verbose output. Can be used for debugging your pipeline.

verbose name
Verbose
default value
False
port type
BoolPort
value type
bool (can be None)

set_breakpoint

Set a breakpoint on this node. If this is enabled, your debugger (if one is attached) will trigger a breakpoint.

verbose name
Set Breakpoint (Debug Only)
default value
False
port type
BoolPort
value type
bool (can be None)

metadata

User-definable meta-data associated with the node. Usually reserved for technical purposes.

verbose name
Metadata
default value
{}
port type
DictPort
value type
dict (can be None)