Jan

> Sure, it is `/sbi/tests/torchutils_test.py:219` > > ``` > ...............xxxx......x............................................................................................. [100%] > ============================================================ FAILURES ============================================================ > ___________________________________________________ test_process_device[cuda] ____________________________________________________ > > device_input = 'cuda' > > @pytest.mark.parametrize("device_input", ("cpu", "gpu", "cuda",...

Hi @h3jia thanks for the issue. There is no option pass a custom `DataLoader` to `append_simulations` unfortunately. In `append_simulations` the data is stored internally and only on the call to...

will be closed by #766

It is now possible to use a custom data loader by using the training interface, see tutorial 18.

Thanks for the update and no worries at all @danielmk! Yes, as part of the Google Summer of Code, @abelaba was able to start working on this. Initially, we aimed...

Yes, that's a good idea @plcrodrigues! This issue here is more a collection of many different issues. Please create a separate one for improving the contribution guidelines, or create PR...

Many points in this issue have been solved. Here is a checklist for closing it before the release: These fixes should probably go into #1147 - [x] update papers, e.g.,...

closed with #1232

yes, correct. The reason that the custom `potential_fn` has `theta` and `x_o` as args is that quantities are required to calculate the "potential", i.e., the unnormalized posterior probability. For the...

> Is this tested somewhere? I only found examples where the argument is of type `BasePotential`. Yes, I had to dig a bit as well, but it's tested here: https://github.com/sbi-dev/sbi/blob/593e1533738bdc9c747d50f502f7c1a47bf94248/tests/potential_test.py#L28-L37...