Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork70
chore: prefer ArrayPartitionStyle to preserve nesting structure#483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ChrisRackauckas commentedAug 21, 2025
Rebase for the tests? |
DhairyaLGandhi commentedAug 25, 2025
I have a question, what purpose does nesting ARrayPartitions serve and is that a structure that should be maintained? Because we could always flatten the paritions of the children as partitions of the parent directly right? |
kellertuer commentedAug 25, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
For the context in#480 originally comes from, no please do not flatten the structure: In that setting we handle elements on a product manifold with ArrayPartitions. We do not have to dive into manifolds, set products are enough: Imagine you are on a set If you internally handle that in a fancy-flattened way, sure, feel free ;) But on the outer I would like to access the first or second element of |
Uh oh!
There was an error while loading.Please reload this page.
Checklist
contributor guidelines, in particular theSciML Style Guide and
COLPRAC.
Additional context
Ref#480
Add any other context about the problem here.