-
Notifications
You must be signed in to change notification settings - Fork 161
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
Summarizing network / learned summary statistics #298
Comments
Linking to openjournals/joss-reviews#2505 for posterity |
Good point, thanks for raising this! It is indeed possible to use a trainable network by passing an This argument got lost from the the documentation page since we started using However, there are not yet any pre-configured nets yet and no examples yet. Both of these things are on our hot desk, and are also documented in #279. |
👋 I see that #299 is merged. I think the API documentation online is still the same. Once that API documentation is updated and exposes |
@michaeldeistler just want to make sure you see note above. |
Thanks, saw it. We'll make a new PyPI release soon (hopefully tomorrow) and then update the docs :) |
From the API documentation, it seems like the package is restricted to simulators that produce output
x
with a constant shape. I wondered about simulators that produce output of varying size and shape. Currently, it seems this would possible if one introduces a function that wraps the simulator to produce fixed length summary statistics. This was not immediately clear to me from the API documentation or the home page in the documentation.I do see that the Hodgkin-Huxley example does exactly this with domain-motivated summary statistics (as opposed to learned summary statistics).
However, the software paper mentions
I can see how this wold work with a pre-trained network that produces summary statistics, but my reading of that sentence with the word "trainable" is that SBI can also train the summarizing network. I haven't found this yet in the API documentation. If it is possible, an example would be great. Either way it would be nice to clarify this in the documentation and/or reword the sentence in the software paper.
The text was updated successfully, but these errors were encountered: