WUR-AI / WUR-AI/diffWOFOST

Testing GPU support -- possible solution

Open
#58 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ideas
Dominant language
Python
Stars
25
Forks
6
Avg merge
2d 23h
Merged PRs (30d)
1

Description

I think I found something interesting regarding the implementation/testing of cpu/gpu support: apparently PyTorch recently introduced a "meta" device that can be used exactly for testing these kind of purposes (https://docs.pytorch.org/docs/stable/meta.html). If I understood correctly, it allows you to move tensors to a "meta" device which is just some hypothetical imaginary device that stores no data. It also allows you create "meta" computations without actual data and can be used to verify whether the device switching happened properly. If the model attempts to make a computation using both a "meta" and cpu/gpu tensor it crashes. So I think if a model can successfully be transferred from cpu to a meta device and ran there it guarantees compatibility with gpu. (if its available of course). And this test can be run without the use of a gpu! Anyways curious to hear your thoughts!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the PyTorch meta device documentation linked in the issue, then inspect the repository for existing CPU/GPU support tests; no specific files or tests are named. Determine whether meta-device execution can validate device transfers and mixed-device failures without a GPU. Done means an agreed test scope and passing coverage without requiring GPU hardware.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.