MSAK calibration plan

[robertodauria]

With the goal of gathering data and facilitate comparison between MSAK and ndt7 data, we are running the MSAK test alongside ndt7 on speed.measurementlab.net. The expected configurations that we are going to run are:

• 1 BBR stream, 10s (2024-02-27 to 2024-06-13)
• 2 BBR streams, 10s (2024-06-13 to 2024-07-23)
• 1 BBR stream, 5s (2024-07-23 to 2024-10-16)
• 3 BBR streams, 10s (2024-10-16 to 2025-04-07)
• 1 cubic stream, 10s (2025-04-07 to 2026-06-22)
• 2 cubic streams, 10s (2026-06-22 to 2026-06-24; see MSAK calibration plan #77 (comment))
• 3 cubic streams, 10s (????-??-?? to ????-??-??)

[M-V-RAGHUPATHI-SAI]

Hey @robertodauria, i saw you added the Task label yesterday.

Since the 1 cubic stream has been collecting data since april 25, are we moving to 2 cubic streams, 10s run next?

I would be happy to update the client config (client.streams = 2). but if the M-Lab team prefers to handle these calibration changes internally, no worries at all, just let me know : )

[bassosimone]

As reported in #222, we discussed with @robertodauria and concluded that it was best to pause the MSAK calibration plan and analyze the existing data. This calibration has been running for too much time and has impacted the user experience. So, we want to restore the single-test user experience now. I am not going to close this issue for now, because keeping it open serves as a reminder for myself about the plan. This may change next time I do issue triage (and, yeah, I am writing this sentence being fully aware that there is a certain probability that next time I'll read it would be embarrassing 😬)