trace.cpp File Reference

Functions
boost::iostreams::stream< boost::iostreams::null_sink >	nullStream ((boost::iostreams::null_sink()))
FileType	Trace_Files__ ()
	Semi-formatted text-based outputs.
void	traceFormatedFloat (Trace &trace, double val, string formatStr)
void	printHex (Trace &trace, vector< unsigned char > &chunk)
void	traceJson_ (Trace &trace, GTime &time, vector< ArbitraryKVP > id, vector< ArbitraryKVP > val)
bool	createNewTraceFile (const string id, boost::posix_time::ptime logptime, string new_path_trace, string &old_path_trace, bool outputHeader, bool outputConfig)

Function Documentation

createNewTraceFile()

bool createNewTraceFile	(	const string	id,
		boost::posix_time::ptime	logptime,
		string	new_path_trace,
		string &	old_path_trace,
		bool	outputHeader,
		bool	outputConfig )

Here is the call graph for this function:

Here is the caller graph for this function:

nullStream()

boost::iostreams::stream< boost::iostreams::null_sink > nullStream

(

(boost::iostreams::null_sink())

)

printHex()

void printHex	(	Trace &	trace,
		vector< unsigned char > &	chunk )

Trace_Files__()

FileType Trace_Files__

(

)

Semi-formatted text-based outputs.

Trace files are the best record of the processing that occurs within the Pea.

The level of trace may be set numerically by configuration. It will enable more or fewer lines of detail, and in some cases, the number of columns to be included in formatted sections.

Receivers and Satellites may have trace file outputs configured, which will include details specific to their processing, such as any preprocessing, and details about measurements that are being computed.

Calculated satellite and receiver positions, and reasons for the exclusion of any measurements are recorded in the receiver trace files.

When satellite orbit propagation is enabled, some details about modelled forces may be available in satellite trace files.

The receiver files may be configured with residual chain outputs on, which will produce formatted output of each modelled component as they are subtracted from the measured quantity. Depending on the possibility of chunking, receiver trace files may also include states that are usually only recorded in the network trace files.

Once the list of measurements is aggregated and passed to the main filter, trace outputs are written to the 'network' trace file. This contains any filter states, measurement residuals, state removals or reinitialsations, and iteration details.

The filter outputs in the network trace file include blocks that are formatted with SINEX-style +BLOCK...-BLOCK sections, which may allow for easier post-processing by eliminating any information outside of the required section.

Here is the caller graph for this function:

traceFormatedFloat()

void traceFormatedFloat	(	Trace &	trace,
		double	val,
		string	formatStr )

Here is the caller graph for this function:

traceJson_()

void traceJson_	(	Trace &	trace,
		GTime &	time,
		vector< ArbitraryKVP >	id,
		vector< ArbitraryKVP >	val )

Here is the call graph for this function: