Optix is a great little library! But my weak opinion is that it should be in its own repo, for these weak reasons:

no JAX core devs are very familiar with the code and we have no vision for it, and so it's not something we could easily maintain or develop (i.e. we're relying on @mtthss) which makes it different from the other code in the JAX repo;
fixes and improvements by @mtthss, @tomhennigan, and others have to be merged into this repo by JAX core devs, which slows progress when we're slow to respond (@mtthss is relying on us);
issues like this one incur a small but nonzero time cost for the JAX core team.

Those are only weak reasons because the code is so concise and currently low-velocity. If the code were big, or being developed rapidly, we'd have already felt the pain and decided to move it out (or never merged it at all). But perhaps regardless of size the same principles could be applied.

If it were deemed too small to be in its own repo (though it's not clear to me there is such a minimum size!), it's not clear to me whether it's better to be bundled with JAX or with, say, Haiku.

Overall, though, I want to do whatever is best for @tomhennigan and @mtthss because this isn't costing us much. Even though my weak opinion is that it should be taken out of JAX, I defer to your judgement. (Though if you're ambivalent, we'll take it out!)

(By the way, #1620 is where it got merged, but there doesn't seem to be a relevant discussion in that PR thread.)

Optix documentation #2297

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions