Closed mdhaber closed 1 year ago
What is the best way to handle that in _info.py? a is really the third argument in Boost's implementation.
The codegen as is assumes (incorrectly) that the positional arguments will align from boost -> scipy. This doesn't seem like too much of an issue though, as you can simply reorder the arguments in the rv_continuous/discrete methods when they get called
The other arguments aren't used, so I just gave them names that never get used in the code.
@mckib2 Boost's skewnorm distribution accepts
location
andscale
. What is the best way to handle that in_info.py
?a
is really the third argument in Boost's implementation.