This is only relevant for those few who are using app_info.xml files with the BRP4 app included in it. Otherwise, you can ignore this thread.
Triggered by some interesting feedback we got from volunteers we are now testing a new BRP4 app on Albert@Home that can process compressed input files. The compressed input files will free resources on the project infrastructure, AND of course this will reduce the file space occupied by E@H on your systems.
The new app can deal with both compressed input files and uncompressed ones. But once we switch to compressed data files for BRP4, the current BRP4 apps will stop to work. By that time the apps on your hosts will have been updated automatically to the new app generation, UNLESS you are using an app_info.xml file. Depending on the outcome of the tests on Albert@Home, this switch mights already occur next week (Jan 14 .. Jan 20).
BTW, if you are still using an app_info.xml file, the first thing you'll want to do is ask yourself WHY :-). Seriously: using the project specific preferences, Einstein@Home lets you opt-out of certain searches, and you can configure how many BRP4 GPU jobs should run in parallel, two main applications of app_info.xml some time ago.
Cheers
HB
Copyright © 2024 Einstein@Home. All rights reserved.
Note for BRP4 app_info.xml users
)
I wanted to say thank you for working on implementing support for compressed input files in the BRP4 application. This will be very helpful for those of us that are constrained by monthly bandwidth caps. I will give the test application a try out via Albert@home.
What are the typical sizes of
)
What are the typical sizes of the WUs uncompressed/compressed? Before/after comparisons are always nice!
RE: What are the typical
)
There's compression data in the thread where the idea was first floated. This message has some indicative values included.
Cheers,
Gary.
RE: RE: What are the
)
And also at this Albert message.
"from 2MB to 475K per file"