This file lists previously undocumented features available in the program. These features may change or be discontinued at any time. Their use is totally unsupported. In prime.txt you can force the program to use different filenames for 6 files. You can also change the working directory (identical to the -W command line argument). prime.ini=your_filename local.ini=your_filename worktodo.ini=your_filename prime.log=your_filename prime.spl=your_filename results.txt=your_filename WorkingDir=your_directory_name Some options in prime.txt can be configured to have different values at different times of the day using this syntax: Option=setting where setting is defined as value OR value during list-of-times else setting At present, only Memory, MaxHighMemWorkers, PauseWhileRunning, LowMemWhileRunning, and PauseCheckInterval support this during/else syntax. Also note you can no longer edit these options from the user interface. To use this feature, you must manually edit the prime.txt/local.txt file. An example in local.txt: Memory=500 during 1-5/17:30-24:00,1-5/0:00-8:30,6-7/0:00-24:00 else 200 The 1-5 and 6-7 refer to days of the week, with Monday=1 and Sunday=7. The time portion refers to the hours of the day based on a 24-hour clock. You do not need to specify days of the week (e.g. 1-7/0:00-8:00 is the same as 0:00-8:00). The above example lets the program use 500MB during the week from 5:30PM to 8:30AM and all day on weekends. Otherwise (weekdays from 8:30AM to 5:30PM), the program can use only 200MB. There are some additional PRP proof controls that are not available in the Resource Limits dialog box. In local.txt, PreallocateDisk=0 or 1 (default is 1) will control whether disk space to hold the PRP proof residues is allocated at the beginning of the PRP test to insure we do not run out of disk space midway through the PRP test. In prime.txt, MaxProofgenWaits=n (default is 48*60/5 = 48 hours) Maximum number of 5 minute waits to execute when an error occurs during proof generation. An error should only occur if a disk is full or offline. We hope the disk problem will resolve itself within 2 days and proof generation can complete. In prime.txt, ProofPower=x (x can be from 5 to 12) ProofPowerAdjust=y (y can be from -2 to +3) these override the selection of proof power based on temporary disk space available. I don't see any reason to ever use these 2 settings. ProofPower sets the proof power to x. ProofPowerAdjust is added to the proof power calculated based on temporary disk space. If the proof power is higher than the optimal proof power, then the proof power is reduced to the optimal proof power. Also available in the Primenet section of prime.txt, ProofUploads=0 or 1 (default is 1) UploadChunkSize=n (in MB, between 1 and 8) DownloadRateLimit=n (in Mbps, default is 0 which means unlimited) The first option can disable proof uploads. You will be responsible for taking the proof files to a machine that is doing proof uploads. One might have a script that moves proofs to a central machine for uploading -- to make sure at most one upload is in progress at any time. You can choose the "chunk" size for uploading. The default is based on your upload rate limit. Slow uploads are done 1MB at a time, fast uploads use larger chunks. Rate limiting the downloads is available but I don't see the need to ever use this as certification downloads are only around a dozen megabytes. The program strives to use proof power 8 for large prime tests. This keeps certification workload low. If temporary disk space resource limit will not let the program use proof power 8, the program may simulate a higher proof power by creating a larger proof file. For example, doing a power=7 proof on the first half of a PRP test and a second power=7 proof on the second half of a PRP test is equivalent to running a power=8 proof but using half the temporary disk space and twice the upload bandwidth. In prime.txt, add ProofPowerMult=1 to disable creating larger proof files to simulate a higher proof power. However, if temporary disk space resources, proof file size resources, and upload bandwidth resources are this limited it is strongly recommended switching to less demanding work, such as double-checking. There are also some options for controlling certification work. In local.txt, add CertWorker=n CertMinExponent=x CertMaxExponent=y This let's you do certifications only on the specified worker number n. You can also control the range of exponents you are willing to do certifications for. You can control whether the program does extra error checking on every iteration of a primality test. This runs a little bit slower. Windows user can control the first of these options from the Advanced Menu. Add one or both of these lines to prime.txt to control these options: ErrorCheck=0 or 1 SumInputsErrorCheck=0 or 1 The first line controls "ROUNDOFF > 0.4" error checks, the second line controls "SUM(INPUTS) != SUM(OUTPUTS)" error checks available in pre-AVX FFTs (which makes it pretty much obsolete). You can control how the "count of errors during this test" message is output with every screen update. These messages only appear if possible hardware errors occur during a test. In prime.txt set: ErrorCountMessages=0, 1, 2, or 3 Value 0 means no messages, value 1 means a very short messages, value 2 means a longer message on a separate line, value 3 means a very long message possibly on multiple lines. Default value is 3. You can control how often Jacobi error checking is run. Default is 12 hours. If a Jacobi test takes 30 seconds, then the default represents an overhead of 30 / (12 * 60 * 60) or 0.07% overhead. Each Jacobi test has a 50% chance of discovering if a hardware error has occured in the last time interval. In prime.txt: JacobiErrorCheckingInterval=N (default is 12) where N is in hours. You can control how many save files are kept that have passed the Jacobi error check. This value is in addition to the value set by the NumBackupFiles setting. So if NumBackupFiles=3 and JacobiBackupFiles=2 then 5 save files are kept - the first three may or may not pass a Jacobi test, the last two save files have passed the Jacobi error check. In prime.txt: JacobiBackupFiles=N (default is 2) You can disable Jacobi error checking which has a 50% chance of catching hardware errors. You might do this if you are running the first LL test and double-checking LL test concurrently. In prime.txt JacobiErrorCheck=0 or 1 (default is 1) You can disable printing Jacobi error-checking messages using this prime.txt entry: SilentJacobi=0 or 1 (default is 0) You can force the Options/CPU dialog to display times using AM/PM or a 24-hour clock format. Otherwise, the program will make its best guess as to the proper format. Add this line to prime.txt: AMPM=n where n is 1 for AM/PM formatting and n is 2 for 24-hour formatting. You can adjust how many decimal digits of precision are displayed in lines output to the screen. In prime.txt enter a value between 0 and 6: PercentPrecision=n You can choose whether the program uses the high resolution system clock, the standard system clock, or the read timestamp counter instruction (RDTSC) to time events. By default the program uses the high resolution system clock if available. Choose one of these values for n (default is 1): 0 - use the system clock. 1 - use RDTSC but do not output clock counts. 2 - use RDTSC and output clock counts. The above values will only have an effect if a high resolution system clock is not available. You can force the program to bypass the high resolution clock by adding 10 to one of the values above. In prime.txt, enter RdtscTiming=n You can alter the way the program outputs timings. In prime.txt set: TimingOutput=n Where n=1 for seconds with 3 digits of precision, n=2 for milliseconds with 1 digit of precision, n=3 for milliseconds with 2 digits of precision, n=4 for milliseconds with 3 digit of precision. You can change the formatting of date and time to the screen. In prime.txt: TimeStamp=n where n=0 turns output off, n=1 is the default date/time without seconds, n=2 is date/time with seconds, n=3 is time only without seconds, n=4 is time-only with seconds. You can have the timings that are output to the screen be cumulative (from program restart or start of a new exponent) rather than resetting after each screen output (ClassicOutput=1 only). Add this line to prime.txt: CumulativeTiming=1 You can change the interval between outputs of the timestamp to the results.txt file ResultsFileTimestampInterval=n If n is zero, the timestamp will never be output. Otherwise the timestamp will be written no more frequently than every n seconds. Default for n is 300 which is 5 minutes. You can revert to the "classic" style output for worker windows doing Lucas-Lehmer and PRP tests. This classic style does not display the ETA. This style was in use prior to version 28.5. In prime.txt: ClassicOutput=0 or 1 (default value is 0) You can output the maximum round off error seen thusfar in the worker windows when doing LL or PRP tests. OutputRoundoff=0 or 1 (default value is 0) You can reset the maximum round off error seen thusfar after each time the maximum round off is output. CumulativeRoundoff=0 or 1 (default value is 1) You can update the title more frequently than the lines are output to the worker window. This feature, only useful in Windows, allows you to keep track of progress in the tray icon or window title without "cluttering up" the worker window. In prime.txt: Titl...
hacyy