BRP4
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250362588
RAC: 35541
14 Jul 2011 13:21:54 UTC
Topic 195866
(moderation:
The Binary Radio Pulsar search (BRP) on Einstein@home will soon run out of data from the Parkes Multibeam Pulsar Survey (PMPS). We'll continue this search with new data from Arecibo, under a new label "BRP4". The transition BRP3 -> BRP4 is estimated for early next week.
BM
BM
BRP4
)
does this mean we will run the same apps then or will we have new version?
The application binaries will
)
The application binaries will be those that we used before, but will have a new name (BRP3 will be replaced with BRP4). If you are using an app_info.xml, I'd suggest you double the einsteinbinary_BRP3>... section and replace "einsteinbinary_BRP3>" with "einsteinbinary_BRP4>" in the second copy.
BM
BM
You would need to duplicate
)
You would need to duplicate the ... section declaring the name, too.
The version numbers and plan classes remain the same, Bernd?
RE: The version numbers and
)
Yes, but you shouldn't need either of these when using an app_info.xml, should you?
BM
BM
RE: The application
)
and there i thought you'd come up with a CUDA-4 version.. :|
does this file app_info and
)
does this file app_info and good :
By cons I miss the lines for the purpose : Gravitational Wave S6 GC search
einsteinbinary_BRP3
Binary Radio Pulsar Search
einsteinbinary_BRP4
Binary Radio Pulsar Search
einsteinbinary_BRP3_1.07_windows_intelx86__BRP3cuda32.exe
einsteinbinary_BRP3_1.00_graphics_windows_intelx86.exe
einsteinbinary_BRP4_1.07_windows_intelx86__BRP3cuda32.exe
einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe
cudart_xp32_32_16.dll
cufft_xp32_32_16.dll
db.dev.win.96b133b1
dbhs.dev.win.96b133b1
einsteinbinary_BRP4
107
windows_intelx86
0.200000
1.000000
BRP4cuda32
6.12.11
einsteinbinary_BRP4_1.07_windows_intelx86__BRP3cuda32.exe
cudart_xp32_32_16.dll
cudart32_32_16.dll
cufft_xp32_32_16.dll
cufft32_32_16.dll
einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe
graphics_app
db.dev.win.96b133b1
db.dev
dbhs.dev.win.96b133b1
dbhs.dev
CUDA
1
220200960.00
einsteinbinary_BRP4
107
windows_intelx86
0.200000
1.000000
BRP4cuda32
6.12.11
einsteinbinary_BRP4_1.07_windows_intelx86__BRP3cuda32.exe
cudart_xp32_32_16.dll
cudart32_32_16.dll
cufft_xp32_32_16.dll
cufft32_32_16.dll
einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe
graphics_app
db.dev.win.96b133b1
db.dev
dbhs.dev.win.96b133b1
dbhs.dev
CUDA
1
220200960.00
RE: RE: The version
)
It only matters if you're installing an app_info for the first time, and want to preserve existing work downloaded under the stock app. But for existing users of BRP3 app_infos - no, it wouldn't matter.
RE: einsteinbinary_BRP4_1
)
What will the file name be. Is it like in the quote, ending with .......BRP3cuda32.exe
or like this, ending with .....BRP4cuda32.exe
einsteinbinary_BRP4_1.07_windows_intelx86__BRP4cuda32.exe
We just ran out of PMPS data
)
We just ran out of PMPS data files, i.e. there will no more work be generated for BRP3. We still have ~30.000 BRP3 tasks to send out, though. (Note: the 'work remaining' on the server status pages is estimating when the last PMPS results will arrive back on the server, not when the last tasks are sent out)
If all goes well, we'll start generating BRP4 work in the next two days.
The plan classes will stay the same (e.g. 'BRP3SSE'), the application name will (of course) be 'einsteinbinary_BRP4', the application version numbers have been reset to '1.00'.
BM
BM
i have done this, but still
)
i have done this, but still get no WUs, not for BRP3, not for BRP4. why?