\documentclass{article}
\title{Natural selection in the Health and Retirement Study}
\author{XXX}
\date{September 2023}
\begin{document}
\maketitle
\begin{abstract}
I investigate natural selection on polygenic scores in the contemporary US, using the Health and Retirement Study.
Results partially support the economic theory of fertility as an explanation for natural selection: among both white and black respondents, scores which correlate negatively (positively) with education are selected for (against).
Selection coefficients are larger among low-income and unmarried parents, but not among younger parents or those with less education.
I also estimate effect sizes corrected for noise in the polygenic scores.
\end{abstract}
\end{document}
I grew up in Greater Manchester, a heavily-industrialised part of the UK, where locally the main industries were at one time coal mining and cotton milling. Members of my family worked in cotton mills, and the machines were so deafening that normal communication was impossible. Consequently, mill workers invented their own forms of communication, which mixed hand signals, exaggerated lip movement, and shouting, which was locally called "meemawing". This communication form was specific to each mill, and workers moving between mills would have to relearn the mill-specific dialect to be able to meemaw with their colleagues.
> It turns out that it is possible if you do it in a special way with locales
What was special about it? From memory, the formalisation [1] proceeded exactly how you would expect. Locales are simply an Isabelle mechanism (in addition to type classes) through which hierarchies of structures are built up.
Ha, I'm not sure! I just write papers, the vagaries of how and why journals and conference proceedings are published the way that they are is beyond my ken. Looking back through some of my other papers it seems that there's a mix --- some styles do include a date, especially those provided by the ACM, whilst others don't, including IEEE TPDS which is where the paper above is published. Who knows?
Arm Research | Security Technical Lead | Cambridge, UK | Fulltime, Onsite
Arm Research’s Security group is tasked with securing the Arm architecture, developing new security-related technology, and keeping the rest of Arm informed of current and developing security-related technologies and trends. We currently consist of 15 permanent members split between Cambridge (UK), Austin (TX), and Austria, plus interns.
The group has many exciting research projects tackling security problems in both hardware, software, and the interface of the two: for example, we have ongoing research projects in distributed systems’ security, privacy-preserving compute, edge security, secure firmware update, the design of remote attestation protocols, the efficient implementation of post-quantum cryptography, and the design of secure hardware debug mechanisms. Recently-completed research projects include the verification of low-level security-critical firmware, the checking of information-flow properties in the Arm M-class architecture, and the design of policy languages for distributed systems’ security.
Group members use a range of cutting-edge technologies including Rust, seL4, WASM, formal verification tools (e.g. the C bounded model checker, CBMC), and we have members active in standardisation bodies (e.g. the IETF). We work closely with groups from academia as well as Arm’s own product groups and other research groups within Arm Research.
We are currently looking for a new technical lead. The role would suit somebody with a broad interest in information security with deep expertise in one or more areas related to our research projects listed above. The successful candidate will guide the direction of the Security group, and the role therefore involves both technical and people-management aspects.
Interested parties are welcome to contact [email protected] for more information about the role.