No, it was not a repair job. Repair jobs have an ending of 2 or greater, but should only be issued if one of the first two jobs ( the ones ending in "0" and "1") either errors out, is not completed for any reason, or if they both are in need of further verification, i.e they are both in the status of "pending verification." None of those conditions exist here.

Yes, the longer one is most likely on a slower host.

Cheers

This is still happening and this time with a slightly new twist. Not only is a third WU sent in a short time, but when it is processed, it did so instantly - zero time elapsed. And it is valid. Mine is the aborted WU, which is why I noticed it.


Here is the result log:

Result Log

Result Name: MCM1_ 0020159_ 3350_ 2--
<core_client_version>7.5.0</core_client_version>
<![CDATA[
<stderr_txt>
05:45:44 (1432): Can't set up shared mem: -1. Will run in standalone mode.
Commandline = ../../projects/www.worldcommunitygrid.org/wcgrid_mcm1_7.35_x86_64-pc-linux-gnu -SettingsFile MCM1_0020159_3350.txt -DatabaseFile dataset-17_72_SDG_v1.txt
Settings File
DateOfDesign = 08/05/2014
Designer = PMCC_OCI_0.1
WorkOrderID = 0020159_3350
DatasetID = 17_72_SDG_v1
NumberOfGenesInStartingSignature = 70
NumberOfGenesInSignatureMin = 70
NumberOfGenesInSignatureMax = 70
GroupVectorValues = {A}{B}{C}{D}{E}{F}
ExplicitStartingGeneSignatures = A B D F
StartingGeneSignatureAlgorithm = randomFixedLengthSearch
SearchAlgorithmNumberToCreate = 542
SearchAlgorithmSequentialStartPosition = 5
RunPermutationAlgorithm = 0
PermutationGroups = A
PermutationGroupsForReplacement = G
PermutationAlgorithm = replaceFromRandomlyToRandomlyGreedy
PermutationsNumIterations = 0
OptimizationAlgorithmFrequency = 0 0 1
FBeta = 1.5
SimAnnealIMax = 20000
SimAnnealAlpha = 0.9996
FitnessFn = 0
MinFitness = 0.37
NReps = 10
TrainFrac = 0.7
NFolds = 10
VMethod = LOO
ModelType = SVM
SvmArgs = "-v 0 -c 0.1 -t 1 -d 2 -r 0"

SvmLearnLimit = 500000
RSeed = 157903351


[05:45:44] Initializing
[05:45:54] Running
[05:45:54] EvaluateFitnessOfStartingGeneSignatures 542
08:16:31 (9782): Can't set up shared mem: -1. Will run in standalone mode.
Commandline = ../../projects/www.worldcommunitygrid.org/wcgrid_mcm1_7.35_x86_64-pc-linux-gnu -SettingsFile MCM1_0020159_3350.txt -DatabaseFile dataset-17_72_SDG_v1.txt
[08:16:31] Initializing
[08:16:41] Running
[08:16:41] EvaluateFitnessOfStartingGeneSignatures 542
09:48:01 (2931): Can't set up shared mem: -1. Will run in standalone mode.
Commandline = ../../projects/www.worldcommunitygrid.org/wcgrid_mcm1_7.35_x86_64-pc-linux-gnu -SettingsFile MCM1_0020159_3350.txt -DatabaseFile dataset-17_72_SDG_v1.txt
[09:48:01] Initializing
[09:48:14] Running
[09:48:14] EvaluateFitnessOfStartingGeneSignatures 542
[10:13:46] Writing final output
[10:13:46] Closing Output Stream
[10:13:46] Cleaning up
Result.out = 34457.000000
Run complete, CPU time: 1529.835608
10:13:47 (2931): called boinc_finish

</stderr_txt>
]]>

Just weird.
Cheers

You may have put your finger on that part of the problem. I had not thought to look at the version number. Still wondering why the third WU sent out though. Thanks for the input.
Cheers