| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 39
|
|
| Author |
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges:
|
2) The second change is that if your result is invalid, then the max credit you get is 50% of the computed credit or your claimed credit, whichever is less. How is that different from before? |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges:
|
It was 50% of computed credits
----------------------------------------![]() Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006 ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
2) The second change is that if your result is invalid, then the max credit you get is 50% of the computed credit or your claimed credit, whichever is less. How is that different from before? Before it was 50% of the computed (aka Valid) credit only, they were only claiming 12-20 credits and gettint 50-70, now they will only get claimed. I have no problem with granting credit for work done, when there is a problem wu, or a problem with the coding. By running problem wu, it helps identify a problem, some credit is due. |
||
|
|
mikefinn
Cruncher USA Joined: Apr 27, 2007 Post Count: 43 Status: Offline Project Badges:
|
I was just about to post that I still had wingman with these invalid workunits when I saw this post: http://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=419197 That thread,http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,35031, is the real resolution of the issue.
|
||
|
|
rilian
Veteran Cruncher Ukraine - we rule! Joined: Jun 17, 2007 Post Count: 1460 Status: Offline Project Badges:
|
Thanks, it looks like a very fair change!
---------------------------------------- |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges:
|
May I hijack this thread with non-Vina observation even thought it is marked as Resolved?
----------------------------------------I found this HCC1 result strange (it is in PVer): X0000137180593201211061243_ 1-- 705 Pending Verification 23.4.2013 06:08:26 23.4.2013 18:28:04 1.42 62.3 / 0.0 X0000137180593201211061243_ 0-- 705 Pending Verification 23.4.2013 06:08:20 25.4.2013 19:22:39 0.04 50.8 / 0.0 <== mine 1.42 hours of CPU time for ATI WU? Wondering what was its Total Run Time (ETA: seems it is the same. 6.10.58 bug ). Its Result Log:Result Name: X0000137180593201211061243_ 1-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> Commandline: projects/www.worldcommunitygrid.org/wcg_hcc1_img_7.05_windows_intelx86__ati_hcc1 --zipfile X0000137180593201211061243.zip --imagelist images.txt --device 0 <app_init_data> <major_version>6</major_version> <minor_version>10</minor_version> <release>58</release> <app_version>705</app_version> <app_name>hcc1</app_name> <project_preferences> <color_scheme>Tahiti Sunset</color_scheme> <max_frames_sec>7</max_frames_sec> <max_gfx_cpu_pct>5.0</max_gfx_cpu_pct> </project_preferences> <project_dir>C:\ProgramData\BOINC/projects/www.worldcommunitygrid.org</project_dir> <boinc_dir>C:\ProgramData\BOINC</boinc_dir> <wu_name>X0000137180593201211061243</wu_name> <comm_obj_name>boinc_2</comm_obj_name> <slot>0</slot> <wu_cpu_time>0.000000</wu_cpu_time> <starting_elapsed_time>0.000000</starting_elapsed_time> <using_sandbox>0</using_sandbox> <user_total_credit>7086570.815058</user_total_credit> <user_expavg_credit>18279.214755</user_expavg_credit> <host_total_credit>86622.949952</host_total_credit> <host_expavg_credit>3590.918668</host_expavg_credit> <resource_share_fraction>1.000000</resource_share_fraction> <checkpoint_period>60.000000</checkpoint_period> <fraction_done_start>0.000000</fraction_done_start> <fraction_done_end>1.000000</fraction_done_end> <gpu_type></gpu_type> <gpu_device_num>-1</gpu_device_num> <gpu_opencl_dev_index>-1</gpu_opencl_dev_index> <ncpus>0.000000</ncpus> <rsc_fpops_est>25399328680341.000000</rsc_fpops_est> <rsc_fpops_bound>1269966434017050.000000</rsc_fpops_bound> <rsc_memory_bound>78643200.000000</rsc_memory_bound> <rsc_disk_bound>50000000.000000</rsc_disk_bound> <computation_deadline>1367289866.000000</computation_deadline> <vbox_window>0</vbox_window> </app_init_data> INFO: gpu_type not found in init_data.xml. INFO: GPU device not specified in init_data.xml. Checking Commandline. Boinc requested ATI gpu device number0 Unzipping input images ../../projects/www.worldcommunitygrid.org/X0000137180593201211061243_X0000137180593201211061243.zip Processing jobdescription Number of Images defined in image list is 2 Found compute platform Advanced Micro Devices, Inc. Selecting this platform CL_DEVICE_NAME: Cedar CL_DEVICE_VENDOR: Advanced Micro Devices, Inc. CL_DEVICE_VERSION: CAL 1.4.1457 (VM) CL_DEVICE_MAX_COMPUTE_UNITS: CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3 CL_DEVICE_MAX_WORK_ITEM_SIZES: 128 / 128 / 128 CL_DEVICE_MAX_WORK_GROUP_SIZE: 128 CL_DEVICE_MAX_CLOCK_FREQUENCY: 300 MHz CL_DEVICE_ADDRESS_BITS: 32 CL_DEVICE_MAX_MEM_ALLOC_SIZE: 200 MByte CL_DEVICE_GLOBAL_MEM_SIZE: 512 MByte CL_DEVICE_ERROR_CORRECTION_SUPPORT: no CL_DEVICE_LOCAL_MEM_TYPE: local CL_DEVICE_LOCAL_MEM_SIZE: 32 KByte CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE CL_DEVICE_EXTENSIONS: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt cl_khr_d3d10_sharing Estimated kernel execution time = 0.91101 [sec] Starting analysis of X0000137180593201211061243.jp2... Extracting GLCM features... Total kernel time: 2495.051270 (1026 kernel executions) Total memory transfer time: 1.915981 Average kernel time: 2.431824 Min kernel time: 2.342578 (dx=19 dy=17 sample_dist=24 ) Max kernel time: 2.561805 dx=1 dy=1 sample_dist=0 INFO: GPU calculations complete. Total time for X0000137180593201211061243.jp2: 2584 seconds Finished Image #0, pctComplete = 0.500000 Starting analysis of X0000137180594201211061243.jp2... Extracting GLCM features... Total kernel time: 2454.137451 (1026 kernel executions) Total memory transfer time: 3.828972 Average kernel time: 2.391947 Min kernel time: 2.304774 (dx=23 dy=11 sample_dist=24 ) Max kernel time: 2.523718 dx=1 dy=1 sample_dist=0 INFO: GPU calculations complete. Total time for X0000137180594201211061243.jp2: 2541 seconds Finished Image #1, pctComplete = 1.000000 CPU time used = 5126.068059 03:05:29 (3488): called boinc_finish </stderr_txt> ]]> Cheers ![]() ![]() Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006 ![]() [Edit 1 times, last edit by branjo at Apr 26, 2013 1:34:50 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hijack alright. The VINA jobs [do it alone, which was the tried exploit] had the problem, just as I think PG is doing it alone too, except those who were trying to urinate up the wrong tree forgot about the check-system at WCG, but still getting the ol 'half of award' credit. Well the half of 'whatever is less' means that now 20 is claimed [as computed by the server actually], and half of that is awarded, meaning a I7 becomes a PIV.
In the case of HCC there's always 2 tasks that check each other. Why those temp alias chose to hide inside bigger teams made them less visible. To me complete reversal of any credit is the only proper action, certainly the admin will be able to make these accounts inaccessible [change password, edit name, garble email address] and invisible i.e. flow to BOINCstats for roll-up is nullified. These were surely known crunchers who created additional accounts to do that malpractice. Gives the whole crunching community a bad rap, so if these can be name/shamed to return the favor, I'm all for it. There's a but: The credit hole was closed, there only being a credit grant hole! Invest much effort to seek them out? I'd say, just move on. |
||
|
|
johncmacalister2010@gmail.com
Veteran Cruncher Canada Joined: Nov 16, 2010 Post Count: 799 Status: Offline Project Badges:
|
Hijack alright. The VINA jobs [do it alone, which was the tried exploit] had the problem, just as I think PG is doing it alone too, except those who were trying to urinate up the wrong tree forgot about the check-system at WCG, but still getting the ol 'half of award' credit. Well the half of 'whatever is less' means that now 20 is claimed [as computed by the server actually], and half of that is awarded, meaning a I7 becomes a PIV. In the case of HCC there's always 2 tasks that check each other. Why those temp alias chose to hide inside bigger teams made them less visible. To me complete reversal of any credit is the only proper action, certainly the admin will be able to make these accounts inaccessible [change password, edit name, garble email address] and invisible i.e. flow to BOINCstats for roll-up is nullified. These were surely known crunchers who created additional accounts to do that malpractice. Gives the whole crunching community a bad rap, so if these can be name/shamed to return the favor, I'm all for it. There's a but: The credit hole was closed, there only being a credit grant hole! Invest much effort to seek them out? I'd say, just move on. If this chicanery is really happening it represents a woeful waste of time, energy and talent - the same sleaze we see in the dissemination of viruses. ![]() crunching, crunching, crunching. AMD Ryzen 5 2600 6-core Processor with Windows 11 64 Pro. AMD Ryzen 7 3700X 8-Core Processor with Windows 11 64 Pro (part time) ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Here's an example of the new points policy in operation:
DSFL_ 00070-29_ 0000014_ 0728_ 3-- 625 Valid 26/04/13 13:49:19 26/04/13 17:39:01 3.69 73.6 / 103.6 DSFL_ 00070-29_ 0000014_ 0728_ 2-- 625 Error 16/04/13 13:49:03 26/04/13 14:10:45 0.00 0.0 / 0.0 DSFL_ 00070-29_ 0000014_ 0728_ 1-- 625 Valid 12/04/13 07:13:15 16/04/13 13:48:33 3.41 133.5 / 103.6 DSFL_ 00070-29_ 0000014_ 0728_ 0-- 625 Invalid 12/04/13 07:13:01 12/04/13 08:18:44 0.65 27.3 / 27.3 The Invalid _0 wingman is the usual version 6.10.25. Still amounts to 42 points/hour , compared with my Valid _3 result giving 28. |
||
|
|
|