Ask Badger CERN CMS 1.5-million-evaluation physics test
Run the documented workload through the current system exactly as it operates today.
Run the identical workload under the same rules, conditions, boundaries, and required outcome.
Reconstruct the same 15,000 authentic CERN CMS events and 100 physics windows normally and with Badger, then compare every selected event, histogram, checksum, retained value, and elapsed time.
- same 15,000 CERN events
- same selected-event list and histogram
- fixed checksums
- retained values, elapsed time, and missing-fact YELLOW
For this high-performance computing application, the waste is unnecessary compute, retained data, energy, latency, and errors.
Finish the same safe high-performance computing job. Badger must cut unnecessary compute, retained data, energy, latency, and errors. Track the facts from start to finish. Missing facts mean YELLOW. GREEN means the result benefits all parties and may proceed. RED means it cannot proceed.
Same job. Same facts. Same needed result. How Badger builds the answer stays private.
Ask Badger CERN CMS 1.5-million-evaluation physics test
The authentic 15,000-event CERN source file downloads, then the normal system and the same system with Badger applied each complete 1.5 million fixed physics evaluations. The work stages, exact answer, and combined efficiency result appear below.
PRODUCTScientific Compute Equilibrium Scheduler
Ask Badger CERN CMS 1.5-million-evaluation physics test
Check whether Scientific Compute Equilibrium Scheduler can produce the same required high-performance computing result while reducing unnecessary compute, retained data, energy, latency, and errors.
Scientific data systems often keep and process every available field, even when the answer needs only a small checked set. That adds computer work, time, heat, and power without improving the answer.
Normally, complete this job with the current process: Reconstruct the same 15,000 authentic CERN CMS events and 100 physics windows normally and with Badger, then compare every selected event, histogram, checksum, retained value, and elapsed time. Then run the same job with Badger. Compare the finished results.
Run the same fixed input through the normal full-record reference system and the same system with Badger applied on the same device.
Finish the same safe high-performance computing job. Badger must cut unnecessary compute, retained data, energy, latency, and errors. Track the facts from start to finish. Missing facts mean YELLOW. GREEN means the result benefits all parties and may proceed. RED means it cannot proceed.
GREEN means the same required output and every listed proof gate passed. YELLOW means a required fact is missing. RED means the result failed.
This test runs the same CERN job two ways on one device. The first run uses every record. The second uses Badger. Both must rebuild particle mass, check 1.5 million events, find the same events, and return the same result.
CERN Open Data record 700 · DOI 10.7483/OPENDATA.CMS.CB8H.MFFA · Download the fixed reference result
This shows the result for this one test. CERN did not endorse it. It is not an LHC work test.