A free Demo version of Fluxica Peregrine is available for evaluation purposes. The Demo version is able to demonstrate the functionality of the commercial versions, but it runs with restrictions. The difference between the versions is shown in the table below.
As the Demo version is without true RNG seeding, the sequence of generated test probe values is the same for each test invocation, but the sequence itself is without bias for a given invocation. With true RNG seeding, the sequence of generated test probe values does not repeat itself for different test invocations.
The maximum number of test iterations for a single invocation of the Peregrine program determines the statistical significance of a test. The significance increases with the number of test iterations.
The maximum number of test probes NP are the last NP test probes that have been injected into the program under test at any given moment in the test cycle. The probe log reports the last NP test probes on test completion or termination.
End User License Agreement
The Demo version is available for download after accepting the EULA. The EULA is a product license, not a sale. The EULA can be found here. The EULA is also available as a downloadable PDF file.
All Peregrine versions are installed in the same manner and ready to be used in four steps:
Create a directory $HOME/peregrine and download the archive file peregrine_demo.tar.gz with the download button above.
Extract the archive file with tar -xvf peregrine_demo.tar.gz -C $HOME/peregrine.
First moving the archive file to $HOME/peregrine directory and then extracting it with tar -xvf peregrine_demo.tar.gz is also possible.
In $HOME/peregrine, assign read, write and execute permission to the file owner of the peregrine program with chmod 700 peregrine and chmod 700 peregrine_gui.
It is usually convenient, but not required, to make the Peregrine executable files, header file and library file available through the /usr/bin/, /usr/include/ and /usr/lib/ directories, respectively, by symbolic linking. Alternatively, the files can also be directly copied or moved to the respective standard directories. See the Reference Manual for more information.
A Reference Manual, which applies to all Peregrine versions, is included in the download as a PDF file. The manual is located in the $HOME/peregrine/support directory after extracting the archive file. The Demo download package includes an abbreviated version of the manual.
Test Setup from a Bird's Eye View
The test is set up in four steps:
Include the Peregrine header file.
Add two Peregrine code delimiters around the code segment to be tested.
Replace (selected) variables with matching Peregrine probe types in the marked out code segment.
Compile the program source code to create an executable file as usual and additionally link against the Peregrine library.
Invoking the Peregrine program and then running the executable file will automatically test the code segment by continuously injecting it with uniformly distributed (unbiased) pseudo-random probe values through the Peregrine probe types. These test values are generated on-the-fly at high speed by the Peregrine program.
The test continuous until the code breaks, a timeout is triggered or a specified number of test iterations is reached. A probe log provides the test results for a post-test analysis.