| # The role of spin in relativistic three-photon standing-wave diffraction |
|
|
| ## Physical setting |
|
|
| Consider an electron incident on a linearly polarized standing x-ray wave formed by two counterpropagating beams. Each beam has peak intensity |
| $2.0\times10^{23}\,\mathrm{W\,cm^{-2}}$ and photon energy $3.1\,\mathrm{keV}$. The incident electron momentum is approximately $176\,\mathrm{keV}/c$, at an angle of $0.4^\circ$ to the laser propagation direction, and its spin is initially aligned with the electric field. |
|
|
| Study the relativistic three-photon Bragg branch with net photon numbers $n_r=2$ and $n_l=-1$. Label the incident momentum mode by $n=0$ and the diffracted mode by $n=3$. For finite-pulse calculations, use a ten-cycle $\sin^2$ turn-on, a flat plateau, and a ten-cycle $\sin^2$ turn-off. |
|
|
| Treat the quoted incident momentum as the approximate physical case. Use the generalized three-photon Bragg condition as an initial estimate and locate the finite-pulse resonance within the stated model; do not assume that the rounded momentum label is an exact numerical resonance coordinate. |
|
|
| Use a time-dependent Dirac description expanded in free momentum modes for the spin-$1/2$ electron. Use the corresponding time-dependent Klein-Gordon momentum-mode model as the spinless control. Let $p_E$ denote the electron-momentum component along the electric field and let $k$ be the photon momentum magnitude. |
| |
| ## Research problem |
| |
| Determine whether, and in what physically distinguishable ways, the electron spin changes resonant three-photon population transfer as $|p_E|/k$ is varied. Your conclusion must connect the computed spin-resolved momentum-mode dynamics to the spin content and oscillation rate of the diffracted wave packet, and must use the spinless control to delimit which effects are genuinely spin-dependent. |
|
|
| Construct the model-to-observable relations, numerical data, representations, and scientific argument needed to support your answer. The evidence must be sufficient to audit the physical channel identities, the comparison across momentum settings, and the stated scope of the conclusion. The number, order, and layout of figures are not prescribed. |
|
|
| ## Submission and resources |
|
|
| Submit one self-contained scientific report and an auditable offline calculation package containing the task-specific derivation, code, numerical data underlying all material claims, a provenance note listing every offline source or software document actually consulted and the method basis for items supplied from general knowledge, and concise run and environment information. Resource limits are supplied exclusively by the accompanying |
| `resource_limits.json`. Its fixed CPU allocation, candidate-active |
| wall time, network boundary are binding. No separate aggregate CPU-hour limit applies. Greater computational expense |
| receives no additional credit. |
|
|
| ## Reference and integrity policy |
|
|
| This examination is conducted without network access or live literature |
| retrieval. You may rely on your existing general scientific knowledge and, if any are |
| explicitly supplied with the examination, on those offline materials or |
| software documentation. Record every such source actually consulted. For formulas, |
| methods, constants, or conventions used from general knowledge rather than a |
| consulted source, state enough of the method basis, definition, value, units, |
| and convention to make the calculation auditable; do not invent a citation. |
| You are not required to identify or prove a publication date or to retrieve |
| literature during the examination. |
|
|
| The hidden target article and its identifying metadata, figures or captions, |
| supplementary material, author code or data, target-specific reproduction |
| code, solution or scoring material, online solutions, and worked |
| reproductions of this case must not be used. All submitted scientific figures |
| and numerical data must be generated by your own implementation of the stated |
| problem. |
|
|
| See [submission requirements](../../submission_requirements.md) for the common submission entry points. |
|
|
