Jump to content

Talk:Gluino

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Perhaps the information on this page should be organized in a slightly more coherent manner? Dgiraffes (talk) 18:36, 27 July 2010 (UTC)[reply]

Current experimental evidence as of Dec, 2015 / Sep, 2016

[edit]

Just heard on radio that "gluino was discovered at LHC". The false "news" might come from Techtimes where they try to interpret the Dec 2015 CERN progress of CMS and ATLAS announcement (which was later revised - 18 Dec 2015). Apparently a confusion arouse combining together "new restrictions for the mass of the gluino" and statistically weak indication of "new particle being produced and decaying". As I understand the LHC message, there is new knowledge about the gluino, but this is only "rectricions for the mass" (saying, not whether it is, or what it is like, but only what it is not like, and not saying how to produce it but only how it likely cannot be produced). And after Run 2 of experiments will be finished, we may hope for a new particle to be discovered (having around 750 gigaelectronvolts), unless the bump in statistical graph shows to be just the usual random bump. Some more links: CERN Dec 2015 presentation of results of Run 2 until its suspension, nature, Wired

90.180.192.165 (talk) 02:06, 4 February 2016 (UTC)[reply]

Update: New mass bounds Latest results from CMS presented at ICHEP 2016 --90.180.192.165 (talk) 09:26, 19 August 2016 (UTC)[reply]

Repeated Sentence

[edit]

The sentence: "In the R-parity violating scenarios, gluinos can either decay promptly into multiple jets, or be long-lived leaving anomalous sign of "displaced decay vertices" from the interaction point where they are generated." is duplicated. I am unsure what "gluinos and their cascade decays" is supposed to say since that is an entire sentence. I think it would also be worth mentioning R-hadrons somewhere on this page. — Preceding unsigned comment added by Scienceperson42 (talkcontribs) 00:28, 27 January 2022 (UTC)[reply]