1 Attachment(s)
cheap tricks ? 32M initial values, pi_rec.dat2 and 16K time
32M initial value range:
Low-range = ~ 6.5s (9.xx), and ~ 7.0s (10.xx)
High-range = ~ 7.0s (9.xx), and ~ 7.5s (10.xx)
i found the 'switch' between High or Low for 32M initial values: the 16K time recorded in the pi_rec.dat2 file.
for Low-range 32M initials, a sub-0.109s 16K time must be present in pi_rec.dat2 before the Spi exe is started (from same folder).
--------------------------
to activate Low-range 32M initials:
(1) delete pi_rec.dat2 from an existing SPi folder, or unzip new Spi folder (running 32M at this stage will give High initials)
(2) using the local Spi exe, run a 16K time below 0.109s (ie 0.094s or less). The created pi_rec.dat2 will contain the Low initial 'instruction'.
http://i447.photobucket.com/albums/q...URES/16k94.jpg
All further instances of Spi opened from the same folder will produce Low-range 32M initial values, but the already open Spi is not affected.
to test this before closing the original Spi, a second instance of Spi can be started from the same folder.
the original will give High 32M initials, and the second instance will give Low.
http://i447.photobucket.com/albums/q...2MHigh_Low.jpg
(3) failed runs can cause 32M initials to switch back to High. It may not be possible to restore Low initials to a pi_rec.dat2 which has suffered a failed run. Instead, repeat steps (1) and (2), or replace 'corrupted' pi_rec.dat2 with a Low 16K copy..... :up:
cheap :yepp:
pi_rec.dat2 (16K = 0.094s)
32M initial values + pi_rec.dat2 : update
guys, just a 'minor' update/correction to this, but the general behaviour is still the same.
my earlier pre-conditions for 32M initials are not correct: Pi size and time are both irrelevant.
i found that any result for any Pi size, if present in pi_rec.dat2 before SuperPi is opened, can reduce 32M initials by 0.5s.
re-tested with runs from 16K up to 32M and they all produced the same effect on 32M initials. Don't know if there is a threshold time for any particular Pi size, but i also tested @ 3Ghz with same results.
new tests/results:
for High 32M initial:
1) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), run 32M (High initial showing)
2) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), close Spi, open new Spi, run 32M (High initial showing)
3) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), run Pi size X, run 32M (High initial showing)
for Low 32M initial:
4) delete pi_rec.dat2, open Spi (new pi_rec.dat2 created), run Pi size X, close Spi, open new Spi, run 32M (Low initial showing)
doubtful that this was really a sensible use of time, but the aim for me was to find a consistent way to get one or other type of 32M initial :rolleyes: :D
cheap
