There is a quarto-webr extension to do this. A bunch of real world examples are at https://quarto-webr.thecoatlessprofessor.com/qwebr-community...

An earlier attempt of this is http://csvy.org/, but AFAIK it has never really caught on.

One of the cancers they mention is pancreatic cancer.

A quick Google search suggests the prevalence of pancreatic cancer in the population is 13 per 100,000.

So if you gave this test with a 0.005 false positive rate and 0.5 true positive rate to 100,000 people it would miss diagnose 500 people and only correctly detect 7 cancers.

So given you had a positive test result there would be a 1-(7/500)=98.6% chance you did _not_ have pancreatic cancer.

Doesn't seem very useful in that light...

The false positive rate of 0.5% refers to the chance that there is ANY false positive in the whole screening, not just a false positive on the pancreatic cancer segment.

Does this take into account age?

The article says:

"The test, which is also being piloted by NHS England in the autumn, is aimed at people at higher risk of the disease including patients aged 50 or older"

The test is aimed at people over 50 were, sadly, the prevalence is much higher!

It seems like there are a number of other risk factors as well (see https://www.cancerresearchuk.org/health-professional/cancer-...), that could shrink the pool of people tested.

I use right assignment in this way all the time, you should try it Joe :)

FWIW `scan()` is going to be much faster if you are just reading doubles from standard input than `as.numeric(readLines())`.

1632[0] is the first in a series of entertaining alternate history novels, where an entire West Virginian town is transported to the middle of the Thirty Years war. It touches on some of these problems in having to translate modern knowledge to people in the past.

0: https://en.wikipedia.org/wiki/1632_(novel)

While it is true that S was originally a macro layer around FORTRAN code R has always been primarily written in C. Very little of R core is in FORTRAN, and essentially none of it is C++.

The language statistics show a good deal of FORTRAN (%24.5) [0], however that is largely skewed by the included LAPACK code [1], which accounts for 221,921 / 259,773 lines of FORTRAN in R.

[0]: https://github.com/wch/r-source [1]: https://github.com/wch/r-source/tree/trunk/src/modules/lapac...

> however that is largely skewed by the included LAPACK code

which is where most of your number crunching will be happening..

While the order of the walls in Super Hexagon is random, each level has a predetermined set of walls. Once you identify which wall pattern is coming you know exactly the maneuver needed to traverse it.

This makes Super Hexagon more a game of quick pattern recognition than reaction time.

When I play it I am generally focused at the edges of the screen to quickly identify the next pattern and only using my peripheral vision to maneuver around the walls in the center.

FWIW I have been using vim with Colemak for quite a few years now, with only movie remains needed to get movement back on the home row [0]

0: https://github.com/jimhester/dotfiles/blob/master/colemak/vi...

Dvorak users in this thread should really give Colemak [1] a try. Dvorak has a number of issues [2] in modern usage and is also harder to learn; many more keys change from their QWERTY equivalents.

I have used QWERTY, Dvorak and Colemak for multiple years and Colemak is the clearly the best of the there for me.

[1]: https://colemak.com/

[2]:https://colemak.com/FAQ#What.27s_wrong_with_the_Dvorak_layou...