You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a 3-dim Stencil Code. When I tried to instead of using dash::BLOCKED in all three dimensions for the DistributionSpec, to use dash::NONE in the dimension of the linear index, I got problems b/c some units had zero volume.
The reason is certainly, that my TeamSpec (with no prior unit distribution given to the TeamSpec constructor) with units distributed to all three dimensions after using balance_extents doesn't combine with my DistributionSpec in a way that would be helpful.
I already tried to give only two dimensions to the TeamSpec, but then my program wont compile b/c the types are not compatible.
Is there a way to make this work without giving the unit distribution manually to TeamSpec? Maybe the balance_extents method should be modified to take an argument about which dimensions it should use?
I don't want to use a 2D dash::NArray, b/c that would make it more or less impossible to use the halo features how they are intended.
The text was updated successfully, but these errors were encountered:
@Spielix I came across a similar problem. My solution was to create a 2D balanced TeamSpec and take the two dimensions of it as the first two input dimensions of the 3D TeamSpec:
I'm working on a 3-dim Stencil Code. When I tried to instead of using
dash::BLOCKED
in all three dimensions for theDistributionSpec
, to usedash::NONE
in the dimension of the linear index, I got problems b/c some units had zero volume.The reason is certainly, that my
TeamSpec
(with no prior unit distribution given to theTeamSpec
constructor) with units distributed to all three dimensions after using balance_extents doesn't combine with myDistributionSpec
in a way that would be helpful.I already tried to give only two dimensions to the
TeamSpec
, but then my program wont compile b/c the types are not compatible.Is there a way to make this work without giving the unit distribution manually to
TeamSpec
? Maybe the balance_extents method should be modified to take an argument about which dimensions it should use?I don't want to use a 2D
dash::NArray
, b/c that would make it more or less impossible to use the halo features how they are intended.The text was updated successfully, but these errors were encountered: