Repository navigation
Conversation
…tack PR 4) exozippy-mkdust <ra> <dec> reads every extinction map it can reach and writes <name>.dust.params.yaml: candidate priors on sed.dust_anchor (the existing channel of the dust profile, review 8.9.8), one live and the rest commented out, the way mkticsed comments out non-default catalog rows. Default, following Nataf: Surot+2020 (VVV E(J-Ks), VizieR), else Zelakiewicz+2025 (UKIRT A_Ks, Zenodo 14919461, pinned in zenodo_assets as an on-demand third-party record), converted to A_V with the Nataf+2013 bulge-mean ratios (A_V = 6.458 E(J-Ks); 7% sight-line scatter measured on Nataf's Table 3). Also written: each map in its native band (with the dust_anchor_band it needs), Nataf+2013 OGLE-III A_I/E(V-I) (Table 3, md5 pinned) and SFD/SF11 (live only at |b| >= 5). Maps that cannot be queried programmatically are listed with the reason. A failed query is reported as FAILED in the file and as a WARNING, and the header names the preferred map the default passed over. docs/dust_maps.md records the conversions, widths and choices; sed.md, redclump.md, sed/defaults.yaml and CLAUDE.md point there. zenodo.py's download messages now name the host (the OGLE archive is not Zenodo). Tests (no network): tests/test_mkdust.py. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AWjnwpYHm56hSpKBzbPhrG
…s, as ruff does The Zelakiewicz+2025 record's title quotes its paper's title; ruff format writes such a literal single-quoted, so render_record's round trip against the shipped registry must too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AWjnwpYHm56hSpKBzbPhrG
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
exozippy-mkdust <ra> <dec>reads every extinction map it can reach at a sky position and writes<name>.dust.params.yaml: candidate priors onsed.dust_anchor, ONE live and every other commented out, the wayexozippy-mkticsedcomments out non-default catalog rows. It is the fourth PR of the dust stack (color rows #600 -> red clump #601 -> the sight-line A_V(d) profile #604 -> this), and feeds #604's existing channel:sed.dust_anchoris the profile's sampled total, the extinction at its anchor (the bar distance with a red clump or a galactic model). No new config key.Maps
zenodo_assets, on demand)Why the default is A_V converted with Nataf+2013 rather than a native Ks line (
dust_anchor_band): the fit's law (CCM89 + O'Donnell) has a fixed near-infrared slope, so A_V/A_Ks ~ 8.4 at R_V = 3.1, where the bulge measures 13-15. A Ks anchor would put ~40% too little dust into V and I. The Ks lines are written commented, and they become the better choice once the near-infrared slope is fitted (the next PR in the stack). Conversion: Nataf+2013 bulge means A_I = 1.217 E(V-I), E(J-Ks)/E(V-I) = 0.3433. Width: the map error plus a 7% sight-line scatter of that ratio, measured on Nataf's Table 3, plus 10% for the A_Ks -> E(J-Ks) step of a Ks map. Everything is in the newdocs/dust_maps.md, andsed.md,redclump.md,sed/defaults.yamlandCLAUDE.mdpoint to it.A failed query is written as FAILED with its error and logged as a WARNING, and the header names the preferred map the default passed over. A changed catalog format raises
MapFormatErrornaming the missing column. It never guesses a column.Example: KMT-2024-BLG-2087, (l, b) = (0.64, -1.70)
VizieR (CDS) was down when this was written, so Surot is FAILED here. The two maps that could be read agree:
Also
zenodo.py's download messages name the host. They used to say "from Zenodo" for every file, which was wrong for the OGLE archive.scripts/zenodo_publish.py'srender_recordquotes a title holding"the way ruff does, so the registry round-trip test holds for the new third-party record.Zelakiewicz:2025,Schlafly:2011. Registered as an SED utility (mkdust) for the GUI.Tests
tests/test_mkdust.py(no network: fixtures in each map's own format, monkeypatched VizieR/IRSA). It covers each reader's numbers, outside / flagged / failed handling, the default order, the SFD latitude rule, the CLI's negative sexagesimal Dec, every written line parsing as YAML with references.bib keys, and the live line resolving as thesed.dust_anchorprior of a lens + source + clump dust-profile system.test_citation_fieldnow also scans mkdust's keys. The Zenodo pin passes the livenetworktest.The live Surot path is untested end-to-end: CDS refused connections all day. Its column names (
E(J-Ks),e_E(J-Ks)) follow VizieR's convention, and if they differ it raises naming them.🤖 Generated with Claude Code
https://claude.ai/code/session_01AWjnwpYHm56hSpKBzbPhrG