Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NetKet 3.3 now spits out a very innocuous warning when you set the number of samples to something that is not a multiple of the number of chains.
The logic is the same as before, we simply warn users that this is happening.
If you don't spceify the number of samples we'll pick the nearest multiple near 1000.
Since this looks like a book, I think it's nicer if users are not annoyed straight away.
I also took explicitly specify the dtype of Jastrow: if you use complex numbers you can describe signs and phases.
I don't speak russian, but in general we always try to stress that if you chose real parameters for your network you can only encode positive-valued states. It's a common source of questions in my experience.