''In theory,'' the random number generators are in no way threadsafe, neither the old `rand()`, nor the mersenne twister of the C++ standard. However, since all we want is some arbitrarily diffused numbers, chances are that this issue can be safely ignored; because a random number computation broken by concurrency will most likely generate -- well, a garbled number or "randomly" corrupted internal state. Validating this reasoning by an empiric investigation seems advisable though.
22 lines
360 B
Text
22 lines
360 B
Text
TESTING "Library Test Suite: calculation" ./test-suite --group=calculation
|
|
|
|
|
|
|
|
TEST "Data Table with CSV storage" DataCSV_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
PLANNED "Statistic and Regression" Statistic_test << END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Random numbers and Seed" Random_test << END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Concurrent PRNG access" RandomConcurrent_test << END
|
|
return: 0
|
|
END
|