Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 264
Posts: 264   Pages: 27   [ Previous Page | 8 9 10 11 12 13 14 15 16 17 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 79491 times and has 263 replies Next Thread
ca05065
Senior Cruncher
Joined: Dec 4, 2007
Post Count: 328
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

[Dec 16, 2013 8:29:45 AM]   Link   Report threatening or abusive post: please login first  Go to top 
XSmeagolX
Senior Cruncher
Joined: Nov 12, 2009
Post Count: 444
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

2128 World Community Grid 18.12.2013 16:03:44 No tasks are available for Mapping Cancer Markers


Did we finish the project?? ;)

Seems to be a bigger problem...
Same message for CEP2-project...
----------------------------------------
WCG-Team Captain of Team SETI.Germany

(official Partner of World Community Grid)

----------------------------------------
[Edit 1 times, last edit by XSmeagolX at Dec 18, 2013 3:12:23 PM]
[Dec 18, 2013 3:07:44 PM]   Link   Report threatening or abusive post: please login first  Go to top 
breathesgelatin
Advanced Cruncher
Joined: Aug 5, 2006
Post Count: 117
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

Well, I'm still having problems. I'd say about 90% of my MCM tasks are still erroring out. I'm also getting some invalids. I probably should have given up on this project a while ago, but I really wanted to earn at least a silver on it. I'm thinking it may just be some issue with this computer. Oh well. Here's an example error:

<core_client_version>7.2.33</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -529697949 (0xe06d7363)
</message>
<stderr_txt>
Commandline = projects/www.worldcommunitygrid.org/wcgrid_mcm1_7.28_windows_intelx86 -SettingsFile MCM1_0001099_9327.txt -DatabaseFile dataset-17_72_SDG_v1.txt
Settings File
DateOfDesign = 11/07/2013
Designer = PMCC_OCI
WorkOrderID = 1099_9327
DatasetID = 17_72_SDG_v1
NumberOfGenesInStartingSignature = 15
NumberOfGenesInSignatureMin = 10
NumberOfGenesInSignatureMax = 20
GroupVectorValues = {A}{B}{C}{D}{E}{F}
ExplicitStartingGeneSignatures = A B D F
StartingGeneSignatureAlgorithm = randomFixedLengthSearch
SearchAlgorithmNumberToCreate = 1
SearchAlgorithmSequentialStartPosition = 5
RunPermutationAlgorithm = 1
PermutationGroups = A
PermutationGroupsForReplacement = G
PermutationAlgorithm = replaceFromRandomlyToRandomlyGreedy
PermutationsNumIterations = 18776
OptimizationAlgorithmFrequency = 0 0 1
FBeta = 1.5
SimAnnealIMax = 20000
SimAnnealAlpha = 0.9996
NReps = 10
TrainFrac = 0.7
NFolds = 10
VMethod = NFCV
ModelType = SVM
FitnessFn = 0
MinFitness = -1
SvmArgs = "-v 0 -c 0.01 -t 1 -d 3 -r 0"
SvmLearnLimit = 500000
RSeed = 74679327


[10:00:16] Initializing


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7630C41F

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 7.2.4


Dump Timestamp : 01/01/14 10:00:16
Install Directory : C:\Program Files (x86)\BOINC\
Data Directory : C:\ProgramData\BOINC
Project Symstore :
LoadLibraryA( C:\Program Files (x86)\BOINC\\dbghelp.dll ): GetLastError = 126
Loaded Library : dbghelp.dll
LoadLibraryA( C:\Program Files (x86)\BOINC\\symsrv.dll ): GetLastError = 126
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( C:\Program Files (x86)\BOINC\\srcsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
LoadLibraryA( C:\Program Files (x86)\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\ProgramData\BOINC\slots\1;C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org


ModLoad: 0000000001170000 0000000000142000 C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org\wcgrid_mcm1_7.28_windows_intelx86 (-exported- Symbols Loaded)
Linked PDB Filename : c:\projects\wcgridAustinWorkspace\scienceApps\MCM1\Release\wcgrid_mcm1_prod_32.pdb

ModLoad: 00000000770e0000 0000000000180000 C:\Windows\SysWOW64\ntdll.dll (6.1.7601.18247) (-exported- Symbols Loaded)
Linked PDB Filename : wntdll.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000076bd0000 0000000000110000 C:\Windows\syswow64\kernel32.dll (6.1.7601.18229) (-exported- Symbols Loaded)
Linked PDB Filename : wkernel32.pdb
File Version : 6.1.7601.18015 (win7sp1_gdr.121129-1432)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18015

ModLoad: 0000000076300000 0000000000047000 C:\Windows\syswow64\KERNELBASE.dll (6.1.7601.18229) (-exported- Symbols Loaded)
Linked PDB Filename : wkernelbase.pdb
File Version : 6.1.7601.18015 (win7sp1_gdr.121129-1432)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18015

ModLoad: 0000000072be0000 0000000000009000 C:\Windows\system32\VERSION.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : version.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000075060000 00000000000ac000 C:\Windows\syswow64\msvcrt.dll (7.0.7601.17744) (-exported- Symbols Loaded)
Linked PDB Filename : msvcrt.pdb
File Version : 7.0.7601.17744 (win7sp1_gdr.111215-1535)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 7.0.7601.17744

ModLoad: 0000000074f00000 0000000000005000 C:\Windows\syswow64\PSAPI.DLL (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : psapi.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000751a0000 0000000000100000 C:\Windows\syswow64\USER32.dll (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : wuser32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.17514

ModLoad: 0000000075400000 0000000000090000 C:\Windows\syswow64\GDI32.dll (6.1.7601.18275) (-exported- Symbols Loaded)
Linked PDB Filename : wgdi32.pdb
File Version : 6.1.7601.18275 (win7sp1_gdr.131002-1533)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18275

ModLoad: 00000000762f0000 000000000000a000 C:\Windows\syswow64\LPK.dll (6.1.7601.18177) (-exported- Symbols Loaded)
Linked PDB Filename : wlpk.pdb
File Version : 6.1.7601.18177 (win7sp1_gdr.130605-1534)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18177

ModLoad: 0000000076650000 000000000009d000 C:\Windows\syswow64\USP10.dll (1.626.7601.18009) (-exported- Symbols Loaded)
Linked PDB Filename : usp10.pdb
File Version : 1.0626.7601.18009 (win7sp1_gdr.121121-1431)
Company Name : Microsoft Corporation
Product Name : Microsoft(R) Uniscribe Unicode script processor
Product Version : 1.0626.7601.18009

ModLoad: 00000000766f0000 00000000000a0000 C:\Windows\syswow64\ADVAPI32.dll (6.1.7601.18247) (-exported- Symbols Loaded)
Linked PDB Filename : advapi32.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000076630000 0000000000019000 C:\Windows\SysWOW64\sechost.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : sechost.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000074ce0000 00000000000f0000 C:\Windows\syswow64\RPCRT4.dll (6.1.7601.18205) (-exported- Symbols Loaded)
Linked PDB Filename : wrpcrt4.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000074c40000 0000000000060000 C:\Windows\syswow64\SspiCli.dll (6.1.7601.18270) (-exported- Symbols Loaded)
Linked PDB Filename : wsspicli.pdb
File Version : 6.1.7601.18270 (win7sp1_gdr.130924-1532)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18270

ModLoad: 0000000074c30000 000000000000c000 C:\Windows\syswow64\CRYPTBASE.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : cryptbase.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000756a0000 0000000000c4a000 C:\Windows\syswow64\SHELL32.dll (6.1.7601.18222) (-exported- Symbols Loaded)
Linked PDB Filename : shell32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.17514

ModLoad: 0000000076350000 0000000000057000 C:\Windows\syswow64\SHLWAPI.dll (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : shlwapi.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000765b0000 0000000000060000 C:\Windows\system32\IMM32.DLL (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : wimm32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.17514

ModLoad: 0000000074f10000 00000000000cc000 C:\Windows\syswow64\MSCTF.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : msctf.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000736a0000 0000000000021000 C:\Windows\system32\ntmarta.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : ntmarta.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000755c0000 0000000000045000 C:\Windows\syswow64\WLDAP32.dll (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : wldap32.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000740a0000 00000000000eb000 C:\Windows\system32\dbghelp.dll (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : dbghelp.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.17514



*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 0, Write: 0, Other 0

- I/O Transfers Counters -
Read: 0, Write: 0, Other 0

- Paged Pool Usage -
QuotaPagedPoolUsage: 0, QuotaPeakPagedPoolUsage: 0
QuotaNonPagedPoolUsage: 0, QuotaPeakNonPagedPoolUsage: 0

- Virtual Memory Usage -
VirtualSize: 0, PeakVirtualSize: 0

- Pagefile Usage -
PagefileUsage: 0, PeakPagefileUsage: 0

- Working Set Size -
WorkingSetSize: 0, PeakWorkingSetSize: 0, PageFaultCount: 0

*** Dump of thread ID 1624 (state: Initialized): ***

- Information -
Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7630C41F

- Registers -
eax=0031f7a4 ebx=0000021c ecx=00000003 edx=00000000 esi=0031f900 edi=0000021c
eip=7630c41f esp=0031f7a4 ebp=0031f7f4
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000212

- Callstack -
ChildEBP RetAddr Args to Child
0031f7f4 011f3b0f e06d7363 00000001 00000003 0031f820 KERNELBASE!RaiseException+0x0
0031f82c 011a1e34 0031f98c 0125f65c 6c11236a 0000000f wcgrid_mcm1_7!DeleteMulticlassModel+0x0
0031f830 0031f98c 0125f65c 6c11236a 0000000f 00a383a9 wcgrid_mcm1_7!boost::archive::detail::iserializer<boost::archive::binary_iarchive,std::vector<bool,std::allocator<bool> > >::load_object_data+0x0
0031f834 0125f65c 6c11236a 0000000f 00a383a9 008deb20 wcgrid_mcm1_7!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '0031f98c'
0031fa18 011711e2 00a38d38 028b0888 32375f37 4744535f wcgrid_mcm1_7!boost::serialization::singleton<boost::archive::detail::`anonymous namespace'::map<boost::archive::binary_oarchive> >::get_mutable_instance+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '0125f65c'
0031faa0 0118ea74 00a38d38 6c11219a 008deb20 008deb80 wcgrid_mcm1_7!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '011711e2'
0031fad8 0119c618 00000000 0000000f 008ddff0 00000000 wcgrid_mcm1_7!boost::archive::detail::iserializer<boost::archive::binary_iarchive,std::vector<bool,std::allocator<bool> > >::load_object_data+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '0118ea74'
0031fb98 011f1bc7 00a30000 00000000 00000018 0000001f wcgrid_mcm1_7!boost::archive::detail::iserializer<boost::archive::binary_iarchive,std::vector<bool,std::allocator<bool> > >::load_object_data+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '0119c618'
0031fbc8 0123ff82 00000007 0118e6fe 008deb20 6c1120ca wcgrid_mcm1_7!DeleteMulticlassModel+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '011f1bc7'
0031fc58 01240031 00000007 011a93ce 0000000f 00a38380 wcgrid_mcm1_7!boost::serialization::singleton<boost::archive::detail::`anonymous namespace'::map<boost::archive::binary_oarchive> >::get_mutable_instance+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '0123ff82'
0031fec0 011f0e8f 011f0ea3 01241c70 0031fee4 012410aa wcgrid_mcm1_7!boost::serialization::singleton<boost::archive::detail::`anonymous namespace'::map<boost::archive::binary_oarchive> >::get_mutable_instance+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '01240031'
0031ff30 76be336a 7efde000 0031ff7c 77119f72 7efde000 wcgrid_mcm1_7!DeleteMulticlassModel+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '011f0e8f'
0031ff7c 77119f45 011f20e7 7efde000 00000000 00000000 kernel32!BaseThreadInitThunk+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '76be336a'
0031ff80 011f20e7 7efde000 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '77119f45'
0031ff84 7efde000 00000000 00000000 00000000 00000000 wcgrid_mcm1_7!DeleteMulticlassModel+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '011f20e7'
0031ff88 00000000 00000000 00000000 00000000 011f20e7 wcgrid_mcm1_7!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '7efde000'

*** Dump of thread ID 3408 (state: Initialized): ***

- Information -
Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000

- Registers -
eax=011e5ed0 ebx=00000000 ecx=00000000 edx=00000000 esi=0283fc74 edi=00000000
eip=770ffd91 esp=0283fc30 ebp=0283fc98
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
0283fc98 76314498 00000064 00000000 0283fcb4 011e5ee4 ntdll!ZwDelayExecution+0x0
0283fca8 011e5ee4 00000064 0283fcc0 76be336a 00000000 KERNELBASE!Sleep+0x0
0283fcb4 76be336a 00000000 0283fd00 77119f72 00000000 wcgrid_mcm1_7!DeleteMulticlassModel+0x0
0283fcc0 77119f72 00000000 70d22d38 00000000 00000000 kernel32!BaseThreadInitThunk+0x0
0283fd00 77119f45 011e5ed0 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
0283fd18 00000000 011e5ed0 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name :
Window Class :
Window Process ID: 0
Window Thread ID : 0

Exiting...

</stderr_txt>
]]>
----------------------------------------

[Jan 1, 2014 5:42:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
breathesgelatin
Advanced Cruncher
Joined: Aug 5, 2006
Post Count: 117
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

I just thought I'd post again to note I am now seeing the return of invalids. Many of them.

I've gone ahead and turned off MCM for the moment... it really might be some kind of hardware issue I have with this project, I'm not sure. :(
----------------------------------------

[Jan 5, 2014 8:34:39 PM]   Link   Report threatening or abusive post: please login first  Go to top 
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

I just thought I'd post again to note I am now seeing the return of invalids. Many of them.

I've gone ahead and turned off MCM for the moment... it really might be some kind of hardware issue I have with this project, I'm not sure. :(

I am not experiencing that. I'll keep checking.

Cheers coffee
----------------------------------------

[Jan 7, 2014 2:06:07 AM]   Link   Report threatening or abusive post: please login first  Go to top 
armstrdj
Former World Community Grid Tech
Joined: Oct 21, 2004
Post Count: 695
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

For the invalids are there restarts in the stderr? Also do you overclock your hardware at all. There was a nother user who was having issues with invalids when they run MCM1 on all cores but I believe they said they overclocked.

Thanks,
armstrdj
[Jan 8, 2014 4:47:02 PM]   Link   Report threatening or abusive post: please login first  Go to top 
BobCat13
Senior Cruncher
Joined: Oct 29, 2005
Post Count: 295
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

For the invalids are there restarts in the stderr? Also do you overclock your hardware at all. There was a nother user who was having issues with invalids when they run MCM1 on all cores but I believe they said they overclocked.

Thanks,
armstrdj

That user is most likely me. The machine is a Q6600 (stock 2.4 GHz) running at 3.2 GHz. I created an app_config.xml that limits MCM1 to 3 concurrent tasks and let the 4th core run any other project and it won't have invalids. Strange thing is that if the 4th core is idle, the machine still gets an invalid every once in a while, but as long as the 4th core runs anything other than MCM1 there are no invalids.
[Jan 8, 2014 7:31:31 PM]   Link   Report threatening or abusive post: please login first  Go to top 
RTS48
Veteran Cruncher
Bolivia
Joined: Aug 2, 2009
Post Count: 1353
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

I have a problem with the projected timings of the WUs. It seems that they can take anything from 4 hours to 17 hours regardless of their projected time. For instance my projected time per WU is 6h 26m. I have 4 WUs on the go (MAC Book Pro Dual Core i7 2.8 GHz) showing the following completion %, time elapsed and time to completion
65.6%, 7h 34m, 1h 42m
60.2%, 6h 54m, 1h 39m
58.6%, 6h 41m, 1h 37m
54.1%, 6h 15m, 1h 41m

The problem is that Boinc calculates the number of WUs it needs to match my buffer and then overloads the buffer which results in high priority running and potentially late submission. I have been forced to abort WUs that clearly will not meet the deadline.

Can anyone throw any light on this?
----------------------------------------
Rod Peel
Santa Cruz
Bolivia
South America

,
,
----------------------------------------
[Edit 1 times, last edit by RTS48 at Jan 14, 2014 11:42:36 PM]
[Jan 14, 2014 11:40:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7846
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

I have a problem with the projected timings of the WUs. It seems that they can take anything from 4 hours to 17 hours regardless of their projected time. For instance my projected time per WU is 6h 26m. I have 4 WUs on the go (MAC Book Pro Dual Core i7 2.8 GHz) showing the following completion %, time elapsed and time to completion
65.6%, 7h 34m, 1h 42m
60.2%, 6h 54m, 1h 39m
58.6%, 6h 41m, 1h 37m
54.1%, 6h 15m, 1h 41m

The problem is that Boinc calculates the number of WUs it needs to match my buffer and then overloads the buffer which results in high priority running and potentially late submission. I have been forced to abort WUs that clearly will not meet the deadline.

Can anyone throw any light on this?

The MCM1 WU's are highly variable, it seems, at least to me, by batch. Sometimes BOINC will have an initial estimated time, but the WU does not match the estimate closely - either too short or too long and it takes a while for BOINC to adjust. Just about the time it may stabilize, some more units come along which do not match the duration of the previous ones and the time estimates get thrown out of whack again. If you do not wish to get overloaded with too many WU's try lowering your cache. The supply seems very dependable. I have my cache settings on 1.5 days and I have never run short, nor not been able to complete units on time (barring a machine malfunction.) I have posted a chart of the variable times at https://secure.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=445854. Hope this helps.
Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
[Jan 15, 2014 12:04:13 AM]   Link   Report threatening or abusive post: please login first  Go to top 
RTS48
Veteran Cruncher
Bolivia
Joined: Aug 2, 2009
Post Count: 1353
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Mapping Cancer Markers - Problems Thread

Thanks Sgt. Joe

Very helpful
----------------------------------------
Rod Peel
Santa Cruz
Bolivia
South America

,
,
[Jan 15, 2014 1:26:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 264   Pages: 27   [ Previous Page | 8 9 10 11 12 13 14 15 16 17 | Next Page ]
[ Jump to Last Post ]
Post new Thread