Purpose Of This Listing:
There are a lot of reports of Project 6013 WUs giving problems, the most common is that some WUs can't be completed within the deadline. To deal with these BAD WUs, PG recommends: (Only for this Project)
If you are doing this, please report it in this thread (more details below). In order to see a larger picture of this Project, which would help us all. The commonly used method for "delete and move on" is:kasson wrote:It's hard to say what's making the WU slow (bad WU vs. unusual interesting WU). But if it won't make the deadline on a machine that usually finishes that project with time to spare, delete and move on.
Step 1: Stop the Client using Crtl+C.
Step 2: Locate the folder where the SMP2 Client is installed.
Step 3: Select the Work Folder, Queue.dat File and delete them both.
Step 4: Start the Client and hopefully, you will be assigned a new WU.
I have made this listing which will be split in four parts:
1) Good WUs - WUs finished before the deadline and donor received (Bonus) credits.
2) Bad WUs - WUs that can't be processed before the deadline hence the donor dumped it.
3) Inconsistent WUs - WUs in this list have been reported to behave in different manner on different systems. (Note that the name is a misnomer as the problem may be with the system rather than the WU. If you can think of a more appropriate name, please tell me and I will change it.)
4) Reported WUs - WUs reported here have too little data available to be classified yet. (An Admin/Mod can tell me if they are marked as bad or have been completed)
IMPORTANT: You should NOT just delete any P 6013 WUs. That would be classified as cherry-picking and would only harm the project and will cause problems for you. You can ONLY delete WUs that meet Dr.Kasson's criteria as stated above.
Good WUs:
Below is the list of WUs (RCG only) belonging to Project 6013. (More details below)
Code: Select all
Run 0 Clone 000 Gen 154
Run 0 Clone 000 Gen 182
Run 0 Clone 001 Gen 154
Run 0 Clone 004 Gen 161
Run 0 Clone 007 Gen 142
Run 0 Clone 009 Gen 108
Run 0 Clone 009 Gen 109
Run 0 Clone 010 Gen 086
Run 0 Clone 010 Gen 108
Run 0 Clone 011 Gen 167
Run 0 Clone 011 Gen 231
Run 0 Clone 012 Gen 076
Run 0 Clone 015 Gen 070
Run 0 Clone 016 Gen 074
Run 0 Clone 017 Gen 068
Run 0 Clone 018 Gen 063
Run 0 Clone 019 Gen 260
Run 0 Clone 020 Gen 033
Run 0 Clone 020 Gen 041
Run 0 Clone 020,Gen 037
Run 0 Clone 021 Gen 030
Run 0 Clone 021 Gen 050
Run 0 Clone 022 Gen 038
Run 0 Clone 023 Gen 028
Run 0 Clone 025 Gen 022
Run 0 Clone 026 Gen 011
Run 0 Clone 026 Gen 019
Run 0 Clone 028 Gen 008
Run 0 Clone 030 Gen 005
Run 0 Clone 032 Gen 140
Run 0 Clone 034 Gen 002
Run 0 Clone 035 Gen 187
Run 0 Clone 036 Gen 018
Run 0 Clone 038 Gen 136
Run 0 Clone 044 Gen 009
Run 0 Clone 056 Gen 114
Run 0 Clone 067 Gen 159
Run 0 Clone 076 Gen 004
Run 0 Clone 084 Gen 184
Run 0 Clone 102 Gen 181
Run 0 Clone 109 Gen 016
Run 0 Clone 111 Gen 045
Run 0 Clone 111 Gen 124
Run 0 Clone 114 Gen 035
Run 0 Clone 118 Gen 105
Run 0 Clone 121 Gen 075
Run 0 Clone 123 Gen 036
Run 0 Clone 130 Gen 045
Run 0 Clone 131 Gen 099
Run 0 Clone 140 Gen 145
Run 0 Clone 142 Gen 087
Run 0 Clone 160 Gen 020
Run 0 Clone 163 Gen 095
Run 0 Clone 169 Gen 112
Run 0 Clone 186 Gen 006
Run 0 Clone 193 Gen 007
BAD WUs:
Below is the list of WUs (RCG only) belonging to Project 6013. There may be duplicate entries which would indicate that more than one donor tried to complete it but failed. (More details below) They meet Dr.Kasson's criteria as stated above.
Code: Select all
Run 0 Clone 027 Gen 136
Run 0 Clone 053 Gen 157
Run 0 Clone 056 Gen 136
Run 0 Clone 073 Gen 125
Run 0 Clone 095 Gen 085
Run 0 Clone 095 Gen 085
Run 0 Clone 142 Gen 121
Run 0 Clone 160 Gen 098
Run 0 Clone 160 Gen 098
Run 0 Clone 171 Gen 060
Run 0 Clone 171 Gen 060
Inconsistent WUs:
Below is the list of WUs (RCG only) belonging to Project 6013. There may be duplicate entries which would indicate that more than one donor tried to complete it but one was successful while the other gave error.. (More details below)
Code: Select all
Run 0 Clone 050 Gen 140
Run 0 Clone 050 Gen 140
Reported WUs:
Below is the list of WUs (RCG only) belonging to Project 6013 that have been reported but lack enough data be be classified in any category.
Code: Select all
Run 0 Clone 095 Gen 085
Run 0 Clone 188 Gen 121
Run 0 Clone 095 Gen 085
Data Collection Method:
If you are reporting the P 6013 WUs, there are some fields that must be included, while others are recommended.
Mandatory Fields:
Run/Clone/Gen
CPU
RAM
OS
Recommended Fields: (If you can think of other data points that might be useful in finding a pattern, please mention it and I will try to add it.)
FahCore Version
TPF
Other Clients
Dedicated
-smp X
Notes:
1) By default I will be mentioning the User because: (Please tell me if you don't want your username to appear in the details)
A) The User can verify if I have entered the data correctly. If not, they can tell me and I can make the appropriate corrections. (More details below)
B) If more information is required by PG/Admin/Mod, they can contact that user directly.
C) If a user wants to update his fields with more accurate information, they can do so. (More details below)
2) If a user is having lot of systems and can't accurately associate the hardware to the corresponding PRCG, then I can make a link to their profile/post (which ever contains all the Mandatory Fields)
3) If you have been using HFM.NET for monitoring, then go to Help -> View HFM.NET Data Files -> (Folder Opens) -> Click "CompletedUnits" (it's a Microsoft Office Excel Comma Separated Values File (.csv)) you can go through the file and select only the P 6013 WUs.
4) If you have Office 2007 (Haven't checked this method with 2000, 2003, or 2010. If somebody can check it and report any differences, I will add it), then select the entire table (Ctrl+A) -> Format as Table (In the Home tab) -> Click OK (Make sure that the box "My table has headers" is Checked) -> Click drop-down box in ProjectID (Small arrow pointing down) -> Uncheck "Select All" (All boxes will be will become blank) -> Scroll till you find 6013 -> Check only that box -> Click OK. You will then have the necessary information displayed to report here. (Don't save the changes to the original file!)
Data Files & Usage:
All the other data fields which the user reported above has be entered in an Excel File (.xlsx) which I will be updating on regular basis. A download link has been provided below so that users can download it and view more information. In order to maintain data security, I have locked the worksheets from any modification (Only a PG/Admin/Mod can request for the password). Users will only be allowed to use the filters to manipulate the view. This is because I believe that in order to find a pattern, one needs to have large data set that can be easily manipulated to identify a possible pattern. I have extrapolated data from the already provided ones to create two or more fields that will provide a fine control when selecting what information to view.
Available Data Fields:
Project 6013 Run X, Clone X, Gen X - This will be sorted from A -> Z (See User Suggestions Below)
CPU Vendor - Extrapolated from CPU.
CPU Model CPU Speed (GHz) - Extrapolated from CPU.
Cores / Threads - Extrapolated from CPU.
RAM Type - Extrapolated from RAM.
RAM Speed (MHz) - Extrapolated from RAM.
OS - Extrapolated from OS.
32/64 bit - Extrapolated from OS.
Core Version - The version of the a3 Core that processed the WU. If you manually forced the Core to upgrade while it was processing the Same WU, include them both.
TPF - How long it took to complete 1%. Will be present if User provides it.
Note - Any special tweaks/testing the User did/finds, e.g. Processed the same WU with two different versions of a3.
Dedicated - Is the system running F@H 24/7 without any other applications running. Yes/No will suffice for now.
SMP X - If you are are not using all the available CPU resources, if you use -smp then I will report the total number of cores as the value.
Other Clients - Are you running any other F@H Clients on the same system? A brief mention will suffice for now, e.g. GPU3 BETA Con @ 1 or GPU2 GUI @ 1 ...
User - Contains the username of the User reporting the WU. If the User declines to do so, all the appropriate usernames will be replaced by User 1, User 2...
Submitting Data:
In order for me to maintain the list in a quick and efficient manner, I have made a data form where all the above mentioned data fields will be available so that the User can easily add all the necessary data and can submit it to me via e-mail (view profile). Do note that it may take some time as some mails may be accidentally classified as Junk Mail. Once I have updated the list with your information, I will mention it in this thread. If you have already submitted it and 48 hours have passed, please tell me. (Hopefully I plan to do it within 12 hours)
Verifying The Reported Data:
As data accuracy is paramount, Users can help me by verifying that I have added their findings correctly. This can be done by viewing the data against your name. You can select your username from the drop-down box (small arrow pointing down) next to the User field and view all records that you submitted. Note that if any mistakes are detected, you can't correct it as it is protected so please tell me what it is along with the Grid Reference, e.g. F22 -> It should be DDR3 not DDR2.
Adding More Data:
If you have already submitted data but later want to make extensive modifications, please give me your Username so that I will be able to send you your records so you can update them. Once you finish, please send it back so that I can update the file. I would appreciate if you followed my formatting style so that it will be easier for me to update the files.
Sorting Data:
All fields stated above can be sorted in one way or another so see if a possible pattern emerges. Users can sort it as they like and if they do find any possible theories please report it here so that I can add it and further research can be done in order to prove/disprove it.
Download Link: (LINK REMOVED. PM ME IF YOU WANT IT. ) {Last Updated @ 26-Jun-10 9:13 AM UTC}
Note that there are four files available to download:
1) Data Submission Form - Contains One worksheet only which is Unlocked {saved as .xlsx}
2) WU Listings For Project 6013 [Good & Bad] Details - Contains Four worksheets which are Locked {saved as .xlsx}
3) ~Data Submission Form - Contains One worksheet only which is Unlocked {saved as .xls}
4) ~WU Listings For Project 6013 (Good & Bad) Details - Contains Four worksheets which are Locked {saved as .xls}
You can't view the files online as they are protected.
If you are using Office 2000/2003 choose .xls
If you are using Office 2007/2010 choose .xlsx
If you are experiencing any formatting problems please inform me so that I can rectify it.
User Suggestions:
1) In order to make the PRCG sorted in A -> Z manner, I will have to change the current format which is used by PG. If I am given permission to do so, then only I will make this change:
Current PRCG Format: Run 0, Clone 1, Gen 8
Proposed PRCG Format: Run 0, Clone 001, Gen 008
The reason is that with the Current PRCG Formatting, the results are: 1, 10, 100, 2, 20, 200, 3, 30, 300 rather then what one would expect: 1, 2, 3, 10, 20, 30, 100, 200, 300. By changing to the new format, I have verified that it will get the required results. [Suggested by Bob8421] {Accepted}
Theories:
Any valid theories are listed here: (If any are invalid, I will mark them rather than deleting so we can have an idea of what we have covered and what isn't)
If you find any errors, please tell me so that I can make the appropriate corrections.
If a member of PG wants more details to be collected in order to troubleshoot this Project, I will do so.
EDIT by Mod: We need to know your RAM, your CPU, and your OS. The version of FahCore would be nice but not as important.