search

tapios / risk-networks

Code for risk networks: a blend of compartmental models, graphs, data assimilation and semi-supervised learning
Other
2 stars 2 forks source link

Package name "epiforecast" may be a misnomer #73

Open glwagner opened 4 years ago

glwagner commented 4 years ago

As discussed elsewhere, the name epiforecast may be a misnomer --- the main functionality of our package does not provide forecasting, due to the fact that the contact network cannot be inferred.

It's relative easy to change the name so this is not urgent. But, good ideas as they come up can be left here.

It's been mentioned that the name should evoke the concept of "risk".

Possible starting points: epirisk, epitrace, risktracer, safecontact...

tapios commented 4 years ago

How about something with safe in it? E.g., Episafe? Or with choice? (I'd like to emphasize the individual aspects.)

odunbar commented 4 years ago

I guess in reality we have 2 pieces: the epidemic simulator, and the "app based" data assimilator. Raff seemed to enjoy the name "MyCovidRisk", or more general variants such as "MyVirusRisk" or "MyContactRisk" could work the app part - as this provides users with a personal risk. If we were really sure we could be effective with the interventions, we could probabily use words like "safe/protect/shield", like "MyVirusShield".

We could name the simulator as EpiSim, or something? - as really this part would eventually be replaced by real data.

lubo93 commented 4 years ago

I like the suggestion to use two names. MyCovidRisk and EpiSim are good candidates :)