[GSoC] Add programmatic parser for Seaton opacity tables#474
[GSoC] Add programmatic parser for Seaton opacity tables#474Manivenkat3612 wants to merge 1 commit intotardis-sn:masterfrom
Conversation
|
*beep* *bop* Details1 F401 [*] unused-import
Found 1 error.
[*] 1 fixable with the `--fix` option.
Complete output(might be large): Detailscarsus/io/literature/tests/test_seaton.py:10:8: F401 [*] `pytest` imported but unused
Found 1 error.
[*] 1 fixable with the `--fix` option.
|
|
@andrewfullard @jvshields , please take a look when you have a moment. Thanks! |
|
Hello @andrewfullard, @afloers, and @jvshields, I would greatly appreciate your review of my implementation for the GSoC 2026 First Objective under the Continuum Opacity Source Reader project idea. Your feedback would be very valuable to ensure I am aligned with the project’s expectations and coding standards. |
|
This seems sensible. Does the tardisbase environment have gzip already, or would that need to be installed? |
|
@andrewfullard Thanks for checking! It uses Python’s built-in gzip module (import gzip), so no extra package installation is needed in [tardisbase]. I also verified this in tardis-dev environment with: |

📝 Description
Type: 🚀
featureThis pull request implements the GSOC 2026 First Objective for the
project idea (Continuum Opacity Source Reader): a programmatic reader for the Seaton continuum opacity data tables from the CDS archive (VI/80).
What was implemented:
get_seaton_opacity_df(file_name): A simple, reusable function that downloads and parses Seaton opacity data files (gzip-compressed) from the CDS FTP archivelogT,logNe,kappa_planck,kappa_rosselandKey features:
https://cdsarc.cds.unistra.fr/ftp/VI/80/{file_name}Files added:
carsus/io/literature/seaton.py- Reader function implementationcarsus/io/literature/__init__.py- Module initialization and exportscarsus/io/literature/tests/test_seaton.py- Test suite📌 Resources
🚦 Testing
All changes have been tested using pytest.
pytest carsus/io/literature/tests/test_seaton.py -vreturns 1 passed)Test coverage:
☑️ Checklist
build_docslabelAI Usage Statement
Tool used: GitHub Copilot
How used: Refining code changes and improving PR wording.
Tool used: Gemini
How used: to research on (Opacities from the Opacity Project : VI/80) archive and to know about its formatting.
Confirmation: I confirm that I have read the PR Checklist and the AI and LLM Usage Policy. I fully understand all AI-assisted changes and can explain every modification in this PR.