Basically, It intrigues me to know the scientific difference between the two telescopes radio data and to discover why the Parkes search was ended :-)
The search's scientific lead is going to post some background here soon.
Quote:
Is the project focus now solely on the GW search? and are there plans for a GPU app for that search?
E@H has always been focused on the search for gravitational waves and we're advancing those data analyses in every aspect with every new run. There's also going to be a GPU version of new CPU analysis code that's currently being finalized. The GPU version should become ready for testing next year.
In the meantime we'll continue to analyze Arecibo data (still using GPUs, as BRP4G) and we're preparing a GPU version of the Fermi search (FGRPB1) as well, a first instance of which might already be ready this year.
let me cover your questions related to the Binary Radio Pulsar Search, as the person having been responsible for that.
Gavin_14 wrote:
I assume we have sifted through all the 'of interest' frequencies in the Parkes data to hand, hence the fact this particular run on the data set has ended.
In principle, you can search for even higher frequencies in the Parkes data to make sure you have not missed anything, but that would be at the moment computationally prohibitive – even with Einstein@Home. Our search code's computing time scales roughly with the maximum spin frequency searched for to the power of three. So increasing this value by a factor of two (which might make sense) will get you an increase in computing time by a factor of eight. This would make this extended search way longer than useful. In the end one has to ask oneself whether this computing time is not spent more productively on other searches on new, fresh data.
Gavin_14 wrote:
Will there be new data from Parkes (at a later date perhaps) or has it been deemed that information from Parkes does not fit the current project goals, for whatever reason? If so, why?
The Parkes data we have searched in the initial and the extended search are archival data from the Parkes Multi-beam Pulsar Survey. The data we have is all there is. Parkes still does pulsar searches, but the data are not public. We still are getting fresh Arecibo data from the PALFA Survey, and some Einstein@Home members are members of the PALFA collaboration.
Finally, as I wrote in the first sentence, I have been responsible for the science behind the Einstein@Home radio pulsar searches in the past, but have as of September last year moved on the being the press and outreach officer for the Max Planck Institute for Gravitational Physics in Hannover. As a consequence of that my priorities have changed, and I can work on Einstein@Home only from time to time.
Gavin_14 wrote: Basically, It
)
The search's scientific lead is going to post some background here soon.
E@H has always been focused on the search for gravitational waves and we're advancing those data analyses in every aspect with every new run. There's also going to be a GPU version of new CPU analysis code that's currently being finalized. The GPU version should become ready for testing next year.
In the meantime we'll continue to analyze Arecibo data (still using GPUs, as BRP4G) and we're preparing a GPU version of the Fermi search (FGRPB1) as well, a first instance of which might already be ready this year.
Stay tuned,
Oliver
Einstein@Home Project
Dear all, dear Gavin, let me
)
Dear all, dear Gavin,
let me cover your questions related to the Binary Radio Pulsar Search, as the person having been responsible for that.
In principle, you can search for even higher frequencies in the Parkes data to make sure you have not missed anything, but that would be at the moment computationally prohibitive – even with Einstein@Home. Our search code's computing time scales roughly with the maximum spin frequency searched for to the power of three. So increasing this value by a factor of two (which might make sense) will get you an increase in computing time by a factor of eight. This would make this extended search way longer than useful. In the end one has to ask oneself whether this computing time is not spent more productively on other searches on new, fresh data.
The Parkes data we have searched in the initial and the extended search are archival data from the Parkes Multi-beam Pulsar Survey. The data we have is all there is. Parkes still does pulsar searches, but the data are not public. We still are getting fresh Arecibo data from the PALFA Survey, and some Einstein@Home members are members of the PALFA collaboration.
Finally, as I wrote in the first sentence, I have been responsible for the science behind the Einstein@Home radio pulsar searches in the past, but have as of September last year moved on the being the press and outreach officer for the Max Planck Institute for Gravitational Physics in Hannover. As a consequence of that my priorities have changed, and I can work on Einstein@Home only from time to time.
Cheers, Benjamin
Einstein@Home Project
0 CPU , 0 GPU (Internet,
)
MY PC, i7-3770k @ 4.2Ghz , GTX1070 , from 0 to 4 tasks on the GPU
0 CPU , 0 GPU (Internet, videos, office work) : 70 - 100 W (80+-5W)
0 CPU , 1 GPU (Internet, videos, office work) : 185W +-5W
0 CPU , 2 GPU (Internet, videos, office work) : 195w +-5W
0 CPU , 3 GPU (Internet, videos, office work) : 195w +-5W
0 CPU , 4 GPU (Internet, videos, office work) : 198w +-5W
tolafoph wrote:MY PC,
)
Nice info, thanks!