On Linux* OS: After unpacking the Intel® Trace Collector archive in a folder of your choice read the file relnotes.txt for information on how to install Intel® Trace Collector.
On Microsoft Windows* OS: run the installation file setup.exe and follow the instructions given in the installation wizard.
Traces of just one process can be generated with the libVTcs library, which allows the generation of executables that work without MPI.
Linking is accomplished by adding libVTcs.a (VTcs.lib on Microsoft* Windows* OS) and the libraries it needs to the link line:
The checking addresses two different concerns:
Finding programming mistakes in the application that need to be fixed by the application developer. These include potential portability problems and violations of the MPI standard which do not immediately cause problems, but might when switching to different hardware or a different MPI implementation.
gettimeofday is the default timer on Linux* OS with _ftime being the equivalent on Microsoft* Windows* OS. Its API limits the clock resolution to 1μs, but depending on which timer the OS actually uses the clock resolution may be much lower (_ftime usually shows a resolution of only 1 millisecond). It is implemented as a system call; therefore it has a higher overhead than other timers.
There are two examples using MPI as means of communication and process handling. But as they are not linked against the normal Intel® Trace Collector library, tracing of MPI has to be done with VT API calls.
--merge [<merged trace name>]
Merges the given raw trace.
When you use the --merge option with the --delete-raw-data option, such configuration deletes the given raw trace after merging.
Intel® Trace Collector is automatically initialized within the execution of the MPI_Init() routine. During the execution of the MPI_Finalize() routine, the trace data collected in memory or in temporary files is consolidated and written into the permanent trace file(s), and Intel® Trace Collector is terminated.