What is the "other name" for the BRP6? Is that Perseus Arm?
I don't see it in Einstein Apps nor Prefs "as such"
If you click on the applications link on the home page of the website you will see two binary radio pulsar searches that are using data from the Parkes Radio Telescope. These are:
Binary Radio Pulsar Search (Parkes PMPS XT) aka BRP6
and (if you scroll down near the bottom of the page)
Binary Radio Pulsar Search (Perseus Arm Survey) aka BRP5
Please note that under the 'Version' column on that page you see things like 1.39 (BRP5-cuda32-nv301). This is NOT the application name - it is the version number followed by the plan class, in brackets. The plan class allows the scheduler to make sure you have the most appropriate application for your particular platform (combination of hardware and software on your host). Because the application being used for BRP6 is actually the same (with a slightly different name) as the one that was used for BRP5, the same plan classes are being reused. If you want to confirm the application being used, take a look in the 'Application' column of your tasks list on the website. In your case, you now have "Binary Radio Pulsar Search (Parkes PMPS XT) v1.39 (BRP5-cuda32-nv301)" showing against your most recent tasks - ie the BRP6 app selected with the BRP5-cuda32-nv301 plan class.
As far as not seeing BRP6 listed in preferences, here is the list that I can see, taken from the E@H preferences page, clearly showing both the old Perseus Arm Survey and the new Parkes PMPS XT search.
Binary Radio Pulsar Search (Arecibo):
Binary Radio Pulsar Search (Arecibo, GPU):
Binary Radio Pulsar Search (Perseus Arm Survey):
Binary Radio Pulsar Search (Parkes PMPS XT):
Gravitational Wave search S6Bucket Follow-up #1:
Gamma-ray pulsar search #4:
You just need to make sure you have selected those searches from that list that you want to run. From that list, the BRP5 Perseus Arm Survey has just about finished. There will be 'resend' tasks available from time to time as needed over the next few weeks but these will become increasingly difficult to get. If you don't want to be bothered by these, just select the new Parkes PMPS XT search.
To make sure you are informed about changes like this, it's a very good idea to follow the 'News' and 'Technical News' boards and to a lesser extent the 'Science' board for the changes that are occurring or are being proposed. For example, this thread covers the very recent end of BRP5 and the start of BRP6, whilst this thread (running for several years) has offered many useful insights into possible future directions under consideration and which have later come to pass.
Quote:
I did see a cuda55 app setup, but it's for Mac.
It's my perception that the cuda32 library/SDK could be the holdup in my case at least, with these task errors.
The version of CUDA would NOT be responsible for the validate errors you had when you were running your GT 640 overclocked. Apart from Mac users, everybody else is using apps built with the old version of CUDA because that is all that the Devs have released. Until apps designed for a newer CUDA are built, tested and released, there is nothing to be done by the user.
RE: What is the "other
)
If you click on the applications link on the home page of the website you will see two binary radio pulsar searches that are using data from the Parkes Radio Telescope. These are:
Binary Radio Pulsar Search (Parkes PMPS XT) aka BRP6
and (if you scroll down near the bottom of the page)
Binary Radio Pulsar Search (Perseus Arm Survey) aka BRP5
Please note that under the 'Version' column on that page you see things like 1.39 (BRP5-cuda32-nv301). This is NOT the application name - it is the version number followed by the plan class, in brackets. The plan class allows the scheduler to make sure you have the most appropriate application for your particular platform (combination of hardware and software on your host). Because the application being used for BRP6 is actually the same (with a slightly different name) as the one that was used for BRP5, the same plan classes are being reused. If you want to confirm the application being used, take a look in the 'Application' column of your tasks list on the website. In your case, you now have "Binary Radio Pulsar Search (Parkes PMPS XT) v1.39 (BRP5-cuda32-nv301)" showing against your most recent tasks - ie the BRP6 app selected with the BRP5-cuda32-nv301 plan class.
As far as not seeing BRP6 listed in preferences, here is the list that I can see, taken from the E@H preferences page, clearly showing both the old Perseus Arm Survey and the new Parkes PMPS XT search.
Binary Radio Pulsar Search (Arecibo):
Binary Radio Pulsar Search (Arecibo, GPU):
Binary Radio Pulsar Search (Perseus Arm Survey):
Binary Radio Pulsar Search (Parkes PMPS XT):
Gravitational Wave search S6Bucket Follow-up #1:
Gamma-ray pulsar search #4:
You just need to make sure you have selected those searches from that list that you want to run. From that list, the BRP5 Perseus Arm Survey has just about finished. There will be 'resend' tasks available from time to time as needed over the next few weeks but these will become increasingly difficult to get. If you don't want to be bothered by these, just select the new Parkes PMPS XT search.
To make sure you are informed about changes like this, it's a very good idea to follow the 'News' and 'Technical News' boards and to a lesser extent the 'Science' board for the changes that are occurring or are being proposed. For example, this thread covers the very recent end of BRP5 and the start of BRP6, whilst this thread (running for several years) has offered many useful insights into possible future directions under consideration and which have later come to pass.
The version of CUDA would NOT be responsible for the validate errors you had when you were running your GT 640 overclocked. Apart from Mac users, everybody else is using apps built with the old version of CUDA because that is all that the Devs have released. Until apps designed for a newer CUDA are built, tested and released, there is nothing to be done by the user.
Cheers,
Gary.