You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the excellent work on flask-split. At this point, the /split route is bailing out with this error. Let me know if you have any insights. I've got the latest version from pip.
2013-05-17T12:10:04.083015+00:00 app[web.1]:
2013-05-17T12:10:04.083146+00:00 app[web.1]: File "/app/.heroku/python/lib/python2.7/site-packages/jinja2/environment.py", line 372, in getattr
2013-05-17T12:10:04.083290+00:00 app[web.1]: return getattr(obj, attribute)
2013-05-17T12:10:04.083378+00:00 app[web.1]: File "/app/.heroku/python/lib/python2.7/site-packages/flask_split/models.py", line 110, in z_score
2013-05-17T12:10:04.083477+00:00 app[web.1]: return mean / sqrt(var_cr + var_crc)
2013-05-17T12:10:04.083572+00:00 app[web.1]: ValueError: math domain error
It seems that var_cr + var_crc is negative in your case, which causes sqrt to raise ValueError. I don't know how this is possible since both var_cr and var_crc should always be positive. Can you check what are the values of cr, crc, n and nc variables in z_score property, when this error is raised?
The problem seems to be that your control alternative has more completions (31) than participations (3), which leads to crc not being between 0 and 1. I guess the reason for that is that finished() does not somehow mark the experiment as finished or the session is not saved after being modified.
I would appreciate if you could either debug finished() and check if the experiment is properly being saved to the 'split_finished' in session, or provide a minimal code that introduces this bug.
Hmm OK. Does the module take care of ensuring repeat calls to finish don't
inflate the counts or do these need to be managed so they match the ab
calls? Users may be refreshing the finish page.
On May 18, 2013 1:23 PM, "Janne Vanhala" notifications@github.com wrote:
The problem seems to be that your control alternative has more completions
(31) than participations (3), which leads to crc not being between 0 and
I guess the reason for that is that finished() does not somehow mark
the experiment as finished or the session is not saved after being
modified.
I would appreciate if you could either debug finished() and check if the
experiment is properly being saved to the 'split_finished' in session, or
provide a minimal code that introduces this bug.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-18096807
.
Activity
jpvanhal commentedon May 17, 2013
It seems that
var_cr + var_crcis negative in your case, which causessqrtto raiseValueError. I don't know how this is possible since bothvar_crandvar_crcshould always be positive. Can you check what are the values ofcr,crc,nandncvariables inz_scoreproperty, when this error is raised?arg0s commentedon May 17, 2013
Here you go. Let me know if you need more details.
jpvanhal commentedon May 18, 2013
The problem seems to be that your control alternative has more completions (31) than participations (3), which leads to
crcnot being between 0 and 1. I guess the reason for that is thatfinished()does not somehow mark the experiment as finished or the session is not saved after being modified.I would appreciate if you could either debug
finished()and check if the experiment is properly being saved to the 'split_finished' in session, or provide a minimal code that introduces this bug.arg0s commentedon May 18, 2013
Hmm OK. Does the module take care of ensuring repeat calls to finish don't
inflate the counts or do these need to be managed so they match the ab
calls? Users may be refreshing the finish page.
On May 18, 2013 1:23 PM, "Janne Vanhala" notifications@github.com wrote:
jpvanhal commentedon May 18, 2013
Yes, the module does take care that repeating calls to finish don't inflate the counts.
arg0s commentedon May 18, 2013
Got it. If its fine can I have your IRC handle? I'll ping you when I'm home
and we can figure this out.
Arvi
On May 18, 2013 1:45 PM, "Janne Vanhala" notifications@github.com wrote:
NickWoodhams commentedon Apr 28, 2015
Still have this error in some circumstances. Appears the user conversion tracking may be screwing up the math. Did you solve previously?