MeasureTransport / MeasureTransport/MParT

Overhaul `MultivariateExpansion`

Open
#338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
18
Forks
5
PR merge metrics
No merged PRs in 30d

Description

This is now an old conversation, but in 1.0 we (matt) figured out how to create maps that were efficient to evaluate and invert. In 2.0 I mostly focused on creating the ability to train and research uses of maps. In the future (e.g. 3.0) I want to get it to a point where we are able to research and experiment with different parameterizations of the maps themselves (this was elegantly put by Matt in our last conversation).

This entails making MultivariateExpansion and the like more friendly to tweak and call from the binding language and, additionally, creating the ability to call the binding language from C++ for univariate or multivariate members of the expansion. Then, we don't have to worry as much about implementing things in straight C++ efficiently the first time around, and we can really experiment with different abilities. As an example, it would be really cool/nice to be able to just throw in a Pytorch/Tensorflow neural network in a component and be able to use it for our map.

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are named. Start by reviewing MultivariateExpansion and the binding-language interface, then map the required C++ call paths for univariate and multivariate members. Done means parameterizations are easier to experiment with and binding-language calls can be made from C++.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.