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.

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

Soss-compatibility with Jaynes #155

Open
femtomc opened this issue Jul 7, 2020 · 0 comments
Open

Soss-compatibility with Jaynes #155

femtomc opened this issue Jul 7, 2020 · 0 comments

Comments

@femtomc
Copy link

femtomc commented Jul 7, 2020

I've been experimenting with IR metaprogramming for constructing a dynamic tracer in Jaynes. This has provided a rather nice way to express "foreign model interfaces" - e.g. here.

The primary abstraction for any function call is a CallSite: https://github.com/femtomc/Jaynes.jl/blob/3642553fa628eda0d08e0ab1ad828856cb73bd41/src/trace.jl#L43-L47

I think I could rather easily extend the tracer to support a SossCallSite which wraps a Soss model and then express the correct semantics in the execution contexts of my system to do the right thing, depending on what the user is trying to do.

This issue does not require work on the side of the Soss team - instead it's just a reference issue as I experiment with making compatibility work between the three main PPLs (Gen, Soss, Turing) in this IR infrastructure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant