Message boards : News : longer DNA@home workunits
Author | Message |
---|---|
I've created a new set of work units from DNA@Home using a new data file (from human genome revision 19 -- hg19). These should run a bit longer than the other work units, so please let me know if the time estimates and credit is okay. They're actually not as long as I'd like them to be, so depending on how things are working work units after this could be 10x longer. | |
ID: 3258 · Rating: 0 · rate:
![]() ![]() ![]() | |
Estimated run time on my computers is 10 to 14 minutes, so I will see how they run. | |
ID: 3259 · Rating: 0 · rate:
![]() ![]() ![]() | |
Estimated run time on my computers is 10 to 14 minutes, so I will see how they run. Okay that's not too bad, if it's accurate than I can make them 10x longer without much of a problem. Didn't want these to run too long because I wanted to make sure they wouldn't crash and validate correctly. | |
ID: 3260 · Rating: 0 · rate:
![]() ![]() ![]() | |
On my fastest system they are estimated at 10 minutes or so. So far one has completed and it was done in 93 seconds cpu time. The next one is at 50% complete with about 43 minutes of cpu time. Quite a difference. So, right now the estimate is 90 minutes or so for this one. Not sure why it's taking so much longer. This is a 4 core system running Linux. There are three other tasks running and they appear to be in line with the one that's half done. Time will tell. | |
ID: 3261 · Rating: 0 · rate:
![]() ![]() ![]() | |
On my fastest system they are estimated at 10 minutes or so. So far one has completed and it was done in 93 seconds cpu time. The next one is at 50% complete with about 43 minutes of cpu time. Quite a difference. So, right now the estimate is 90 minutes or so for this one. Not sure why it's taking so much longer. This is a 4 core system running Linux. There are three other tasks running and they appear to be in line with the one that's half done. Time will tell. Strange, there's probably an error with the one that took 93 seconds. Was it a test_hg19 work unit or something else? 90 minutes sounds more right for the test_hg19 work units. | |
ID: 3262 · Rating: 0 · rate:
![]() ![]() ![]() | |
A double check of that fast one shows it was a leftover from the last batch of small ones. Must have been stuck. It was created earlier today. So, the time estimates for the new batch seem to be very low. | |
ID: 3263 · Rating: 0 · rate:
![]() ![]() ![]() | |
They come to me with an "estimated completion" time of 9:25. | |
ID: 3264 · Rating: 0 · rate:
![]() ![]() ![]() | |
Tasks seems to have a validate horror, any validator bug? | |
ID: 3265 · Rating: 0 · rate:
![]() ![]() ![]() | |
What is the check-pointing set at for these??? | |
ID: 3266 · Rating: 0 · rate:
![]() ![]() ![]() | |
What is the check-pointing set at for these??? This will take a whole lot more memory as the input file is quite a bit larger. Let me check out the errors. Checkpointing is done by the number of iterations the application does. Since I set it to do 10000 total iterations and it was previously checkpointing every 5000, 50% looks right. I should probably make it checkpoint more frequently, maybe every 5% or so. | |
ID: 3267 · Rating: 0 · rate:
![]() ![]() ![]() | |
it's also really strange that they're erroring out. From the tasks themselves it looks like they're returning the same results... | |
ID: 3268 · Rating: 0 · rate:
![]() ![]() ![]() | |
Estimated run time on my computers is 10 to 14 minutes, so I will see how they run. They are taking just over an hour (between 3,994 and 4,248 seconds) to actually run. Four so far returned with two pending and two with Validate Errors (along with my wingmen). Conan | |
ID: 3269 · Rating: 0 · rate:
![]() ![]() ![]() | |
it's also really strange that they're erroring out. From the tasks themselves it looks like they're returning the same results...Stderr of invalid task (validate error) doesn't show any error, it seems to be validator bug. | |
ID: 3272 · Rating: 0 · rate:
![]() ![]() ![]() | |
it's also really strange that they're erroring out. From the tasks themselves it looks like they're returning the same results...Stderr of invalid task (validate error) doesn't show any error, it seems to be validator bug. Actually what's happening is the stderr is too long, so it's cutting off information the validator needs to validate things. | |
ID: 3273 · Rating: 0 · rate:
![]() ![]() ![]() | |
Message boards : News : longer DNA@home workunits