Papers › How should spin-weighted spherical functions be defined?

How should spin-weighted spherical functions be defined?

27 Apr 2016arXiv:1604.08140links table onlyarchive 2025-07-28

Michael Boyle

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Spin-weighted spherical functions provide a useful tool for analyzing tensor-valued functions on the sphere. A tensor field can be decomposed into complex-valued functions by taking contractions with tangent vectors on the sphere and the normal to the sphere. These component functions are usually presented as functions on the sphere itself, but this requires an implicit choice of distinguished tangent vectors with which to contract. Thus, we may more accurately say that spin-weighted spherical functions are functions of both a point on the sphere and a choice of frame in the tangent space at that point. The distinction becomes extremely important when transforming the coordinates in which these functions are expressed, because the implicit choice of frame will also transform. Here, it is proposed that spin-weighted spherical functions should be treated as functions on the spin group. This approach more cleanly reflects the geometry involved, and allows for a more elegant description of the behavior of spin-weighted functions. In this form, the spin-weighted spherical harmonics have simple expressions as elements of the Wigner 𝔇 representations, and transformations under rotation are simple. Two variants of the angular-momentum operator are defined directly in terms of the spin group; one is the standard angular-momentum operator L, while the other is shown to be related to the spin-raising operator ƪ. Computer code is also included, providing an explicit implementation of the spin-weighted spherical harmonics in this form.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 17 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 17 samples from 2 repositories, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

moble/SphericalFunctions.jl officialmentioned on GitHubMITSyntology: not harvested report
moble/spherical officialMITSyntology: 8 samples, 5 ran (0 instrument-failed) · 3 unverified report
moble/spherical_functions officialMITSyntology: 9 samples, 4 ran (0 instrument-failed) · 5 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

17 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

9ran
8unverified

Licence: 0 of the 17 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

moble/spherical official repository 8 samples, 5 ran (0 instrument-failed) · 3 unverified
Lplus spherical/modes/derivatives.py ran MIT (permissive) · c3d66f4bf7cc4dca · report fixture: signature self:MockSWSH/2/complex · returned MockSWSH · level recorded 2026-09-25
Lsquared spherical/modes/derivatives.py ran MIT (permissive) · 595a6ead31c8a3c5 · report fixture: signature self:MockSWSHArray/0/? · returned MockSWSHArray · level recorded 2026-09-25
Lz spherical/modes/derivatives.py ran MIT (permissive) · 73b8fa47a7f2bdf5 · report fixture: signature self:MockSWSH/0/? · returned MockSWSH · level recorded 2026-09-25
conjugate spherical/grid/algebra.py ran MIT (permissive) · ac7964e51cc8f811 · report fixture: signature self:Grid/0/?, inplace:bool/0/bool · returned Grid · level recorded 2026-09-25
truncate_ell spherical/modes/utilities.py ran MIT (permissive) · dadda285e9f11330 · report fixture: signature self:SphericalHarmonicArray/0/?, new_ell_max:int/0/int · returned SphericalHarmonicArray · level recorded 2026-09-25
conjugate spherical/modes/algebra.py unverified MIT (permissive) · 2556857c19541ea6 · report
grid in 20 papers spherical/modes/utilities.py unverified MIT (permissive) · bd39c20114eb94e2 · report
index in 10 papers spherical/modes/utilities.py unverified MIT (permissive) · 21b00aed4b55bdb2 · report
moble/spherical_functions official repository 9 samples, 4 ran (0 instrument-failed) · 5 unverified
Lsquared spherical_functions/SWSH_modes/derivatives.py ran MIT (permissive) · 831e0350f8581c71 · report fixture: signature self:MockSWSH/2/complex · returned MockSWSH · level recorded 2026-09-25
Lz spherical_functions/SWSH_modes/derivatives.py ran MIT (permissive) · 442de9260f805abf · report fixture: signature self:MockSWSHArray/0/? · returned MockSWSHArray · level recorded 2026-09-25
conjugate spherical_functions/SWSH_grids/algebra.py ran MIT (permissive) · 02641c8427a3914f · report fixture: signature self:MockGrid/0/?, inplace:bool/0/bool · returned MockGrid · level recorded 2026-09-25
truncate_ell spherical_functions/SWSH_modes/utilities.py ran MIT (permissive) · 73671ccdf95f81a6 · report fixture: signature self:SphericalHarmonicArray/0/?, new_ell_max:int/0/int · returned SphericalHarmonicArray · level recorded 2026-09-25
Lplus spherical_functions/SWSH_modes/derivatives.py unverified MIT (permissive) · b7c863b42e470047 · report
conjugate spherical_functions/SWSH_modes/algebra.py unverified MIT (permissive) · 722c133e5142bc31 · report
grid in 20 papers spherical_functions/SWSH_modes/utilities.py unverified MIT (permissive) · 1adba7e0f60adafc · report
index in 10 papers spherical_functions/SWSH_modes/utilities.py unverified MIT (permissive) · 69ad5617df33bfef · report
modes spherical_functions/SWSH_grids/utilities.py unverified MIT (permissive) · 5617b8b481cabbf0 · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections