Chat message

Slack / Private Message Drop, p.968 [SLACK_001182] · slack_pm:msg:10086

Date: 2021-06-30 10:42
Type: chat message · slack
recipient: Kristian G. Andersen, Robert F. Garry, Edward C. Holmes
speaker: Andrew Rambaut

Recipients on this medium are inferred from channel membership, not per-message addressing.

I am thinking for the figure a simple two panel with the tree rooted between A and B and the map with the cases onit. We can link them up using colours.

In context

A single line often inverts meaning once you see what it answers, so neighbouring messages are always shown.

2021-06-30 10:20 Robert F. Garry open

Perhaps, word version and request that they use track changes probably works the best. Old school. You can do the same with Google docs obviously but when ten or more ppl get to making changes as we've seen now about 5X itgets unwieldy.
2021-06-30 10:36 Andrew Rambaut open

Personally I find it much worse when I get 10 word documents with track changes on and have to merge them.
2021-06-30 10:37 Andrew Rambaut open

I have created a PDF version with a code in the DOI of the last reference. [shared file(s): Image from iOS.jpg]
2021-06-30 10:39 Andrew Rambaut open

But I may be a bit paranoid
2021-06-30 10:42 Andrew Rambaut

I am thinking for the figure a simple two panel with the tree rooted between A and B and the map with the cases onit. We can link them up using colours.
2021-06-30 10:44 Kristian G. Andersen open

Sounds good about the figure - keep it simple. Possible to shade the excess deaths on the map too? Issue with cases is that people will say there was a sampling bias towards the market.
2021-06-30 10:46 Kristian G. Andersen open

Excess deaths is simple data [shared file(s): Screen Shot 2021-06-23 at 09.59.57.png]

Full conversation →