emm | A general monad for managing stacking effects | Functional Programming library

First, you a legend because you mapped on the size aes instead of using size as an argument, i.e. outside of aes(). Second, you get an error because arrow() has no size argument. See ?arrow.

Instead you could increase the size of the arrows like so:

This could be achieved via the aes argument of emmeans::pwpp which allows to set the size of labels, points and segments (see ?emmeans::pwpp):

To call the API you will need a GCP account as mentioned in the documentation you shared.

However this is only required to call the API. If ou want your application to be hosted on a different cloud that can work, just need the GCP account to generate the API key in order to use the Zero-touch API.

The different p-values you are seeing reflect unadjusted p-values vs p-values that were adjusted for multiple comparisons.

The ?emmeans::pairs documentation tells us:

Ordinarily, when simple is a list or "each", the return value is an emm_list object with each entry in correspondence with the entries of simple. However, with combine = TRUE, the elements are all combined into one family of contrasts in a single emmGrid object using rbind.emmGrid.. In that case, the adjust argument sets the adjustment method for the combined set of contrasts.

So, with your reproducible example, you can combine all the simple main effects into one data frame with the combine argument set to TRUE. And you can choose between unadjusted vs adjusted p-values by setting the adjust argument.

You will need a left join on hr_work_locations instead of inner join.

well, I do observe delay with between different users when updating any app - some of them will get an update in a hour, some will get stuck with old version (no update in Play Store) for hours, even more than a day. few years ago it was even few days, also on start of pandemia... so I guess this is how it just works, such big system (distributing lot of apps worldwide) need some time to process and propagate

PS. never used this app update mechanism, just described common way

You can broadcast alpha to 64-bit using scalar multiply with 0x0001000100010001ULL before copying to an MM reg. Another option would be to just zero-extend the 8-bit integer to 32-bit for movd, then pshufw to replicate it.

There were also various safety problems with your asm.

This is how I personally include Google Test in a clean way:

We can set up dataset with examples that work: