OK, guys, gals, and fellow alpha-testers. Again, speaking specifically about FGRP (Gamma-ray pulsar search #3) GPU apps only:
I've got a workround for the -197 EXIT_TIME_LIMIT_EXCEEDED.
First, set up an app_config.xml file containing this section:
hsgamma_FGRP3
1
1
1
Make BOINC read the file, and check that it's been found properly: this is important, else the next stage will try to make your computer run 10 tasks at once....
Second, check that you understand the host/venue mapping for your fleet, and identify which host(s) and venue(s) will be running the FGRP3/GPU tests. Go to the Albert@Home preferences page for your account, and for the venue(s) you've selected for the test, set the "GPU utilization factor of FGRP apps" low. Really low. Crazy low, like 0.1 This is madness (don't say you haven't been warned), but with app_config.xml keeping the lid on your machine, it works.
Third, allow and fetch new FGRP3/GPU work for the machine. You should see the estimated run time for any work already cached on the machine jump five-fold - that's your confirmation that the setting has been transferred properly.
That should get us through to the first 100 validations for the project as a whole. Watch out for further advice on how we might handle phase 2.
I didn't want to spam the boards with my stats - just milestone theads - but apparently signatures are no longer optional. Follow the link if you're interested.
I hope the validate error problem has been fixed, I'm just about to start my first, all my wingmen that have completed this Wu already have validate error:
That Wu is completed, and is showing as 'Completed, waiting for validation', but the 'In progress' wingman is an OpenCL 1.1 Intel GPU, so it's either going to be inconclusive or Validate error.
A lot of my other Wu's were round 1 inconclusives with OpenCL 1.1 Intel GPUs, so they should validate straight away.
Well, we're making progress with the validations. As at 22:00 UTC (Bernd has kindly given us some access to the statistics), we had the following validations, all from Windows/64.
[pre]plan_class n
FGRPopencl-ati 9
FGRPopencl-intel_gpu 5
FGRPopencl-nvidia 20[/pre]
I'm still not sure what will happen when that last line reaches 100, but it looks like I won't have to keep watching overnight.
I didn't want to spam the boards with my stats - just milestone theads - but apparently signatures are no longer optional. Follow the link if you're interested.
OK, guys, gals, and fellow
)
OK, guys, gals, and fellow alpha-testers. Again, speaking specifically about FGRP (Gamma-ray pulsar search #3) GPU apps only:
I've got a workround for the -197 EXIT_TIME_LIMIT_EXCEEDED.
First, set up an app_config.xml file containing this section:
hsgamma_FGRP3 1 1 1Make BOINC read the file, and check that it's been found properly: this is important, else the next stage will try to make your computer run 10 tasks at once....
Second, check that you understand the host/venue mapping for your fleet, and identify which host(s) and venue(s) will be running the FGRP3/GPU tests. Go to the Albert@Home preferences page for your account, and for the venue(s) you've selected for the test, set the "GPU utilization factor of FGRP apps" low. Really low. Crazy low, like 0.1 This is madness (don't say you haven't been warned), but with app_config.xml keeping the lid on your machine, it works.
Third, allow and fetch new FGRP3/GPU work for the machine. You should see the estimated run time for any work already cached on the machine jump five-fold - that's your confirmation that the setting has been transferred properly.
That should get us through to the first 100 validations for the project as a whole. Watch out for further advice on how we might handle phase 2.
I didn't want to spam the boards with my stats - just milestone theads - but apparently signatures are no longer optional. Follow the link if you're interested.
http://www.boincsynergy.com/images/stats/comb-3475.jpg
I hope the validate error
)
I hope the validate error problem has been fixed, I'm just about to start my first, all my wingmen that have completed this Wu already have validate error:
https://albertathome.org/workunit/603947
Otherwise this is going to be Another real long journey.
Claggy
That Wu is completed, and is
)
That Wu is completed, and is showing as 'Completed, waiting for validation', but the 'In progress' wingman is an OpenCL 1.1 Intel GPU, so it's either going to be inconclusive or Validate error.
A lot of my other Wu's were round 1 inconclusives with OpenCL 1.1 Intel GPUs, so they should validate straight away.
Claggy
Well, we're making progress
)
Well, we're making progress with the validations. As at 22:00 UTC (Bernd has kindly given us some access to the statistics), we had the following validations, all from Windows/64.
[pre]plan_class n
FGRPopencl-ati 9
FGRPopencl-intel_gpu 5
FGRPopencl-nvidia 20[/pre]
I'm still not sure what will happen when that last line reaches 100, but it looks like I won't have to keep watching overnight.
I didn't want to spam the boards with my stats - just milestone theads - but apparently signatures are no longer optional. Follow the link if you're interested.
http://www.boincsynergy.com/images/stats/comb-3475.jpg
I continue having "Maximum
)
I continue having "Maximum elapsed time exceeded" error in all Binary Radio Pulsar Search (Perseus Arm Survey) v1.39 (BRP5-cuda32-nv270) tasks.
Rest of WU seem to run ok.
Trotador
Good I posted, last four
)
Good I posted, last four units have finished ok!:)
Trotador