Page 1 of 1

-oneunit flag

Posted: Sun Jun 15, 2008 8:20 pm
by Phred15
Do you think someone could work on this flag. I have three stranded smp WUs because it is not working. I am shutting down some computers during the hot weather.

Re: -oneunit flag

Posted: Sun Jun 15, 2008 11:01 pm
by parkut
What seems to be the problem?

The -oneunit flag is supposed to terminate the client when the WU is done.

Perhaps you restarted the FAH client again after the first WU was completed... I think it will download a fresh WU and run the new one to completion.

Re: -oneunit flag

Posted: Sun Jun 15, 2008 11:02 pm
by jrweiss
Are you trying to use the -oneunit flag in a Startup shortcut or in a Service command line? If so, those will override the intent of the flag on restart if the WU has finished...

Re: -oneunit flag

Posted: Mon Jun 16, 2008 5:03 pm
by Phred15
I am using the smp client in a command window. I did not restart it. I added -oneunit in the fah.exe properties window. I now have four stranded work units.

Re: -oneunit flag

Posted: Mon Jun 16, 2008 5:09 pm
by bruce
I'm not sure I understand what you're saying, phred15. Please post FAHlog.txt showing at least the top 60 lines and the sections where you have the 4 stranded units. Also, run -queueinfo (or qd) so we'll know what those units are. Have they passed the deadlines?

Restart the client with -verbosity 9 -send all and post that FAHlog.txt, too.

Re: -oneunit flag

Posted: Mon Jun 16, 2008 5:10 pm
by 7im
Stranded because the flag didn't work, or because the work servers were busy when the client tried to upload. -oneunit only tries to upload a few times before it quits and gives up.

Posting examples of the problem from your fahlogs would help us understand the problem, and help Pange Group improve the behavior as needed.

EDIT: Plus what Bruce said to unstrand those WUs. ;)

Re: -oneunit flag

Posted: Tue Jun 17, 2008 4:20 am
by Phred15
I'm sorry about the lack of information.. I've been folding for 10 years and I get frustrated when I can't figure things out. Here are two of the logs. The -one unit flag is not even recognized at the finish of the work unit. Maybe it should be the first flag. I did not write in the .exe.

Code: Select all

Launch directory: C:\FAH
Executable: C:\FAH\fah -verbosity 9 -oneunit.exe


[17:05:45] - Ask before connecting: No
[17:05:45] - User name: Phred15 (Team 11108)
[17:05:45] - User ID: 591A69DE2B9FDFD0
[17:05:45] - Machine ID: 1
[17:05:45] 
[17:05:45] Loaded queue successfully.
[17:05:45] 
[17:05:45] + Processing work unit
[17:05:46] Core required: FahCore_a1.exe
[17:05:46] Core found.
[17:05:46] Working on Unit 02 [June 14 17:05:46]
[17:05:46] + Working ...
[17:05:46] 
[17:05:46] *------------------------------*
[17:05:46] Folding@Home Gromacs SMP Core
[17:05:46] Version 1.74 (March 10, 2007)
[17:05:46] 
[17:05:46] Preparing to commence simulation
[17:05:46] - Ensuring status. Please wait.
[17:06:03] - Looking at optimizations...
[17:06:03] - Working with standard loops on this execution.
[17:06:03] - Previous termination of core was improper.
[17:06:03] - Going to use standard loops.
[17:06:03] - Files status OK
[17:06:15] - Expanded 4732455 -> 24426905 (decompressed 516.1 percent)
[17:06:15] 
[17:06:15] Project: 2665 (Run 3, Clone 295, Gen 11)
[17:06:15] 
[17:06:23] Entering M.D.
[17:06:31] Calling FAH init
[17:06:32] ater
[17:06:32] Writing local files
[17:06:32] Completed 2500 out of 250000 steps  (1 percent)
[17:06:32] water
[17:06:32] Writing local files
[17:06:32] Completed 2500 out of 250000 steps  (1 percent)
[17:06:39] Extra SSE boost OK.
[17:19:52] Writing local files
[17:19:52] Completed 5000 out of 250000 steps  (2 percent)

snip

[14:41:43] Completed 247500 out of 250000 steps  (99 percent)
[14:54:54] Writing local files
[14:54:54] Completed 250000 out of 250000 steps  (100 percent)
[14:54:54] Writing final coordinates.
[14:54:55] Past main M.D. loop
[14:54:56] Will end MPI now
[14:55:56] 
[14:55:56] Finished Work Unit:
[14:55:56] - Reading up to 21310704 from "work/wudata_02.arc": Read 21310704
[14:55:56] - Reading up to 557712 from "work/wudata_02.xtc": Read 557712
[14:55:56] goefile size: 0
[14:55:56] logfile size: 212426
[14:55:56] Leaving Run
[14:55:58] - Writing 22087214 bytes of core data to disk...
[14:56:00]   ... Done.
[14:56:00] - Failed to delete work/wudata_02.sas
[14:56:00] - Failed to delete work/wudata_02.goe
[14:56:00] Warning:  check for stray files
[14:56:00] - Shutting down core
[14:58:00] 
[14:58:00] Folding@home Core Shutdown: FINISHED_UNIT
[14:58:00] 
[14:58:00] Folding@home Core Shutdown: FINISHED_UNIT
[14:58:06] CoreStatus = 64 (100)
[14:58:06] Sending work to server


[14:58:06] + Attempting to send results
[15:03:50] + Results successfully sent
[15:03:50] Thank you for your contribution to Folding@Home.
[15:03:50] + Number of Units Completed: 30

[15:05:54] - Preparing to get new work unit...
[15:05:54] + Attempting to get work packet
[15:05:54] - Connecting to assignment server
[15:05:55] - Successful: assigned to (171.64.65.64).
[15:05:55] + News From Folding@Home: Welcome to Folding@Home
[15:05:55] Loaded queue successfully.
[15:06:01] + Closed connections
[15:06:01] 
[15:06:01] + Processing work unit
[15:06:01] Core required: FahCore_a1.exe
[15:06:01] Core found.
[15:06:01] Working on Unit 03 [June 15 15:06:01]
[15:06:01] + Working ...
[15:06:02] 
[15:06:02] *------------------------------*
[15:06:02] Folding@Home Gromacs SMP Core
[15:06:02] Version 1.74 (March 10, 2007)
[15:06:02] 
[15:06:02] Preparing to commence simulation
[15:06:02] - Ensuring status. Please wait.
[15:06:03] - Starting from initial work packet
[15:06:03] 
[15:06:03] Project: 2653 (Run 22, Clone 4, Gen 71)
[15:06:03] 
[15:06:04] Assembly optimizations on if available.
[15:06:04] Entering M.D.
[15:06:22] ial work packet
[15:06:22] 
[15:06:22] Project: 2653 (Run 22, Clone 4, Gen 71)
[15:06:22] 
[15:06:22] 653 (Run 22, Clone 4, Gen 71)
[15:06:22] 
[15:06:26] Entering M.D.
[15:06:32] Rejecting checkpoint
[15:06:33] SE boost OK.
[15:06:33] ein in POPCExtra SSE boost OK.
[15:06:33] 
[15:06:33] Extra SSE boost OK.
[15:06:34] Writing local files
[15:06:34] Completed 0 out of 500000 steps  (0 percent)
[15:15:07] Writing local files
[15:15:07] Completed 5000 out of 500000 steps  (1 percent)
[15:23:40] Writing local files
[15:23:40] Completed 10000 out of 500000 steps  (2 percent)

snip

[16:32:05] Completed 50000 out of 500000 steps  (10 percent)
[16:40:38] Writing local files
[16:40:38] Completed 55000 out of 500000 steps  (11 percent)
Machine # 2

Code: Select all

Launch directory: C:\FAH
Executable: C:\FAH\fah -verbosity 9 -forceasm -oneunit.exe


[18:48:54] - Ask before connecting: No
[18:48:54] - User name: Phred15 (Team 11108)
[18:48:54] - User ID: C41E96D3D48A72A
[18:48:54] - Machine ID: 1
[18:48:54] 
[18:48:54] Loaded queue successfully.
[18:48:54] 
[18:48:54] + Processing work unit
[18:48:54] Core required: FahCore_a1.exe
[18:48:54] Core found.
[18:48:54] Working on Unit 05 [June 14 18:48:54]
[18:48:54] + Working ...
[18:48:55] 
[18:48:55] *------------------------------*
[18:48:55] Folding@Home Gromacs SMP Core
[18:48:55] Version 1.74 (March 10, 2007)
[18:48:55] 
[18:48:55] Preparing to commence simulation
[18:48:55] - Ensuring status. Please wait.
[18:49:12] - Looking at optimizations...
[18:49:12] - Working with standard loops on this execution.
[18:49:12] - Previous termination of core was improper.
[18:49:12] - Going to use standard loops.
[18:49:12] - Files status OK
[18:49:17] - Expanded 2442683 -> 12890749 (decompressed 527.7 percent)
[18:49:18] 
[18:49:18] Project: 2653 (Run 3, Clone 24, Gen 71)
[18:49:18] 
[18:49:22] Entering M.D.
[18:49:28] Calling FAH init
[18:49:29] in POPC
[18:49:29] Writing local files
[18:49:29]  checkpoint)
[18:49:29] Read checkpoint
[18:49:29] 0 steps  (30 percent)
[18:49:29] Extra SSE boost OK.
[18:49:29] es
[18:49:29] Completed 150000 out of 500000 steps  (30 percent)
[18:49:31] Extra SSE boost OK.
[19:05:36] Writing local files
[19:05:36] Completed 155000 out of 500000 steps  (31 percent)

snip

[13:31:21] Completed 495000 out of 500000 steps  (99 percent)
[13:47:21] Writing local files
[13:47:21] Completed 500000 out of 500000 steps  (100 percent)
[13:47:21] Writing final coordinates.
[13:47:22] Past main M.D. loop
[13:47:22] Will end MPI now
[13:48:22] 
[13:48:22] Finished Work Unit:
[13:48:22] - Reading up to 3721776 from "work/wudata_05.arc": Read 3721776
[13:48:22] - Reading up to 1936452 from "work/wudata_05.xtc": Read 1936452
[13:48:22] goefile size: 0
[13:48:22] logfile size: 26649
[13:48:22] Leaving Run
[13:48:25] - Writing 5689277 bytes of core data to disk...
[13:48:25]   ... Done.
[13:48:25] - Failed to delete work/wudata_05.sas
[13:48:25] - Failed to delete work/wudata_05.goe
[13:48:25] Warning:  check for stray files
[13:48:25] - Shutting down core
[13:50:25] 
[13:50:25] Folding@home Core Shutdown: FINISHED_UNIT
[13:50:25] 
[13:50:25] Folding@home Core Shutdown: FINISHED_UNIT
[13:50:31] CoreStatus = 64 (100)
[13:50:31] Sending work to server


[13:50:31] + Attempting to send results
[13:51:54] + Results successfully sent
[13:51:54] Thank you for your contribution to Folding@Home.
[13:51:54] + Number of Units Completed: 23

[13:53:58] - Preparing to get new work unit...
[13:53:58] + Attempting to get work packet
[13:53:58] - Connecting to assignment server
[13:53:59] - Successful: assigned to (171.64.65.64).
[13:53:59] + News From Folding@Home: Welcome to Folding@Home
[13:53:59] Loaded queue successfully.
[13:54:11] + Closed connections
[13:54:11] 
[13:54:11] + Processing work unit
[13:54:11] Core required: FahCore_a1.exe
[13:54:11] Core found.
[13:54:11] Working on Unit 06 [June 15 13:54:11]
[13:54:11] + Working ...
[13:54:11] 
[13:54:11] *------------------------------*
[13:54:11] Folding@Home Gromacs SMP Core
[13:54:11] Version 1.74 (March 10, 2007)
[13:54:11] 
[13:54:11] Preparing to commence simulation
[13:54:11] - Looking at optimizations...
[13:54:11] - Created dyn
[13:54:11] - Files status OK
[13:54:19] - Expanded 4802269 -> 24810145 (decompressed 516.6 percent)
[13:54:19] - Starting from initial work packet
[13:54:19] 
[13:54:19] Project: 2665 (Run 2, Clone 843, Gen 13)
[13:54:19] 
[13:54:21] Assembly optimizations on if available.
[13:54:21] Entering M.D.
[13:54:43]  percent)
[13:54:44] - Starting from initial work packet
[13:54:44] 
[13:54:44] Project: 2665 (Run 2, Clone 843, Gen 13)
[13:54:44] 
[13:54:49] Entering M.D.
[13:54:55] Rejecting checkpoint
[13:54:58] Protein: HGG with glycosylations
[13:54:58] Writing local files
[13:55:10] Extra SSE boost OK.
[13:55:11] Writing local files
[13:55:11] Completed 0 out of 250000 steps  (0 percent)
[14:20:34] Writing local files
[14:20:34] Completed 2500 out of 250000 steps  (1 percent)
[14:46:16] Writing local files
[14:46:16] Completed 5000 out of 250000 steps  (2 percent)
I am going to finish the unit on this computer with the -oneunit flag first unless you inform me otherwise.


Snipped and added code tags, as suggested. -7im

Re: -oneunit flag

Posted: Tue Jun 17, 2008 4:36 am
by anandhanju
Phred15 wrote:I'm sorry about the lack of information.. I've been folding for 10 years and I get frustrated when I can't figure things out. Here are two of the logs. The -one unit flag is not even recognized at the finish of the work unit. Maybe it should be the first flag. I did not write in the .exe.

Launch directory: C:\FAH
Executable: C:\FAH\fah -verbosity 9 -oneunit.exe...
That strikes me as incorrect. Flags are specified AFTER the full executable name. For example;

Code: Select all

C:\FAH\fah.exe -verbosity 9 -oneunit
if fah.exe is the name of the client exectuable in the FAH directory. Can you try this? Or has the name been inadvertantly changed to include the flags in it?

Johnny B. Goode, be good.

PS. Use the code button while posting log files, it makes things easy on the eye :wink:

Re: -oneunit flag

Posted: Tue Jun 17, 2008 4:37 am
by ChelseaOilman
Phred15 wrote:I did not write in the .exe.

Executable: C:\FAH\fah -verbosity 9 -oneunit.exe
I would double check your shortcut. The .exe should be there, it's just in the wrong place.

The line in the log should read: Executable: C:\FAH\fah.exe -verbosity 9 -oneunit

On my WinXP machine those lines print out in the log like this:
Launch directory: C:\Program Files\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files\Folding@Home Windows SMP Client V1.01\fah.exe
Arguments: -forceasm -verbosity 9

Re: -oneunit flag

Posted: Tue Jun 17, 2008 4:56 am
by bruce
ChelseaOilman wrote:
Phred15 wrote:I did not write in the .exe.

Executable: C:\FAH\fah -verbosity 9 -oneunit.exe
I would double check your shortcut. The .exe should be there, it's just in the wrong place.

The line in the log should read: Executable: C:\FAH\fah.exe -verbosity 9 -oneunit

On my WinXP machine those lines print out in the log like this:
Launch directory: C:\Program Files\Folding@Home Windows SMP Client V1.01
Executable: C:\Program Files\Folding@Home Windows SMP Client V1.01\fah.exe
Arguments: -forceasm -verbosity 9
The exe has been renamed so that it just looks like the flags are present. The full name of the program is now fah -verbosity 9 -oneunit.exe and no flags are being used.

Rename fah -verbosity 9 -oneunit.exe to be fah.exe like it probably was originally and then change the Target field in the shortcut to say C:\FAH\fah.exe -verbosity 9 -oneunit where the green parameter string follows the full name of the (blue) executable program.

Re: -oneunit flag

Posted: Tue Jun 17, 2008 5:24 am
by 7im
Snipped and added code tags, as suggested. -7im

Re: -oneunit flag

Posted: Wed Jun 18, 2008 2:42 am
by Phred15
I'm sorry but I don't understand code button.

How do I go about renaming or adding arguments. I thought I just had to bring up the properties window and add the flags. This is when the ,exe gets in the wrong place. I tried renaming it and end up with fah.exe -oneunit -verbosity 9.exe when I execute the command.

Re: -oneunit flag

Posted: Wed Jun 18, 2008 2:56 am
by anandhanju
Ah, I see what you're doing. You need to create a shortcut first before changing the properties. Here are the steps:

1. Stop the client.
2. Rename your fah<something>.exe back to fah.exe. You can use the proprty window for this.
3. Once done, the icon will read fah.exe or fah.
4. Right click on this and click Create Shortcut.
5. Right click on the shortcut ("Shortcut to fah") and in the Shortcut tab (default), there is a box that says Target which will read "C:\FAH\fah.exe". Just add the oneunit and other flags at the end, after the closing quote. E.g.,

Code: Select all

"C:\FAH\fah.exe" -oneunit -verbosity 9
6. Use the shortcut to start the client.

If all went well, this is what you should see in the log:
Launch directory: C:\FAH
Executable: C:\FAH\fah.exe
Arguments: -oneunit -verbosity 9
Hope this helps.

Re: -oneunit flag

Posted: Wed Jun 18, 2008 3:06 am
by bruce
anandhanju wrote:Ah, I see what you're doing. You need to create a shortcut first before changing the properties. Here are the steps:. . .
Hope this helps.
These steps are an excellent answer for the V5 client that is being discussed in this thread.

To anyone who may be reading this who has a V6 systray client, the steps will be somewhat different, so do not assume you can use them directly.

Re: -oneunit flag

Posted: Wed Jun 18, 2008 12:42 pm
by Phred15
Thank you. I wil fire up the other computers and see if I can finish the other work units on time