RM Mapping

Canonical operational file: Reverberation Mapping Support.md — covers hardware requirements, target list, precision budget, LAMP/SEAMBH/OzDES programme details, and pipeline design. This file preserved for its unique theoretical content not found in the canonical version: iso-delay paraboloid geometry, the transfer function formalism ($L_{line}(t) = \int \Psi(\tau) L_{cont}(t-\tau)d\tau$), BLR "breathing" mode physics, the aliasing simulation proposal, and the f-factor degeneracy discussion.

Sometimes a star flares up, and we see the direct light first. Later, we see "echoes" as that light reflects off surrounding dust clouds.

How it works: The time delay between the flash and the echo allows astronomers to map the 3D structure of the dust and calculate the distance to the star using simple geometry. (A famous example is the star V838 Monocerotis).

Non stop multi week or month long imaging of blackhole using [[Greedy Handoff]]

You are correct, and I apologize for the detour into gravitational waves. We are talking about Reverberation Mapping (RM) in Active Galactic Nuclei (AGN).

In the context of your distributed telescope array, you are focusing on the visual light echoes produced when a flash of radiation from the accretion disk (the "central engine") travels outward and reflects off surrounding structures.

The Physics of the "Monthly" Delay¶

The reason the time between the initial flash and the echo is measured in months (rather than milliseconds) is purely a matter of scale. For a supermassive black hole, the surrounding Dust Torus can be light-months or even light-years away from the center.

The Distance Equation: The time delay $\Delta t$ between the continuum (the initial flash) and the emission-line response (the echo) is given by:

$$\Delta t = \frac{R}{c} (1 + \cos \theta)$$

where $R$ is the radius of the reflecting region and $\theta$ is the angle relative to the observer's line of sight.
Scale: In massive galaxies like Fairall 9 or NGC 5548, the lag for the Broad Line Region (BLR) is typically 20 to 50 days, while the Dust Torus lag can be 100+ days (months).

"Moving from one side to another"¶

This seems to be talking about something different than the rest of the topic?

The specific phenomenon you described—observing disturbances moving from one side to the other—is known as Velocity-Delay Mapping.

Because the gas in the accretion disk and BLR is orbiting the black hole at high speeds, it is Doppler-shifted.

Blueshifted side: Gas moving toward us.
Redshifted side: Gas moving away from us.

As the central flash moves outward, it hits the "near" side of the orbiting gas first and the "far" side later. By observing the echo in the blueshifted spectrum first and then the redshifted spectrum (or vice versa), astronomers can effectively "see" the disturbance sweep across the structure. This allows us to map the geometry and mass of the black hole without needing a telescope large enough to resolve it visually.

The Role of Your Distributed Array¶

This is where your handoff algorithms become critical. To create an accurate velocity-delay map, you need uninterrupted monitoring of the light curve.

The Problem: A single ground-based telescope is limited by the "diurnal cycle" (daylight) and weather. A gap in data at a critical moment when the "echo" is passing through a specific velocity wing can ruin the entire model.
The Solution: Your distributed array uses handoff logic to ensure that as one site (e.g., in Europe) loses the target due to Earth's rotation, another site (e.g., in the Americas) is already locked on. This maintains a high-cadence, continuous light curve over the several months required to see the full echo cycle.

Sources¶

Peterson, B. M. (1993): "Reverberation Mapping of Active Galactic Nuclei." Publications of the Astronomical Society of the Pacific. (Established the fundamental methodology).
Horne, K., et al. (2004): "Echo Mapping of Active Galactic Nuclei." (Detailed the velocity-delay mapping and the need for continuous monitoring).
Bentz, M. C. (2015): "Black Hole Mass Estimates from Reverberation Mapping." (Discusses the time scales involved in these observations).

Potential Error in the Idea:

One detail to watch for: "Visual" echoes in the Dust Torus are often actually Infrared echoes (since the dust absorbs UV/Visible light and re-emits it as heat). If your array is strictly optical, you would be looking at the Broad Line Region (BLR) echoes (using spectroscopy) rather than the Dust Torus.

For your distributed telescope array, the answer depends on whether you are doing Photometric or Spectroscopic reverberation mapping. Since you are building a distributed system focused on high-cadence "handoffs," you can actually get away with surprisingly modest hardware if you choose your targets wisely.

1. The "Standard" Requirement¶

In professional astronomy, reverberation mapping (RM) is traditionally done with 2-meter class telescopes because they need to perform spectroscopy—splitting the light into a rainbow to measure specific emission lines (like H$\alpha$ or H$\beta$).

However, for a distributed array like yours, you are likely looking at Photometric RM, which uses specialized filters to measure brightness changes instead of full spectra.

Telescope Type	Aperture Size	Target Capability	Use Case
Small / Prosumer	0.3m – 0.5m (12–20")	Bright Seyfert Galaxies ($V < 14$)	Continuum monitoring & high-cadence "handoff" logic.
Meter-Class	0.8m – 1.2m	Quasars and faint AGN ($V < 17$)	High-precision RM and some narrowband work.
Professional	2.0m+	Deep space / High redshift	Detailed "Velocity-Delay" mapping (spectroscopy).

2. Why "Smaller" is often "Better" for your project¶

The "echoes" you are measuring happen over months, but the individual fluctuations can happen over hours or days.

The Cadence Problem: A 10-meter telescope is world-class, but you can only get time on it once a month. This creates "gaps" in your data.
The Array Advantage: If you have an array of 0.5m telescopes spread across the globe (e.g., in Groningen, Chile, and Australia), you can achieve a continuous light curve. For RM, sampling frequency (how often you look) is often more important than aperture (how much light you collect).

3. The Technical Constraint: Signal-to-Noise (SNR)¶

To measure an echo, you must detect a brightness change of roughly 1–2%. This is your "error budget."

Target Magnitude: Most bright AGNs (like NGC 5548 or Mrk 817) are between magnitude 13 and 15.
Exposure Time: On a 0.4m (16-inch) telescope, you can typically reach a high enough SNR for a Mag 14 AGN in about 300 to 600 seconds of exposure.
Conclusion: A 14-inch to 20-inch (0.35m - 0.5m) telescope is the "sweet spot" for a distributed array. It is small enough to be robotic and affordable, but large enough to see the "central engine" of hundreds of nearby galaxies.

4. Hardware Recommendations for your Array¶

If you are building this as a distributed software project (using your Go/GCP stack), I would aim for:

Aperture: 0.4m (16") Ritchey-Chrétien or CDK telescopes.
Mount: Direct-drive mounts (essential for the fast "handoff" and high-duty cycle you’re planning).
Filters: You need a "dual-band" approach. One filter for the continuum (the flash) and a narrow-band filter tuned to the emission line (the echo).1

A Note on Velocity Mapping: If you want to see the "moving from one side to another" (Velocity-Delay Mapping), you actually need spectroscopy. For that, you would need at least one 1.0m telescope in your array to act as the "spectroscopic anchor" while the smaller ones handle the photometric timing.

Summary: How big do you need?¶

Minimum viable: 0.25m (10") — Limited to only the top 10 brightest AGNs.
Recommended: 0.4m to 0.5m (16-20") — Allows you to monitor ~50+ active galaxies with professional-grade precision.
Overkill: 1.0m+ — Expensive to maintain in a distributed array, but would allow you to see the echoes of black holes in the very distant universe.

Would you like me to look into specific "Narrowband" filter sets that would allow a 0.4m telescope to simulate the spectroscopic results needed for velocity mapping?

Reverberation Mapping (RM) is the "gold standard" for measuring the mass of supermassive black holes (SMBHs) that are too far away to be seen directly. Since we cannot resolve the black hole's event horizon with standard telescopes, we use time resolution as a substitute for spatial resolution.

Think of it like being in a dark canyon and shouting: even if you can't see the canyon walls, you can figure out how far away they are by timing how long it takes for your echo to return.

1. The Components: Flash and Echo¶

An Active Galactic Nucleus (AGN) consists of a central engine—the accretion disk—surrounded by clouds of gas called the Broad Line Region (BLR).

The Continuum (The Flash): The accretion disk near the black hole is unstable and frequently flickers or flares. This produces a "continuum" of UV and visible light.
The Emission Lines (The Echo): The gas clouds in the BLR absorb this high-energy light and "re-emit" it as specific spectral lines (like Hydrogen-beta).
The Delay: Because light has a finite speed, we see the flash from the disk first. We then have to wait for that light to travel to the BLR clouds, excite them, and for their "echo" to reach us.

2. The Physics of the "Month" Delay¶

The distance from the accretion disk to the BLR clouds is typically light-weeks or light-months.

If the time delay ($\tau$) is 60 days, we know the radius ($R$) of the gas clouds is $R = c\tau$.
For a black hole with a mass of 100 million Suns, the BLR is roughly the size of our solar system, leading to the months-long delays you remembered.

3. Measuring the Mass (The Virial Equation)¶

Once we have the radius from the time delay, we only need the velocity of the gas to calculate the black hole's mass. We get the velocity by looking at the "width" of the spectral lines (the Doppler broadening). The mass ($M$) is calculated using the virial theorem:

$$M = f \frac{R \Delta v^2}{G}$$

$R$: Radius (from the time delay).
$\Delta v$: Velocity of the gas (from the spectral line width).
$G$: Gravitational constant.
$f$: A "form factor" that accounts for the unknown shape and orientation of the clouds.

4. Why Your Distributed Array Matters¶

The biggest challenge in RM is that black holes don't flare on a schedule. They are "stochastic" (random).

Continuous Cadence: If you miss a 3-day window of clear weather, you might miss the "peak" of a flare, making it impossible to calculate the exact delay.
The Handoff: Your distributed array solves the "aliasing" problem. By handing off the observation from a telescope in Europe to one in the Americas, you create a 24/7 monitoring stream. This allows you to catch the subtle "moving disturbances" (velocity-delay maps) as the light sweeps from the blueshifted side of the rotating disk to the redshifted side.

Key Takeaways for your project¶

Target Selection: Focus on "Seyfert 1" galaxies; they have the best balance of brightness and variability for RM.
Filter Logic: You'll need high-precision photometry to detect the ~1-2% brightness changes in the echo.
Timing: Your Go backend needs to sync timestamps across the array with millisecond precision to ensure the "echo" isn't lost in the noise of site-to-site calibration differences.

Black Hole Accretion Flows

This presentation by a leading astrophysicist explains how measuring X-ray and optical echoes allows us to quantify the effects of curved spacetime and black hole spin.

Reverberation Mapping (RM) is essentially 3D scanning using tijd (time) delays.

Since we cannot resolve the central region of a galaxy spatially (it's too small and too far), we use the finite speed of light to map it. By watching how a flash of light propagates through the gas, we can reconstruct the geometry of that gas.

Here is the elaboration on the physics, geometry, and mathematics behind it.

1. The Geometry: "Iso-Delay Paraboloids"¶

This is the most critical concept to understand. When the central black hole flares, that light spreads out in a sphere. However, we (the observers) are viewing this from one specific direction.

Imagine a single flash from the black hole.

The gas clouds directly between us and the black hole see the flash first, and re-emit it almost instantly. The lag is near zero.
The gas clouds behind the black hole see the flash later, and then that light has to travel all the way back to us. The lag is huge ($2 \times$ radius / $c$).

Mathematically, the "locus of points" (the shape) where the time delay is identical is a paraboloid with the black hole at the focus.

Near side: Short time delay .
Far side: Long time delay

As the flash propagates, this paraboloid surface sweeps through the gas cloud like a scanner. By analyzing the shape of the "echo," we can tell if the gas is a flat disk, a spherical shell, or a cone.

2. The Mathematics: The Transfer Function¶

We model the relationship between the continuum light (the trigger) and the emission line (the echo) using a mathematical tool called a Transfer Function ($\Psi$).

$$L_{\text{line}}(t) = \int_{0}^{\infty} \Psi(\tau) L_{\text{cont}}(t - \tau) d\tau$$

$L_{\text{cont}}$: The light curve of the central source (what you see in the blue filter).
$L_{\text{line}}$: The light curve of the gas clouds (what you see in the red/line filter).
$\Psi(\tau)$: The "Response Function." This map tells us how much gas is located at each time delay $\tau$.

If the Broad Line Region (BLR) is a thin ring face-on, the transfer function is a sharp spike (all gas responds at the same time). If it is a thick spherical shell, the function is a broad "smear."

3. The "Breathing" Mode¶

One of the most fascinating discoveries from RM is that the BLR is not a static structure; it "breathes."

When the AGN becomes brighter (more luminosity), the ionization front moves outward. The gas clouds that are capable of emitting the specific line (like H-beta) are now found further out.

High Luminosity: Larger Radius $\rightarrow$ Slower speed (orbiting further out).
Low Luminosity: Smaller Radius $\rightarrow$ Faster (orbiting closer in).

This confirms the system is governed by gravity (Virialized), which leads us to the mass equation.

4. Deriving the Black Hole Mass¶

To weigh the black hole, we use the Virial Theorem. We need two numbers:

Size ($R$): We get this from the time lag ($\tau$).
Velocity ($V$): We get this from the Doppler width of the emission line.

$$M_{BH} = f \times \frac{R_{\text{BLR}} \times (\Delta V)^2}{G}$$

$f$ (The Unknown): This is the "fudge factor." It depends on the inclination. If we look at a disk face-on, we see no Doppler motion (the gas moves across the sky, not towards us), so we measure zero velocity even if the gas is moving fast. We usually assume an average $f \approx 4-5$, but this is the biggest source of error.

5. Why Distributed Arrays are Critical (Aliasing)¶

This is where your project becomes relevant.

To solve the equation above, you need to measure the time lag $\tau$ accurately. But what if the lag is 2.5 days?

Day 1: You observe.
Day 2: You observe.
Day 2.5: The "echo" arrives, but it is daytime in your location. You cannot see it.
Day 3: You observe. The echo is gone.

This is called Aliasing. The gaps in your data introduce fake signals. A single telescope often misses the most important features of the light curve because of the sun or weather.

Your Solution: A distributed array ensures that when it is day in Europe, a telescope in the US or Japan is observing. You catch the features that happen "between the nights," allowing you to measure lags with far higher precision than even large professional observatories that only observe once per night.

Next Step¶

For your simulation project, you could simulate this "Aliasing" problem. You could write a Go program that generates a fake AGN light curve, "samples" it with gaps (simulating a single telescope), and then samples it continuously (simulating your array) to prove mathematically how much better your array recovers the Black Hole mass. Would you like to try that?

https://www.youtube.com/watch?v=2zu5eD-YT1E&start=0

Weighing Supermassive Black Holes (Reverberation Mapping)

The Problem: To measure the mass of a supermassive black hole in a distant galaxy (AGN), astronomers use "reverberation mapping." They watch for a flicker in the accretion disk (near the hole) and wait to see how long it takes for that flicker to "echo" in the gas clouds further out. This delay (lag) reveals the mass.

Why it fails normally: The "echo" can take days or weeks. If the sun rises or clouds roll in at a single observatory during the critical "echo" moment, the data is ruined.

The Distributed Solution: A "Longitude Relay." As the target sets in Europe, it rises in the US, then in Asia. A distributed amateur network can maintain a continuous "light curve" for weeks, ensuring the specific echo time-lag is captured. This allows us to "weigh" black holes that professional observatories can't spare the time to monitor.

Source: A Feasibility Study of Photometric Reverberation Mapping Using Meter-Class Telescopes (Utah State University/DigitalCommons).

1. The "Atomic Clock" Question¶

No, you do not need an atomic clock for Reverberation Mapping.

Your intuition about black holes warping time is correct (General Relativity), but "Reverberation Mapping" doesn't measure that warping directly.

What it measures: It measures the time it takes for a flash of light to travel from the black hole's disk out to the gas clouds surrounding it.1
The Scale: This distance is huge—billions of kilometers. Light takes days or weeks to travel that far.
The Precision Needed: You only need to know "did the flash happen on Tuesday or Wednesday?" Standard computer clocks (NTP) synced to the internet are plenty accurate for this.

B. Black Hole Reverberation Mapping

Has it been done? Yes, but rarely by amateurs alone.
The Project: Professional collaborations often recruit smaller 1-meter class telescopes (which are just big amateur scopes) for this.
The Opportunity: Bright Active Galactic Nuclei (AGNs) like NGC 5548 vary on timescales of ~20 days.4 A distributed amateur network is actually better at this than professionals because professionals can't book a telescope for 6 months straight. Amateurs can.
Source: Reverberation Mapping of Active Galactic Nuclei (Peterson & Horne, 2004) explicitly mentions the need for "high cadence" (daily) monitoring over "long duration" (months)—the perfect use case for a distributed network.