Skip to content

Don't merge: hack skip values #728

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

havogt
Copy link
Contributor

@havogt havogt commented Apr 28, 2025

No description provided.

Copy link

Mandatory Tests

Please make sure you run these tests via comment before you merge!

  • cscs-ci run default
  • launch jenkins spack

Optional Tests

To run benchmarks you can use:

  • cscs-ci run benchmark-bencher

To run tests and benchmarks with the DaCe backend you can use:

  • cscs-ci run dace

In case your change might affect downstream icon-exclaim, please consider running

  • launch jenkins icon

For more detailed information please look at CI in the EXCLAIM universe.

offset_provider = method(*args) if args else method()
if gtx_common.is_neighbor_connectivity(offset_provider):
offset_provider_type = offset_provider.__gt_type__()
if True: #not offset_provider_type.has_skip_values:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would expect that removing -1s for fields that don't have skip_values set would be enough, because all that have skip_values should be protected by a can_deref.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to Till the can_deref only protects the neighbor sums, if there is a direct access like CONN[0] this does not help.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant, if the user claims has_skip_values, then the user has to use neighbor_sum.

@havogt havogt changed the title don't merge: hack skip values Don't merge: hack skip values Apr 28, 2025
@halungge halungge mentioned this pull request May 28, 2025
halungge added a commit that referenced this pull request Jun 6, 2025
Add a function that removes remaining skip values from the neighbor
tables. This replaces [PR 728](#728)

- Replacing the skip values is configurable by a flag in the
`GridConfig`.
- when `GridConfig.keep_skip_values = False` the skip values in the
neighbortables of the `Connectivity` will be replaced by the max index
in the neighborhood of an entity. This is done for all except for the
pentagon points in a global grid.

---------

Co-authored-by: Hannes Vogt <[email protected]>
@havogt
Copy link
Contributor Author

havogt commented Jun 6, 2025

merged in #761

@havogt havogt closed this Jun 6, 2025
iomaganaris pushed a commit that referenced this pull request Jun 16, 2025
Add a function that removes remaining skip values from the neighbor
tables. This replaces [PR 728](#728)

- Replacing the skip values is configurable by a flag in the
`GridConfig`.
- when `GridConfig.keep_skip_values = False` the skip values in the
neighbortables of the `Connectivity` will be replaced by the max index
in the neighborhood of an entity. This is done for all except for the
pentagon points in a global grid.

---------

Co-authored-by: Hannes Vogt <[email protected]>
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