Fermilab seems to have ruled out monopoles with mass less than 850 GeV, but I have seen some estimates of the mass thought to be in the order of up to $10^{18}$ GeV, which, of course, would make them undetectable in any accelerators. By 2013, the LHC is scheduled to reach up to 14 TeV. The only disputed sighting of a cosmic ray produced magnetic monopole was in 1982 when Blas Cabrera reported discovering one (Valentine event monopole). This has never been duplicated. CERN has set up the Monopole and Exotics Detector MOEDAL. Other experiments set up to detect them are the Antarctic Impulsive Transient Antenna--ANITA, and the Antarctic Muon And Neutrino Detection Array, aka AMANDA. While both of these detected neutrinos, neither detected magnetic monopoles (looking for Cerenkov radiation produced by products of monopole interaction).
Another method of detection is to look for induced current in a superconducting ring when a monopole passes through.
Joseph Polchinski called the existence of monopoles “one of the safest bets that one can make about physics not yet seen.” This shows some optimism on his part that one will be seen. Is there any reason or way to limit the mass of the monopole on the upside to 14 TEV or less?


Question: Are comments considered a form of documentation?
Answer: Comments are definitely documentation. For most projects, comments are (unfortunately) the primary (if not only) form of project documentation. For this reason, it's very important to get it right. You need to make sure that this documentation stays accurate despite code changes. This is a common problem with comments. Developers often "tune" them out when they're working in familiar code, so they forget to update comments to reflect code. This can create out-of-date, and misleading comments.

A lot of people suggest making the code self-documenting. This means that instead of comments, you restructure your code to remove the need for them. This can get rid of most of the "what" and "how" comments, but doesn't really help with the "why" comments. While this might work effectively to get rid of most comments, there are still plenty of times where writing a comment is the simplest and most efficient way to document a piece of code.