ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Hunting the Higgs: Why is it So Hard?

Updated on July 27, 2012

Recent data from the Large Hadron Collider could be interpreted as a sighting of the elusive Higgs boson. This isn't the first time such hints have been reported. All of which raises the question: how can researchers not know whether they've seen the Higgs or not?

For more on the Higgs Boson and the latest results, please see:

Has the Higgs Boson come out of Hiding?

Particle accelerators such as the Large Hadron Collider (LHC) are complicated machines. At the LHC, protons are accelerated to nearly the speed of light and smashed into each other at a rate of around 600 million collisions per second.

These collisions produce billions of particles - and they don't pop out with labels saying "this is an electron" or "this is a Higgs boson". Instead, the identity of each particle has to be worked out from properties such as its charge, its velocity, and at what point in the detector it is found. Based on these properties, scientists can make a good guess that a particular particle is an electron (or a neutrino, or a photon), but they can't always be sure.

What makes it even more tricky in the case of hunting the Higgs is that researchers at the LHC can't see the Higgs directly. They have to infer that a Higgs particle existed briefly in the murky depths of the collider by looking for pairs of particles that could have been created by its decay. However, the same types of particles are also produced by other processes, so the Higgs signal that scientists are looking for is in fact a slight overproduction of relevant pairs of particles compared to what would be expected if the Higgs did not exist.

The search is restricted to pairs of particles which have energies in a particular range. The exact energy that the pair will have depends on the mass of the Higgs boson, which isn't known. Fortunately, previous experiments have ruled out a Higgs mass of less than 115 GeV or more than 158 GeV, so researchers at the LHC are able to concentrate on searching for a "bump" in the number of particle pairs that are produced with energies between 115 and 158 GeV.

What the Higgs signal is expected to look like. The blue part is the background signal (the photon pairs produced by other processes). The red part is the "bump" - the extra pairs produced by Higgs decay - that would imply the presence of a Higgs.
What the Higgs signal is expected to look like. The blue part is the background signal (the photon pairs produced by other processes). The red part is the "bump" - the extra pairs produced by Higgs decay - that would imply the presence of a Higgs. | Source

But even if researchers find a "bump" in the correct range of energies, how do they know that it isn't just due to random statistical fluctuations? After all, there are thousands of interactions going on inside the accelerator that could have any number of different outcomes: it's not at all impossible that at a particular moment the quantum soup could react in such a way as to produce a slightly more particles with a particular energy than average. A bump in the data, such as the one seen recently at the LHC, could be the signature of a Higgs particle springing briefly into life, or just random fluctuation.

How to decide whether a result is significant

Particle physicists have spent years carefully calculating exactly what they expect to see being produced at the LHC, based on our best knowledge of particle physics (the Standard Model). When they see an unexpected result, they calculate the probability of seeing that result, assuming that the Higgs does not exist. If they find that the probability is sufficiently small, they begin to consider whether the alternative conclusion - that the Higgs does exist - is in fact more likely.

The researchers at ATLAS say that the bump in their data has an 8% chance of being the result of random statistical flucutation*. Particle physicists generally don't accept a finding until the confidence level is 5 sigma – a 0.00003% chance of being a random fluctuation. That sounds like an astonishingly stringent criteria, but there are good reasons for being sceptical. For more about uncertainties and when to have confidence in a scientific result, please see:

How Certain is Certain?

*source: results were announced at a conference last friday, and reported at profmattstrassler.com/2011/07/22/atlas-and-cms-summarize-their-higgs-searches/

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)