-
Notifications
You must be signed in to change notification settings - Fork 48
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
Issues related to factorial2 function #303
Comments
Yes, the documentation is embarrassingly bad. It took me a bit of time to remember how the integral works. It would have helped if we would have documented it. The integral is but before this funtion is invoked the Gaussian product rule has been invoked, and the utility variable was defined. Then the constant prefactor is factored out. (At least these utility variables are relatively clearly). So this function actually computes Then, using the standard Gaussian integral formula, We have: Realistically, this is overcomplicated: IMO some of the things we did to "save evaluations in the inner loop" were probably not worth the loss in readability, and at least demanded more documentation. It also seems to me that the double-factorial we are using is off by one, but I can't imagine how we managed to pass the old tests if that is the case, so I must be missing something. |
Sorry, forgot to mention that this is fixed in #319 |
The issue with the
factorial2
function persists, as the GitHub test workflow fails.Additionally, the second argument of
factorial2
is of bool type. The following usage offactorial2
is quite confusing:iodata/iodata/overlap.py
Lines 225 to 243 in 6b9c6e0
The text was updated successfully, but these errors were encountered: