Skip to content

Backport change from main to a new release branch#935

Open
VincentVanlaer wants to merge 38 commits intor25.12.1_colors_updatedfrom
r25.12.1-backport
Open

Backport change from main to a new release branch#935
VincentVanlaer wants to merge 38 commits intor25.12.1_colors_updatedfrom
r25.12.1-backport

Conversation

@VincentVanlaer
Copy link
Member

This contains:

  • Documentation fixes and additions. Since these do not affect installation and such, this provides quite some value without affecting users.
  • Bugfixes (e.g. the fixes for the new version of GCC, and some other recently reported issues)
  • All colors changes since the release

Please comment if you think certain changes should be in the small release. I have named the release 25.12.2 in the changelog but this can of course be changed.

abhro and others added 30 commits March 21, 2026 18:31
Older link is stale, use newer permalink provided by site
* [ci skip] minor change to python helper so different filters work.

* [ci skip] readme updates, still WIP

* [ci skip] new python visualisations for interpolation distance

* added interpolation radius to allow for quality checks in custom colors + added select case for those wishing to change interpolation method -- this still needs to be piped to a user option

* [ci skip] updating python helpers now so later commit is easier

* [ci skip] added zero point defined by user]

* [ci skip] added user defined zero point

* [ci skip]
 updating colors data file

* [ci skip] WIP README, new format and overview.

* [ci skip] changed defaults to Johnson UBVRI

* readme update

* [ci skip] pulling updates

* [ci skip] Update distance value in colors.defaults to 10pc

* [ci skip] cleaning

* [ci skip] pg star

* [ci skip] inlists

* [ci skip] updated defaults

* [ci skip] make_CMD_InterpRad_movie.py

* Update README.rst

* Update README.rst

* [ci skip] Enhance README with parameter examples

Added examples for various parameters in README.

* [ci skip] added management for missing columns in stellar atm tables

* [ci skip] inlist update

* Update README.rst

* Enhance README with test suite details and usage

Expanded the README to include detailed descriptions of the test suite's functionality, output, and purpose. Added sections on real-time visualization and inlist options.

* Create README.rst

* [ci skip] removed old python helpers from /colors/ as they are now deprecated with https://github.com/nialljmiller/SED_Tools

* cleaning for merge

* lintinh

* adding new colors data

* fortitude check --fix

* ruff check on python files

* added some pg star windows

* change colors test termination condition

* make sure to save final.mod in colors testing

* add final modl name

* fixing bug found in usage of clight where the wrong units were assumed for AB zeropoint. Also fixed Vega zero point interpolation error.

* [ci skip] cleaning files

* built with SDK 25.12.1

* moved colors data from colors/data to data/colors_data

* [ci skip] Added more files for moving the data.

* [ci skip] removing junk

* [ci skip] removing file io junk

* [ci skip] updates on file io operations. zero points are calculated at initilisation and SED tables are cached at initialiation.

* [ci skip] updates for history files and python helpers

* fixed inlist

* Python linting

* Python linting

* Apply suggestions from code review

removing unnecessary redefine of dp.

Co-authored-by: Warrick Ball <W.H.Ball@bham.ac.uk>

* [ci skip] docs linting

---------

Co-authored-by: pmocz <philip.mocz@gmail.com>
Co-authored-by: Warrick Ball <W.H.Ball@bham.ac.uk>
Allocate flux_cube_lambda for trilinear interpolation and update boundary checks to use lbound and ubound functions instead of assuming a 1 base index.
The omp simd directive assumes that all loop iterations are independent.
This is not the case for swapping elements of a single row/column.
Hence, this causes UB.
Changing names on MAC
Changing MRP names
@rhdtownsend
Copy link
Contributor

Should the release number follow the year-month-number approach we've been using previously -- e.g., 26.3.1 for the first release in March 2026?

@matthiasfabry
Copy link
Contributor

I agree, this’ll be a full blown release, not just a patch of an old one.

@aurimontem
Copy link
Contributor

aurimontem commented Mar 22, 2026 via email

@Debraheem
Copy link
Member

Since this is shaping up to be a full release, I've updated the controls documentation by moving the new tdc controls from controls_dev into the controls.defaults. This is purely a documentation change. A separate pr will handle the merge into main.

…DC module.

Updated changelog for version 26.3.1, including new features in the TDC module.
@Debraheem
Copy link
Member

I've amended the changelog with the new release version name "26.3.1", and documentation for the tdc changes.

@Debraheem Debraheem mentioned this pull request Mar 22, 2026
@Debraheem
Copy link
Member

@nialljmiller @VincentVanlaer, aside from testing, is there anything else we need to add into this branch before merging and beginning the release process?

@rhdtownsend
Copy link
Contributor

Can we add a build check using SDK 26.3.2? This may require @matteocantiello to put together a Zenodo release for the SDK.

@VincentVanlaer
Copy link
Member Author

@nialljmiller @VincentVanlaer, aside from testing, is there anything else we need to add into this branch before merging and beginning the release process?

@Debraheem Two things would still need to happen. #926 needs to be merged (I wanted to do this earlier, but didn't find the time to properly test stellar) and the colors changes in #929 that are not the Newton iterations need to split out. Both of these can happen after this branch merges in however.

Can we add a build check using SDK 26.3.2? This may require @matteocantiello to put together a Zenodo release for the SDK.

@rhdtownsend Should be possible with just the SDK being on your website. I have also done some tests myself and it seems to work fine. But both of those would just be Linux tests.

@nialljmiller
Copy link
Collaborator

@nialljmiller @VincentVanlaer, aside from testing, is there anything else we need to add into this branch before merging and beginning the release process?

The colors changes in #929 that aren't the Newton iterations still need to be split out. But that can happen after this branch merges, so it's not a blocker. I will do that once #935 is in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants