Skip to content

Add ComponentData#201

Draft
JamesEdgeley wants to merge 1 commit into
UKAEA-Edge-Code:devfrom
JamesEdgeley:je/component-data
Draft

Add ComponentData#201
JamesEdgeley wants to merge 1 commit into
UKAEA-Edge-Code:devfrom
JamesEdgeley:je/component-data

Conversation

@JamesEdgeley
Copy link
Copy Markdown

Add ComponentData class

@JamesEdgeley
Copy link
Copy Markdown
Author

@SMijin this is approximately the feature I need for the 2D3V reflection

@SMijin
Copy link
Copy Markdown
Contributor

SMijin commented Mar 3, 2026

I was thinking this could go in the ExtractorData as an optional argument, i.e. the current extraction takes the first N components, but there could always be an offset there, as well. So your ComponentData would just be ExtractorData<1> with the appropriate offset. This way one could take any number of consecutive components.

This would make it easier to repurpose existing tests, but would also require some doc changes. I can look at this in a few weeks.

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.

2 participants