-
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
Fix Factorial2 #308
Comments
@Ali-Tehrani is this also going to be an issue in |
I doubt it will be a problem at all, since GBasis will only go up to like 7-11!! and the performance advantages from vectorization are much greater |
Sorry to bother you after all this time. I've been really busy. I apologize for asking you this now, but could you please explain to me how I can use a file test from 'iodata/test' ? I initially thought it was a problem because the 'setup.py' was in the root directory of the project. So, I attempted this command instead: 'python3 -m iodata.test.common.py', but unfortunately, it didn't work either. Once again I am sorry to asking you this @Ali-Tehrani |
No worries, if you want to run in the format you specified, you should be removing the .py and be in the
However, I would recommend to use
Adding |
The most recent merged pull-request causes 165 tests to fail in Github Actions for various python systems. The following error is obtained for the vast majority of them:
Further the following line does not match scipy.factorial2 API. Looking at the earlier release of this package, we want
exact=True
in scipy.factorial2. When settingexact=True
, then scipy.factorial2 only accepts integers, and so we will need to run it over each individual element of the array.The solution would be too in
factorial2
function:out = scipy.special.factorial2(np.array(n), exact=exact)
when exact=Falsei. Add if n is not
int
, then convert it to arrayn = np.array([n])
)ii. compute
scipy.special.factorial2(x, exact)
on each individual elementx
of the arrayn
.Thank you to @LudoRNLT and @D-TheProgrammer, if you got the time to look into this.
The text was updated successfully, but these errors were encountered: