Cwa-documentation: How were some of the parameters decided on?

Created on 24 Jun 2020  路  3Comments  路  Source: corona-warn-app/cwa-documentation

Consolidation

After prodding a bit in #229, #256, #257, #307, we get some more information about how and where the parameter values are set in the code:

Background

The configuration of CoronaWarn, as described in the solution architecture document, leverages two parts of the GAEN API: an "Exposure Score" (based on a per exposure summary) and a "Normalized Total Risk Score" (based on an aggregate) to calculate the risk. The interesting bit is that SwissCovid relies on the first, while Immuni relies on the second. So in a perfect world, each component of this risk score would match each of those other deployments (no?).

Remark

We still don't have clarity (#307) on the bold part of

All exposures for a diagnosis key that lasted less than 10 minutes in total (regardless of how close the smartphones came during that time) or during which the smartphones were more than 8 meters (73 dB attenuation) apart on average (regardless of how long the exposure lasted) are discarded as harmless.

except that this line is probably the mean this is achieved.

Questions

I still have a few questions though:

  1. why is there this clipping at 73dB "on average"? what does "on average" mean? (this was #307, left unaddressed there, even though the issue is now closed)
  2. why isn't the weight 0 for exposures between 10 and 15 minutes? This differs from the Immuni configuration, for instance (this is https://github.com/corona-warn-app/cwa-server/issues/601 on the server repo)
  3. what are the app_defined factors? what do they mean, beyond a numeric value of risk?
  4. what is the idea behind the deault-bucket-offset (currently set to 0, not really explained in the solution architecture)
  5. given that default-bucket-offset is 0, I would have expected that your configuration of attenuationThresholds should match the Swiss one for that part, but it differs significantly. With the same weights as you of [1, 0.5, 0], they chose [50, 55] while you chose [55, 63]. Given what I said in the Background above, I am very surprised by this difference. What am I missing?
  6. How was the Risk Score classification threshold value of 15 chosen?
  7. what does "the attenuation is weighted by the duration at each risk level and averaged for the overall duration" mean?

In general we can now tell where each factor is set, and what the value is, but not _how_ it was decided to set it to that value (even once the solution architecture was chosen). The risk scoring documentation does not answer those questions either.

question

All 3 comments

Dear @pdehaye,

I'm sorry that I forgot to update all references in the respective issues to the central cwa-wishlist issue that I explicitly reopened yesterday to address these open questions. As the other issue was opened earlier and especially has seen quite an interesting discussion already, I copied your detailed questions over to the other issue so that we can address them altogether. I hope that is OK for you!

Mit freundlichen Gr眉脽en/Best regards,
SW
Corona Warn-App Open Source Team

See also my attempts in the PR #320 to link these into the documents. @SebastianWolf-SAP What's the workflow regarding such PR's. Haven't heard anything from your team about it?

The workflow is that for major improvements, we first need to have a handshake via a GitHub issue that somebody can work on that. Otherwise there might be the problem that people work on things which we are not able to change or only very hard as legal discussions are needed. See also the README:

We appreciate feedback to all elements of this project scope document. However, additional features or any other content changes beyond fixes to grammatical issues or typos need to be aligned on by these partners before they can be included in the document. Thank you for your understanding!

We definitely need to communicate that more explicitly for example like already done in the iOS and Android repositories: https://github.com/corona-warn-app/cwa-app-ios/blob/develop/.github/pull_request_template.md

Our team will keep you updated. We will tackle the open issues and PRs over the next days/next week with respective answers. Thanks for your understanding that things simply take their time and we want to give proper answers to everybody.

Mit freundlichen Gr眉脽en/Best regards,
SW
Corona Warn-App Open Source Team

Was this page helpful?
0 / 5 - 0 ratings