Launch and Forget?

[sneakers55]

We're making more and more progress with our F@H programs. However, in this day and age, more and more people are upgrading to or using higher end hardware. However, installing the most productive software for F@H is starting to require knowledge and ability that many novice users just don't have and will take time to aquire.... Is it possible to write a "Launch and Forget" program that will inventory a PC and deceide on the best configuration for a F@H program? I speculate on a program that would connect the PC with a server, the two would then "talk" to each other to figure out what would be the most productive set up for the PC.

IMHO, there is only one configuration that goes with "fire and forget" and that's the CPU client as a service.

[Kingcarcas]

Probably just running the graphical client. Thing is, with all the hardware advancements and Stanford working on newer clients all the time will they ever have the time to make that type of program? Also is that font really necessary?

[uncle fuzzy]

Within these limits, the v5.04 console as a service is better than the v5.03 graphical. 5.03 will install things that can still be seen from the desktop. 5.04 will be gone unless you go hunting for it.

The down side- reconfiguring a service or adding/removing flags. It can be done, but it gets a little involved.

[VijayPande]

Right now, the CPU client as a service is the best "launch and forget" we have. In time, I expect that the GPU and SMP clients will get there too, but there's some way to go (although I think the GPU client should be getting much closer with some new revisions coming up.)

[dnnyo]

I installed console v5.04 and chose checkpoint interval quite short. then I learned that a longer checkpoint interval results in quicker finish of WU's.
So now how do I reconfigure it to more like a half hour between checkpoint writing?
It seems more time is spent writing checkpoints than writing local files or doing any work.

[anandhanju]

I installed console v5.04 and chose checkpoint interval quite short. then I learned that a longer checkpoint interval results in quicker finish of WU's.
So now how do I reconfigure it to more like a half hour between checkpoint writing?
It seems more time is spent writing checkpoints than writing local files or doing any work.

If you have an interval set to 5 minutes or less, that's the only time you will need to change this as they have been reports in the past of some problems. The time spent in writing the checkpoint doesn't seem to make any noticeable difference if the checkpoint interval is 5-30. However, if you do need to change the interval, reconfigure the client and in the config questions, go to Advanced and set the time interval.

Checkpoints are also written when a % of the WU is completed*. So even if your checkpoint interval is set to 30, you may see messages every 5 or 10 minutes. This is when a % of the WU gets complete and there are quite a few such small and fast WUs nowadays. This is nothing to worry about.

Edit: *-This appears to be dependant on the FAHCore* that is being used for the protein. Thank you codysluder, for this info.