FAH Tips [Archive] - PCSTATS Forum

BionicRedneck

06-15-04, 02:26 PM

I have been folding since Dec 2001 and have ran the windows cli and gui, the linux client, and even the window cli and gui with linux using wine. So I pretty much have a handle on the ins and outs on what work and what doesn't. there are 4 different cores FAHCore_65, FAHCore_c9, FAHCore_78, and FAHCore_ca. FAHCore_65: is for tinker wu's FAHCore_c9: is for the older genome wu's FAHCore_78: is for gromacs wu's (uses SSE/3dnow extended) FAHCore_ca: is for the newer genome wu's First off you have different flags you can use with the client. -config: Allows users to change their configuration information. This includes user & team names (reflected in the stats), whether or not to ask before a network connection is made to fetch/send work, set up proxy servers, preferred work unit type (Folding/Genome), process priority, CPU usage requested (5-100%), whether or not to use assembly loops, whether or not to use deadline information, and Machine ID changes. -delete x: Delete item #x from work queue. This option should only be used if there is a serious error with the current unit that the client does not automatically recover from (e.g. crash-inducing). This should not normally happen, and if it does, we would be grateful if you could send us the FAHlog.txt file from the unit that causes the error. -license: Displays the end-user license agreement -queueinfo: Get information on queued work units. Includes for each unit the status (READY/FINISHED/EMPTY), unit type (Folding/Genome), originating server, and date when the unit was received (local time in GMT), as well as deadline if the server sent that information. -send x: Send result #x back to server. Exits after trying to send unit (successfully or unsuccessfully). Use "-send all" to send all results outstanding. If unit x is not a completed work unit then the client exits without doing anything. -verbosity x: Sets the output level, from 1 to 9 (max). The default is 3. This option should be used if the user wishes to see more detailed client output, particularly useful if there is a problem which needs to be reported to the F@H client development team. -forceasm: Instruct the core to use SSE/3DNow assembly instructions if possible, even if it has previously made the determination that the machine may not be handling this well. -advmethods: Request to be assigned any new Cores or work units. (typically it give you Gromacs wu's) -local: Use configuration files from local directory. This option has no meaning on Linux, but is vital on Windows and Macintosh for running multiple clients on a machine. It instructs the client to read its config information from the client.cfg file in the current directory rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, the Library/Folding@home directory. Information such as the user name, team name, proxy information, machine ID are maintained in the client.cfg file. The flag ensures that work does not conflict. Use "-local" only if you are planning on running more than one instance of Folding@Home on the same machine (this is only useful if you are running on a multi-processor machine). Create as many directories as there are processors on the machine, copy the exe files and client.cfg file into each of these directories, run "FAH3Console -local -config" on each and specify unique machine IDs for each directory (under the Advanced Settings option). From then onwards you may run each copy by switching to its directory and running with the -local flag. -help: Print out the command line flags available and then exit. Linux Specific -freeBSD: For use by those wishing to use the Linux client on a machine running FreeBSD. See our FAQ for details on how to do this, but with this flag, all Cores downloaded will automatically be branded as being a Linux executable. Windows Specific The below options are accepted but ignored by the clients for operating systems other than Microsoft Windows. -pause: Pause after finishing and trying to send current unit. Allows a user to shut down after finishing a unit, by pressing Ctrl-C, without then getting new work to process. This is recommended if you are planning on shutting down your machine for a long time (e.g. for a vacation), or are planning to un/re-install F@H after finishing the currently processing work unit. -service: Run in service mode (for programs such as firedaemon). This prevents the client from exiting when it detects the current user is logging out. If this option is used when the client is not run as a service then it will run normally, but will not shut down automatically if the user logs out, and a "Wait for program to close." dialog box will be displayed. From a most point per a day stand point running the client with the -advmethods and -forceasm gives you gromacs wu's but you need to have a cpu that uses SSE or 3dnow extended Note: you may have to lower your overclock somewhat with these types of work units and you will also notice a higher cpu temps. The way to use the flags is make a shorcut to the client and right click on it go to properties and where it says target it will have the path to the client just after the last " add a space then the flag and as many flags as you want. I recommend one shortcut for -advmethod -forceasm another for -send all and one more for -queueinfo Other Tips 1)FAH depends soley on mhz and fsb doesn't have an effect eithier way. 2)Don't use screen saver it's really slow. 3)if using gui keeping minimized to tray will improve speed. 4)If you have a problem with the client when you show display try updating your video card driver. 5)Dont freak if you get a genome work unit instead of a Folding one you will still get credit. 6)For linux if you run the windows client with wine you will see alot faster frame times and if you decide to run the gui w/ wine don't even think about showing the display if you do you will run into problems 7)The gromacs work units give you roughly about 3x what a tinker work unit would per a day so if you have a stable cpu use the -advmethods flag 8)even with the -advmethods flag if that server isn't sending them out then the AS will send you to another server. 9)The way stanford figures out how many points a wu is worth is they benchmark it with a celereon 500 and 1 day= 1 pt 10)disable ckecking of deadline in config or if you decide to change day or time on your system for any reason your wu might get deleted. 11)To shut down console use ctrl+c