Digital constellation for 8PSK.
Constructor Specific Documentation:
Digital constellation for BPSK .
Constructor Specific Documentation:
Calculate Euclidian distance for any constellation.
Constellation which calculates the distance to each point in the constellation for decision making. Inefficient for large constellations.
Constructor Specific Documentation:
Make a general constellation object that calculates the Euclidean distance for hard decisions.
Parameters: |
|
---|
Digital constellation for DQPSK.
Constructor Specific Documentation:
constellation_psk
Constellation space is divided into pie slices sectors.
Each slice is associated with the nearest constellation point.
Works well for PSK but nothing else.
Assumes that there is a constellation point at 1.x
Constructor Specific Documentation:
Parameters: |
|
---|
Digital constellation for QPSK.
Constructor Specific Documentation:
Rectangular digital constellation
Only implemented for 1-(complex)dimensional constellation.
Constellation space is divided into rectangular sectors. Each sector is associated with the nearest constellation point.
Works well for square QAM.
Works for any generic constellation provided sectors are not too large.
Constructor Specific Documentation:
Make a rectangular constellation object.
Parameters: |
|
---|
Creates a QPSK constellation.
Creates a PSK constellation object.
Creates a QAM constellation object.
If large_ampls_to_corners=True then sectors that are probably occupied due to a phase offset, are not mapped to the closest constellation point. Rather we take into account the fact that a phase offset is probably the problem and map them to the closest corner point. It’s a bit hackish but it seems to improve frequency locking.