Posts by Thyme Lawn

1) Message boards : News : Re-starting the project! (Message 1424) Posted 1 Apr 2018 by Thyme Lawn Post: My i7 just completed its first Test_2-Pueyo_APDR task (the type that failed in test 1 due to the _0 upload file being too large). The _0 file was 0 bytes and the _1 was 274 KB.
2) Message boards : News : Re-starting the project! (Message 1418) Posted 29 Mar 2018 by Thyme Lawn Post: Thanks Jesús. Yesterday, I uploaded a new version that solves this bug. My i7 has completed 20 Test_2 tasks so far. The _0 upload file sizes were: Zero for most (Drouin_ENDO, Drouin_EPI, CLVPET_Block_Ks, TESZT_Block_K1 and TESZT_Block_Kr) 341.83 KB for BASE_EPI and Coppini 113.96 KB for Schmidt_333 136.75 KB for Schmidt_400 170.93 KB for Schmidt_500 196.57 KB for Schmidt_575 227.91 KB for Schmidt_666 2.67 MB for Schmidt_8000 The _1 upload file size was 224 bytes for everything except CLVPET_Block_Ks (38.59 KB).
3) Message boards : Number crunching : Uploads failing - server disk full (Message 1399) Posted 26 Mar 2018 by Thyme Lawn Post: 26/03/2018 14:28:15 \| DENIS@Home \| Started upload of GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_0 (1.03 MB) 26/03/2018 14:28:15 \| DENIS@Home \| [error] Error reported by file upload server: Server is out of disk space 26/03/2018 14:28:15 \| DENIS@Home \| Temporarily failed upload of GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_0: transient upload error 26/03/2018 14:28:15 \| DENIS@Home \| Backing off 00:10:40 on upload of GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_0 and 26/03/2018 14:36:42 \| DENIS@Home \| Started upload of GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_1 (244 bytes) 26/03/2018 14:36:44 \| DENIS@Home \| [error] Error reported by file upload server: can't write file /home/boincadm/projects/denisathome/upload/1df/GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_1: No space left on server 26/03/2018 14:36:44 \| DENIS@Home \| Temporarily failed upload of GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_1: transient upload error 26/03/2018 14:36:44 \| DENIS@Home \| Backing off 00:05:36 on upload of GD_jcarro_20180321183348000000_Test_1-Drouin_ENDO_6000-conf_506.xml_1_1
4) Message boards : News : Problems in the server (Message 1389) Posted 25 Mar 2018 by Thyme Lawn Post: I'm down 4600 on my single computer. Its average credit rate per task is around 90, so that'll be approximately 50 affected tasks. The task list for my i7 currently says I have 61 tasks pending validation. It's very likely that some of those were validated when the wingman was reported during the missing period, but those tasks should be revalidated when the wingmen time out and repair tasks are issued for the workunits. The task list also shows that 43 tasks are in progress, but there are only 21 running, pending and ready to report tasks on my system. The BoincTasks history tab confirms that the 22 missing tasks were reported (times are UTC, clock synced with uk.pool.ntp.org), with 10 of the workunits having a wingman waiting for validation (3 reported after the missing time period, 7 reported before and now waiting for revalidation with repair task after my tasks time out): 22/03/2018 22:39:36 - GD_jcarro_20180321180458000000_Test_1-Pieske_4000-conf_774.xml_1, elapsed time 02:06:02, CPU time 01:58:35 22/03/2018 22:39:36 - GD_jcarro_20180321180512000000_Test_1-Schmidt_2000-conf_779.xml_1, elapsed time 02:05:40, CPU time 01:58:06 22/03/2018 22:39:36 - GD_jcarro_20180321180512000000_Test_1-TESZT_Block_K1_75-conf_779.xml_0, elapsed time 02:04:00, CPU time 01:59:49 22/03/2018 22:39:36 - GD_jcarro_20180321180515000000_Test_1-Coppini_5000-conf_780.xml_1, elapsed time 02:05:01, CPU time 01:57:42 22/03/2018 22:39:36 - GD_jcarro_20180321180515000000_Test_1-Drouin_EPI_2000-conf_780.xml_0, elapsed time 02:04:36, CPU time 01:57:08 22/03/2018 22:39:36 - GD_jcarro_20180321180515000000_Test_1-Pieske_333-conf_780.xml_1, elapsed time 02:03:49, CPU time 01:59:46 22/03/2018 23:16:50 - GD_jcarro_20180321180518000000_Test_1-CLVPET_Block_K1_75-conf_781.xml_1, elapsed time 02:22:12, CPU time 02:14:48 23/03/2018 00:19:49 - GD_jcarro_20180321180454000000_Test_1-TESZT-conf_776.xml_0, elapsed time 02:04:01, CPU time 01:58:56 23/03/2018 00:19:49 - GD_jcarro_20180321180512000000_Test_1-Pieske_4000-conf_779.xml_0, elapsed time 02:02:09, CPU time 01:59:15 23/03/2018 00:19:49 - GD_jcarro_20180321180512000000_Test_1-Schmidt_750-conf_779.xml_0, elapsed time 02:02:53, CPU time 02:00:25 23/03/2018 00:19:49 - GD_jcarro_20180321180515000000_Test_1-Drouin_ENDO_10000-conf_780.xml_0, elapsed time 02:00:53, CPU time 01:58:04 23/03/2018 00:19:49 - GD_jcarro_20180321180518000000_Test_1-BASE_EPI-conf_781.xml_1, elapsed time 02:03:00, CPU time 01:58:12 23/03/2018 00:19:49 - GD_jcarro_20180321180518000000_Test_1-CLVPET_Block_Kr_70-conf_781.xml_1, elapsed time 02:20:47, CPU time 02:13:26 23/03/2018 01:31:43 - GD_jcarro_20180321180504000000_Test_1-Schmidt_1400-conf_777.xml_1, elapsed time 02:00:55, CPU time 01:58:51 23/03/2018 01:31:43 - GD_jcarro_20180321180519000000_Test_1-Drouin_ENDO_1000-conf_781.xml_1, elapsed time 02:00:47, CPU time 01:58:51 23/03/2018 02:50:46 - GD_jcarro_20180321180458000000_Test_1-Pieske_500-conf_774.xml_1, elapsed time 01:59:15, CPU time 01:58:38 23/03/2018 02:50:46 - GD_jcarro_20180321180508000000_Test_1-Schmidt_575-conf_783.xml_0, elapsed time 02:00:15, CPU time 01:59:27 23/03/2018 02:50:46 - GD_jcarro_20180321180511000000_Test_1-CLVPET_Block_Ks_95-conf_779.xml_1, elapsed time 02:13:22, CPU time 02:12:30 23/03/2018 02:50:46 - GD_jcarro_20180321180512000000_Test_1-Schmidt_500-conf_779.xml_0, elapsed time 02:00:19, CPU time 01:59:31 23/03/2018 02:50:46 - GD_jcarro_20180321180515000000_Test_1-Pieske_500-conf_780.xml_1, elapsed time 01:59:12, CPU time 01:58:21 23/03/2018 02:50:46 - GD_jcarro_20180321180516000000_Test_1-Schmidt_3000-conf_780.xml_0, elapsed time 01:58:04, CPU time 01:57:20 23/03/2018 04:02:47 - GD_jcarro_20180321180518000000_Test_1-CLVPET_Block_Kr_15-conf_781.xml_1, elapsed time 02:13:27, CPU time 02:12:38 Additionally, the following 34 tasks were in a batch of work assigned on 22/03/2018 at 23:16:09 which doesn't appear in the task list. They have been reported as follows: 23/03/2018 04:02:47 - GD_jcarro_20180321180825000000_Test_1-Drouin_ENDO_6000-conf_731.xml_1, elapsed time 01:57:17, CPU time 01:56:20 23/03/2018 04:02:47 - GD_jcarro_20180321180829000000_Test_1-Drouin_ENDO_10000-conf_732.xml_1, elapsed time 01:57:56, CPU time 01:57:00 23/03/2018 04:02:47 - GD_jcarro_20180321180825000000_Test_1-Drouin_EPI_1000-conf_731.xml_0, elapsed time 01:58:40, CPU time 01:58:07 23/03/2018 04:02:47 - GD_jcarro_20180321180826000000_Test_1-Schmidt_2000-conf_731.xml_1, elapsed time 01:58:31, CPU time 01:57:33 23/03/2018 04:02:47 - GD_jcarro_20180321180826000000_Test_1-Schmidt_8000-conf_731.xml_0, elapsed time 01:58:02, CPU time 01:57:30 23/03/2018 05:26:50 - GD_jcarro_20180321180826000000_Test_1-Schmidt_750-conf_731.xml_0, elapsed time 01:59:55, CPU time 01:59:28 23/03/2018 05:26:50 - GD_jcarro_20180321180826000000_Test_1-TESZT-conf_731.xml_1, elapsed time 01:58:39, CPU time 01:57:54 23/03/2018 06:43:56 - GD_jcarro_20180321180828000000_Test_1-BASE_ENDO-conf_732.xml_0, elapsed time 01:59:19, CPU time 01:58:48 23/03/2018 07:46:56 - GD_jcarro_20180321180828000000_Test_1-BASE_EPI-conf_732.xml_0, elapsed time 01:59:11, CPU time 01:58:50 23/03/2018 06:43:56 - GD_jcarro_20180321180825000000_Test_1-Coppini_5000-conf_731.xml_1, elapsed time 01:57:40, CPU time 01:57:13 23/03/2018 06:43:56 - GD_jcarro_20180321180829000000_Test_1-Coppini_5000-conf_732.xml_1, elapsed time 01:58:47, CPU time 01:58:17 23/03/2018 06:43:56 - GD_jcarro_20180321180829000000_Test_1-Drouin_ENDO_3000-conf_732.xml_0, elapsed time 01:58:10, CPU time 01:57:41 23/03/2018 06:43:56 - GD_jcarro_20180321180825000000_Test_1-Drouin_ENDO_5000-conf_731.xml_0, elapsed time 01:56:01, CPU time 01:55:42 23/03/2018 06:43:56 - GD_jcarro_20180321180825000000_Test_1-Drouin_EPI_4000-conf_731.xml_1, elapsed time 01:55:55, CPU time 01:55:34 23/03/2018 07:46:56 - GD_jcarro_20180321180826000000_Test_1-Schmidt_1000-conf_731.xml_0, elapsed time 01:59:27, CPU time 01:58:57 23/03/2018 07:46:56 - GD_jcarro_20180321180822000000_Test_1-TESZT_Block_Kr_15-conf_735.xml_1, elapsed time 01:58:39, CPU time 01:58:17 23/03/2018 08:52:59 - GD_jcarro_20180321180825000000_Test_1-Drouin_ENDO_3000-conf_731.xml_1, elapsed time 01:57:53, CPU time 01:56:57 23/03/2018 08:52:59 - GD_jcarro_20180321180825000000_Test_1-Drouin_ENDO_10000-conf_731.xml_0, elapsed time 01:57:51, CPU time 01:56:54 23/03/2018 08:52:59 - GD_jcarro_20180321180825000000_Test_1-Drouin_EPI_6000-conf_731.xml_1, elapsed time 01:57:53, CPU time 01:56:58 23/03/2018 08:52:59 - GD_jcarro_20180321180825000000_Test_1-Drouin_EPI_10000-conf_731.xml_1, elapsed time 01:57:39, CPU time 01:56:43 23/03/2018 08:52:59 - GD_jcarro_20180321180826000000_Test_1-Schmidt_1400-conf_731.xml_1, elapsed time 01:57:53, CPU time 01:57:23 23/03/2018 10:39:01 - GD_jcarro_20180321180829000000_Test_1-Drouin_ENDO_2000-conf_732.xml_1, elapsed time 01:58:31, CPU time 01:57:03 23/03/2018 10:39:01 - GD_jcarro_20180321180825000000_Test_1-Drouin_ENDO_4000-conf_731.xml_1, elapsed time 01:57:08, CPU time 01:56:20 23/03/2018 10:39:01 - GD_jcarro_20180321180825000000_Test_1-Drouin_EPI_2000-conf_731.xml_0, elapsed time 01:57:07, CPU time 01:56:25 23/03/2018 10:39:01 - GD_jcarro_20180321180826000000_Test_1-Pieske_500-conf_731.xml_1, elapsed time 01:59:08, CPU time 01:58:16 23/03/2018 10:39:01 - GD_jcarro_20180321180826000000_Test_1-Schmidt_500-conf_731.xml_1, elapsed time 02:00:10, CPU time 01:59:23 23/03/2018 10:39:01 - GD_jcarro_20180321180822000000_Test_1-TESZT_Block_K1_75-conf_735.xml_0, elapsed time 01:59:47, CPU time 01:58:59 23/03/2018 12:14:05 - GD_jcarro_20180321180821000000_Test_1-CLVPET_Block_Ks_95-conf_735.xml_0, elapsed time 02:14:21, CPU time 02:12:03 23/03/2018 13:20:11 - GD_jcarro_20180321180829000000_Test_1-Drouin_ENDO_1000-conf_732.xml_1, elapsed time 02:01:34, CPU time 01:57:31 23/03/2018 13:20:11 - GD_jcarro_20180321180822000000_Test_1-TESZT_Block_Kr_70-conf_735.xml_0, elapsed time 02:00:22, CPU time 01:57:16 23/03/2018 18:28:17 - GD_jcarro_20180321180828000000_Test_1-CLVPET_Block_Kr_70-conf_732.xml_0, elapsed time 02:19:48, CPU time 02:11:45 23/03/2018 18:28:17 - GD_jcarro_20180321180821000000_Test_1-Drouin_ENDO_5000-conf_735.xml_0, elapsed time 02:01:43, CPU time 01:56:44 23/03/2018 18:28:17 - GD_jcarro_20180321180825000000_Test_1-Drouin_EPI_5000-conf_731.xml_1, elapsed time 01:58:21, CPU time 01:55:38 23/03/2018 18:28:17 - GD_jcarro_20180321180822000000_Test_1-Schmidt_1000-conf_735.xml_1, elapsed time 02:04:51, CPU time 01:58:08 In summary, I have: 34 tasks which aren't in the restored database and can never be credited. Some of them may have been validated during the missing time period. 7 tasks which definitely went through the validation process during the missing time period. These won't now be credited. The wingmen should be revalidated when the workunit issues repair tasks after these tasks time out. 15 other tasks which were completed during the missing time period. Up to 12 of them could have been validated, but none of them will now be credited. An unknown number of tasks (possibly >40) which were validated during the missing time period. These should be revalidated when the wingman times out and repair tasks are issued for the workunits.
5) Message boards : News : Re-starting the project! (Message 1372) Posted 22 Mar 2018 by Thyme Lawn Post: I don't get any tasks at all; neither on my Windows nor on my Linux machines. My Windows XP 32 bit computer fails all tasks, so have stopped that computer. However my Linux 64 bit computers have no problems with the tasks. If you are not getting any tasks, check your settings in both your account here at the project and BOINC Manager to see if there could be a problem, also your anti-virus might be the problem. Conan In particular, check that test applications are allowed in project preferences (the only current application is "Beta version of the DENIS Myocyte software for validation").
6) Message boards : News : Re-starting the project! (Message 1369) Posted 22 Mar 2018 by Thyme Lawn Post: My i7's pending Pueyo_APDR task has been cancelled on the server side. The 61.9MB _0 file for a CLVPET_Block_Kr_15 task is currently being uploaded. It hasn't been compressed, and the size drops to 8.5MB when it is.
7) Message boards : News : Re-starting the project! (Message 1367) Posted 22 Mar 2018 by Thyme Lawn Post: Further to Conan's post and my own, the BOINC event log contains the following when the task failed: 22-Mar-2018 04:10:46 [DENIS@Home] Output file GD_jcarro_20180321164525000000_Test_1-Pueyo_APDR-conf_952.xml_0_0 for task GD_jcarro_20180321164525000000_Test_1-Pueyo_APDR-conf_952.xml_0 exceeds size limit. 22-Mar-2018 04:10:46 [DENIS@Home] File size: 216000018.000000 bytes. Limit: 200000000.000000 bytes File sizes are dependent on the task type, for example: A CLVPET_Block_Ks_95 task had a 61.97 MB _0 file (_1 was 38.42 KB) Drouin_ENDO tasks had 351.58 KB _0 files (_1 were 244 bytes) Drouin_EPI tasks had 1.03 MB _0 files (_1 were 244 bytes) Pieske_333 tasks had 113.96 KB _0 files (_1 were 244 bytes) Pieske_4000 tasks had 1.34 MB _0 files (_1 were 244 bytes) (I use a self-compiled BOINC client which adds the file size to "Started upload" messages)
8) Message boards : News : Re-starting the project! (Message 1364) Posted 22 Mar 2018 by Thyme Lawn Post: Mostly working fine on my i7 Win10 Pro system, which has 17 successful tasks and 8 pending validation (another successful completion waiting to report, 8 in progress and 27 pending). The single failure was GD_jcarro_20180321164525000000_Test_1-Pueyo_APDR-conf_952.xml_0 (failed because the _0 output file was larger than the 200 million bytes allowed by the max_nbytes value in the workunit template). The stderr message for that task ended with: <message> upload failure: <file_xfer_error> <file_name>GD_jcarro_20180321164525000000_Test_1-Pueyo_APDR-conf_952.xml_0_0</file_name> <error_code>-131 (file size too big)</error_code> </file_xfer_error> </message> The failed task has been the only one where the name contains "Pueyo_APDR" (one of the pending tasks has that name format).
9) Message boards : Number crunching : DENIS_BETA v1.03 & v1.04 tasks finished (pending validation) and no credit given? (Message 1040) Posted 30 Jul 2016 by Thyme Lawn Post: I have 34 beta tasks to be validated and a number of them have 2 completed tasks in the workunit, including: BETA_23071039_8000_0704 since 25 Jul 2016, 11:46:14 UTC BETA_23071039_8000_0813 since 28 Jul 2016, 10:02:00 UTC BETA_23071039_8000_2172 since 30 Jul 2016, 9:29:39 UTC According to the Project Status page there are no validator, assimilator or database purge processes running and 106 workunits are waiting for validation.
10) Message boards : Number crunching : DENIS_BETA v1.04 checkpoints are working (Message 1024) Posted 28 Jul 2016 by Thyme Lawn Post: Happy to confirm that checkpoints are working in DENIS_BETA v1.04 on Windows 10. Selected messages from stderr.txt in the slot directory: CONFIG END Checkpoint file not found Doing CP It:111173340 Doing CP It:222792338 Doing CP It:331327699 Doing CP It:431515154 <---- BOINC restart ----> CONFIG END LoadFromCP: it = 431515154 Doing CP It:537907377
11) Message boards : Number crunching : Too short deadlines! Cancel? (Message 1018) Posted 28 Jul 2016 by Thyme Lawn Post: 1. Are tasks which are finished successfully after the deadline of any value for the scientists or developers? Or will the results of these tasks be ignored anyway? Yes, , but only if the workunit hasn't been validated or reached its maximum number of error/total/success tasks before the late task is reported. 2. Do tasks which are finished successfully after the deadline provide credits? Same answer as question 1. 3. If I disable Run test applications in my settings but still keep the application Beta Testing Version of D.E.N.I.S Application enabled, will I get different tasks (maybe with longer deadlines)? Or do both settings have to be enabled to get tasks of Beta Testing Version of D.E.N.I.S Application at all? Tasks will be the same. Both options have to be enabled to allow sending of beta work. If the Carro-Rodriguez-Laguna-Pueyo Epicardial Model (Carro et al. 2011) for human ventricular cells application had a mix of production and beta work users could only receive beta tasks if Run test applications is enabled. If there was any production work for Beta Testing Version of D.E.N.I.S Application users could receive those with Run test applications disabled.
12) Message boards : Number crunching : Very long wus (Message 996) Posted 25 Jul 2016 by Thyme Lawn Post: I used SysInternals Process Monitor to check what the beta application does in the slot directory during a checkpoint. The sequence is as follows: File "denis_state" is not found. Creates the file "temp" with "Desired Access: Generic Write, Read Attributes" and "ShareMode: Read, Write". Successful with "OpenResult: Overwritten". Does this twice. Writes the "CP" line to "stderr.txt". Writes 1280 bytes to "temp" then successfully closes it once. Attempts to create "temp" with "Desired Access: Read Attributes, Delete, Synchronize", "Disposition: Open", "ShareMode: Read, Write, Delete". This causes a sharing violation (repeated on 5 further attempts) because the file was opened twice with "ShareMode: Read, Write", only closed once and the new open attempt is trying to add "Delete" to "ShareMode". The obvious solution to this is to remove the spurious open of "temp".
13) Message boards : News : Telegram Channel (Message 906) Posted 15 Jul 2016 by Thyme Lawn Post: The problem is due to the following "link" on the page Jesús linked to: tg://resolve?domain=denisproject Telegram can be installed from here. I installed the desktop application but have uninstalled it because it seems to require a mobile phone number. I only have a fixed line telephone and the application tells me the number (which I've had for more than 30 years) is invalid.
14) Message boards : News : Beta Version of DENIS Simulator (Natrium) now running (Message 824) Posted 22 Mar 2016 by Thyme Lawn Post: It appears that I am unable to check the "run test applications" box in my settings. Makes it kind of hard to help test things. Can someone take a look at what is going on? The boxes on the DENIS@Home preferences page look like they should be clickable but they aren't. You need to click on the "Edit preferences" link to get to the page where you can change your preferences (and yes, I only spotted that link after the test applications box didn't change when I clicked it).
15) Message boards : News : Beta Version of DENIS Simulator (Natrium) now running (Message 813) Posted 18 Mar 2016 by Thyme Lawn Post: 3 tasks have been successfully completed (pending validation) by my i5-3230M Windows 7 Pro system. They were run simultaneously with very similar CPU times (min 3:42:45, max 3:44:44) but a very wide range of elapsed times (min 4:08:16, max 5:10:33).
16) Message boards : Number crunching : Deadline (Message 794) Posted 9 Feb 2016 by Thyme Lawn Post: The one other thing going against you this time is this chart: Tasks ready to send 0 Tasks in progress 0 Denis does NOT think ANY tasks are outstanding so it may have already written yours off as never coming back and if that's the case then NO you will not get any credits for crunching them. What I'm saying is that probably only an Admin can give you the final answer this time. Your current task list confirms what Mikey said. 2 of the 4 tasks sent to your computer on 1st February have status "Completed, too late to validate" (i.e. repair tasks were created when your tasks passed their deadline and the were validated before your tasks were reported). The other 2 have status "Not started by deadline - canceled" (i.e. a server abort was sent to your computer because the repair tasks were returned and validated before your tasks had started running).