Torch backend implementation
Open
@selmanozleyen is already working on this.
Since May 28, 2025.
enhancement
- Dominant language
- Python
- Stars
- 159
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Description of feature
Once we merged #228, #235, #239, #240, we can start with the torch backend implementation. Therefore
- we will keep one
CellFlowclass for both backends - have a
src/backends/jaxand asrc/backends/torchdirectory CellFlow.prepare_modelwill have an argumentbackend: Literal["jax", "torch"]- for now, let's not implement GENOT for torch, let's just go with
OTFlowMatching, to keep things simple- - the only problem which arises is that
prepare_modeltakes backend-specific arguments, namelymatch_fn,optimizer, andvf_act_fn.
For the last point, I see the following as the best solution
allow passing both jax and torch instances, setting per default None , describe the default in the docs, and eventually instantiating them later in the solver classes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.