For each of the Interfaces there is a listen-INTERFACE-unix node that creates a listening UNIX stream socket to send out a packet stream, and there is a connect-INTERFACE-unix node that connects to a UNIX stream socket and receives the packets.

The connect-INTERFACE-unix nodes are sources of that particular interface.

Help

Usage:

connect-cooked-unix [OPTION]... PATH

Allowed options:

Option	Description
`--help`	produce help message
`--socket-path PATH`	connect to UNIX socket at PATH

connect-cooked-unix

Type signature: (->cooked)

Example

sdgps connect-cooked-unix my_socket ! tracker ! decoder

In this example, by connecting to the socket we can stream cooked packets for local processing. As mentioned in other places in the documentation, we cannot terminate this node chain on this node since the cooked interface has desired correlator configurations being sent backwards to the cooked source.

connect-cooked2-unix

Type signature: (->cooked2)

Example

sdgps connect-cooked2-unix my_socket ! decoder

By connecting to the socket we can stream cooked2 packets.

connect-observables-unix

Type signature: (->observables)

Example

sdgps connect-observables-unix my_socket ! kf2

Here, we process the observables packets from a socket to get a solution using the kf2 node.

connect-raw-unix

Type signature: (->raw)

Example

sdgps connect-raw-unix my_socket ! write-raw-file foo.raw

Here we write the raw packets being streamed on a socket to a file called foo.raw

connect-solution-unix

Type signature: (->solution)

Example

sdgps connect-solution-unix my_socket ! write-solution-file --filename foo.sol

Here we write the solution packets being streamed on a socket to a file called foo.sol