Cosmic String Cusp Burst Strain
Cosmic String Cusp Burst Strain Introduction
Cosmic-string cusp bursts are a useful way to turn an exotic early-universe idea into a concrete strain estimate. In the picture used by this calculator, a loop oscillates, briefly forms a cusp, and sends a tightly beamed burst of gravitational radiation in a preferred direction. If the observer sits inside that beam, the burst can appear much stronger than the loop's average emission.
This calculator gives the Fourier-domain strain amplitude at one chosen observing frequency. It is meant for quick comparisons, not for simulating the full burst waveform or a detector pipeline, so its main purpose is to show how the signal changes as you adjust tension, loop size, frequency, or distance.
The basic trends are the ones built into the cusp scaling law: higher tension and larger loops raise the strain, while higher frequency and larger distance reduce it. Because the output is a dimensionless strain estimate, you can compare it with rough detector sensitivity bands, but any real search also has to account for bandwidth, burst duration, antenna response, and the chance that the beam misses Earth entirely.
Gravitational-Wave Bursts from Cosmic String Cusps
Cosmic strings remain hypothetical, but they provide one of the cleanest settings for studying bursty gravitational-wave emission. Their tension is often summarized by Gμ, the dimensionless combination of Newton's constant and energy per unit length. When a loop oscillates, a cusp can form briefly and concentrate the radiation into a narrow beam. That sharp burst is the phenomenon this calculator estimates.
The waveform of a cusp burst is strongly non-sinusoidal, so the strain depends on frequency through a power law rather than a single tone. The calculator uses the following approximation for the strain amplitude at observing frequency f from a loop of length L and a source at distance r:
when the loop size is expressed in seconds (L/c in SI units) and the distance r is in meters. This scaling captures the main physical levers: stronger tension, larger loops, and smaller distances increase the signal, while higher frequency suppresses it. The numerical factor 2.7 is a normalization often used in cusp estimates.
This calculator turns the inputs into a single strain estimate so you can compare scenarios without doing the unit conversion by hand. The loop length L is converted from meters to a light-crossing time, the source distance r is converted from megaparsecs to meters, and the observing frequency f is taken in hertz. Since the result is proportional to Gμ, any uncertainty in tension carries straight through to the strain.
Gravitational-wave detectors cover very different bands, which is why the same cusp event can matter for one instrument and vanish for another. Ground-based detectors such as LIGO and Virgo are most sensitive around tens to hundreds of hertz, space missions like LISA work in the millihertz range, and pulsar-timing arrays probe nanohertz signals. The calculator's frequency input lets you explore those bands one at a time and see how the cusp scaling shifts the expected strain.
How to Use the Cosmic String Cusp Burst Strain Calculator
Start by entering a value for the string tension Gμ. This quantity is dimensionless, and in most cosmic-string scenarios it is very small, so scientific notation is normal. A larger Gμ makes the burst stronger because the strain responds directly to tension in the formula.
Next, enter the loop length L in meters. This is the physical size of the oscillating cosmic-string loop. The calculator internally converts that length into a light-crossing time by dividing by the speed of light, so larger loops raise the strain through the two-thirds power that appears in the scaling law.
Then choose the observed frequency f in hertz. This is the frequency at which you want to evaluate the burst strain. The cusp signal weakens as frequency increases, which is why the same source can look more promising in a lower-frequency band than in a higher one.
Finally, enter the source distance r in megaparsecs. The calculator converts megaparsecs to meters before evaluating the formula. Distance reduces the observed amplitude, so moving the source closer is one of the fastest ways to raise the strain estimate. After clicking Compute Strain, the result box shows the estimated strain in scientific notation and a coarse sensitivity label based on broad thresholds coded into the page.
Those labels are deliberately rough. They are not substitutes for detector-specific analyses, matched filtering, burst pipelines, or population studies. They simply give you a quick qualitative cue about whether the computed strain is tiny or at least interesting enough to compare against a rough detector benchmark.
Cosmic String Cusp Burst Formula
The cosmic-string cusp burst calculator uses the same scaling relation shown above, and it is worth reading the inputs one by one so the dependence on each quantity is clear. The strain grows with Gμ and with loop size, but it shrinks as the source moves away or as you evaluate it at a higher frequency.
In the JavaScript, the computation is performed as follows. The loop length entered in meters is converted to seconds using L/c, where c is the speed of light. The distance entered in megaparsecs is converted to meters using 1 Mpc ≈ 3.086 × 1022 m. The code then evaluates the strain estimate
Formula: h ≈ (2.7 Gμ (L/c)^2/3) / (r f^1/3)
Here, h is dimensionless strain, L is the loop length in meters before conversion, c is the speed of light, r is the source distance in meters after conversion from megaparsecs, and f is the observing frequency in hertz. The numerical coefficient 2.7 is a model-dependent normalization commonly used for cusp estimates. Because this is a scaling relation, it is best interpreted as an approximate amplitude rather than an exact prediction for a specific astrophysical event.
Different papers describe cusp bursts in slightly different conventions, so you may see the spectral behavior written in more than one way depending on whether the author is discussing the time-domain waveform, the Fourier amplitude, or a strain normalization. This calculator keeps the exact formula implemented on the page, so the displayed result stays aligned with the script.
Worked Example: Default cosmic-string cusp burst inputs
A straightforward cosmic-string cusp burst example is already loaded into the form: Gμ = 10-7, L = 1010 m, f = 100 Hz, and r = 100 Mpc. Leaving those defaults in place lets you see the calculator's behavior before you start exploring more extreme loops, frequencies, or distances.
With those inputs, the strain is very small, which is exactly what you would expect from a distant burst produced by a modest tension. The main lesson is how the scaling works: stronger tension, a larger loop, a lower frequency, or a closer source all push the estimate upward.
Use the defaults as a reference point and then change one variable at a time. That makes it easier to see which input dominates in a given scenario; in this model distance usually has the sharpest impact because it appears linearly in the denominator, while frequency changes the output more gently through a cube-root power.
The table below gives a quick feel for how the cosmic-string cusp burst strain changes when loop size and frequency vary, while Gμ and distance stay fixed at the default values:
| L (m) | f (Hz) | h |
|---|---|---|
| 109 | 100 | ≈ 1.2×10-24 |
| 1010 | 100 | ≈ 5.6×10-24 |
| 1010 | 1000 | ≈ 2.6×10-24 |
| 1011 | 10 | ≈ 1.2×10-23 |
Interpretation and Detector Context
Once you have a cusp burst strain, the next question is which detector band it lands in. Ground-based observatories, space-based concepts, and pulsar-timing arrays all work in very different frequency ranges, so the same cosmic-string burst can be relevant in one setting and irrelevant in another. The calculator does not choose a winner for you; it simply gives the strain so you can compare it with the sensitivity curve that matters for your application.
Cusps are only one part of the broader cosmic-string story. Kinks on a loop radiate bursts with a different spectral shape, and interactions between strings can create junctions or fragment loops in ways that change both the burst rate and the observed spectrum. Realistic forecasts therefore depend on a whole network model, not just one hand-picked cusp event. This page intentionally leaves those population effects out so the single-event scaling stays easy to inspect.
From a theoretical point of view, cosmic strings arise in some symmetry-breaking schemes and in some string-theory constructions. The strength of the signal is often discussed in terms of the same Gμ parameter used here, and many observational bounds come from a mix of gravitational-wave data, the cosmic microwave background, and lensing constraints. A strain estimate from this calculator is only one piece of that larger picture.
Interest in cosmic strings has grown as gravitational-wave astronomy has matured. Pulsar timing, ground-based interferometers, and future space missions all probe different parts of the burst landscape, and a network of strings could contribute either isolated bursts or a broader stochastic background. This calculator is therefore useful as a quick intuition builder: it helps you see how the burst scales before you move on to search pipelines or network simulations.
Cosmic String Cusp Burst Limitations and Assumptions
This cosmic-string cusp burst calculator is intentionally stripped down to a single scaling law, so it leaves out a lot of the astrophysics that a full analysis would need.
It does not model redshift, loop evolution, beam geometry, burst duration, detector antenna patterns, noise integration, or the chance that Earth lies outside the narrow cusp beam. Those effects matter when you turn a strain estimate into an observational claim, but they would also make the page much harder to read at a glance.
The calculator also assumes that the input values describe a physically sensible cosmic-string scenario. Some combinations of Gμ, L, f, and r are mathematically allowed yet unrealistic in a detailed network model, and the on-page sensitivity label is only a coarse heuristic. It should not be treated as a stand-in for a search pipeline or a detector-specific forecast.
For that reason, the page is best used as a teaching aid and a back-of-the-envelope check. If you need burst rates, population statistics, or redshifted predictions, you will need a more complete model or the scientific literature. What this calculator does well is show how the strain changes when you nudge one cosmic-string parameter at a time.
Optional Mini-Game: Cusp Beam Aligner
If you want a faster way to build intuition, try this mini-game. Each round shows several burst candidates orbiting a detector ring. Every candidate carries the same variables used by the calculator—Gμ, loop length L, observing frequency f, and distance r. Your job is to aim the detector beam and lock onto the candidate that should produce the largest strain. The rule is the same one used above: louder bursts favor larger tension, larger loops, lower observing frequency, and especially smaller distance.
The game is intentionally separate from the calculator result, so it does not alter the math or your output. It simply turns the same tradeoffs into a short arcade challenge. On desktop, move the pointer and click to fire, or use the arrow keys plus Space. On mobile, tap the target you want to lock. The first practice scan is seeded from the values currently in the calculator, and later scans remix the numbers to keep each run fresh.
Mission: align the beam and pick the candidate with the largest strain h.
A good run teaches a subtle point of the formula: dropping the distance can matter even more than lowering the frequency, because distance appears linearly in the denominator while frequency enters only as a cube-root power.