-
Notifications
You must be signed in to change notification settings - Fork 3
/
ABAlternative.cs
88 lines (76 loc) · 2.19 KB
/
ABAlternative.cs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
using System.Xml.Serialization;
namespace ABTesting
{
public class ABAlternative
{
public string Content { get; set; }
public int Participants { get; set; }
public int Conversions { get; set; }
/// <summary>
/// Alias for "Participants".
/// </summary>
public int Successes
{
get
{
return Conversions;
}
}
/// <summary>
/// Alias for "Participants - Conversions".
/// </summary>
public int Failures
{
get
{
return Participants - Conversions;
}
}
[XmlIgnore]
public int Index { get; set; }
/// <summary>
/// In statistics, we'd call this the success proportion.
/// </summary>
public double ConversionRate
{
get
{
int p = Participants;
return p == 0d ? 0d : (double)Conversions / p;
}
}
public string PrettyConversionRate
{
get { return (ConversionRate*100).ToString("0.##") + "%"; }
}
public ABAlternative()
{
}
public ABAlternative(string content)
{
Content = content;
}
public void ScoreParticipation()
{
Participants++;
}
public void ScoreConversion()
{
Conversions++;
}
/// <summary>
/// If this alternative (ie: sample) has at least 10 failures and 10 successes, then the sample size assumption of the two-proportion z-test is satisfied.
/// </summary>
public bool SampleMeetsTestAssumtions
{
get
{
//CF:If we wanted to get really strict about this, we could move this into the Experiment class and compute the pooled expected failure/success rate
//to accomodate the case where we may have one alternative with low success rates. See the Gardasil/HPV example in "Intro Stats" page 566.
//For our needs, checking for 10 success & failures seems fine.
return Successes >= 10 && Failures >= 10;
}
}
}
}