Publish native closure inputs - #172
Draft
krystophny wants to merge 1 commit into
Draft
Conversation
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 changed
ErwhenOm_tEis prescribedOm_tE-to-ErconversionWhy
The K3 outer-loop extractor needs the exact thermodynamic forces used with D31/D32. The native output contained the transport matrix and profiles but omitted their radial derivatives; prescribed-rotation mode also omitted the corresponding radial electric field.
Impact
Downstream closures can consume one self-contained, unit-tagged native file instead of combining solver output with mutable side inputs.
Validation
fo test er_rotation_testfo test ntv_output_geometry_testfo test multispecies_iteration_sync_testfopipeline: build, tests and lint passThis remains stacked and unmerged for flux-pumping verification.