Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DaCe orchestaration: re-evaluate explicit memory movement #69

Open
romanc opened this issue Dec 4, 2024 · 0 comments
Open

DaCe orchestaration: re-evaluate explicit memory movement #69

romanc opened this issue Dec 4, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@romanc
Copy link

romanc commented Dec 4, 2024

Description

In DaCe/orchestration mode, we have a function to explicitly "Move all data from DaCe memory space to GT4Py". According to @FlorianDeconinck, this data download might be a no-op because we own the memory. This is an investigation issue to see if we can get rid of that function.

Background

This is a follow-up from NOAA-GFDL#87 (comment).
@romanc romanc added the enhancement New feature or request label Dec 4, 2024
@romanc romanc mentioned this issue Dec 4, 2024
Merged
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@romanc