This message was deleted.
# announcementsw
worried-planet-2191
08/14/2023, 4:59 AMThis message was deleted.
f
fresh-football-47124
08/14/2023, 5:37 AM
it could be caused by the assignment attribute of the experiment being different than the assignment in the experiment report
fresh-football-47124
08/14/2023, 5:37 AM
but usually they are caused by changing of the split mid experiment
l
loud-hydrogen-50191
08/14/2023, 5:46 AMhi @fresh-football-47124 thanks for the quick reply.
I have checked that
1. the hashed attribute did not change,
2. the experiment start time is above the last feature change i can see in the audit log.
3. split was not modified
f
fresh-football-47124
08/14/2023, 7:01 AM
what split do you have?
l
loud-hydrogen-50191
08/14/2023, 8:38 AMhi Graham, sorry for the late reply, it's 50/50
Copy code
{
"defaultValue": false,
"rules": [
{
"condition": {
"deviceId": "test-forced-on"
},
"force": true
},
{
"condition": {
"loginStatus": 0
},
"variations": [
false,
true
],
"coverage": 1,
"weights": [
0.5,
0.5
],
"key": "MyExptKey",
"hashAttribute": "deviceId"
}
]
}loud-hydrogen-50191
08/14/2023, 8:45 AM Copy code
Warning: Sample Ratio Mismatch (SRM) detected. We expected a 50/50 split, but observed a 50.4/49.6 split (p-value = 9.2e-7). There is likely a bug in the implementation.count, main_sum, main_sum_square140 Views