Magnus Dehli Vigeland

My book is out!! 🎉 Relatedness analysis, IBD simulations, linkage and much more - all with background theory and easy-to-follow R code. Written in @rstudio with {bookdown}.🙏 #rstats #statisticalgenetics #forensicscience elsevier.com/books/pedigree…

@darielab Yes, this was already on the todo list. As of yesterday QuickPed has a "miscarriage" button! 🙂

@mdvigeland Would be awesome to be able to add symbols for spontaneous abortions as those are frequent in most pedigrees.

My pedigree & relatedness tool is published!🎉 bmcbioinformatics.biomedcentral.com/articles/10.11… #rstats #shiny

We are so proud of our new PhD and her excellent defence today🎉 Public Defence: Maria Dehli Vigeland med.uio.no/klinmed/englis…

Update: Whatever caused this, it seems to be fixed in R 4.3.1.

Could this be a bug in R 4.3.0? I just checked that R 4.2.2 gives the expected error: "object 'fakevar' not found".

Can anyone explain this weird #rstats error message? (The actual problem is of course that `fakevar` doesn't exist.)

@JulienMouchnino Sure: f = function(...) list(...)[fakevar] f(foo = "bar")

@mdvigeland Could you paste the code in plain text in a tweet?

@Nico_Metocean Thanks!

@Nico_Metocean (Same as you, I mean...)

@Nico_Metocean Do you have R 4.2.2 (or older)? I get the same there.

@Nico_Metocean That's the error I would expect, but I'm not seeing it! I'm running R 4.3.0, fresh session, on Windows 10

@Fawwaz_mirzani The error message doesn't mention `fakevar` at all, that's what got me stumped for an hour... :)

@mdvigeland This error message is indicating that the variable 'fakevar' is not recognized or doesn't exist. To resolve this issue, you need to ensure that the variable name is spelled correctly and that it has been properly defined or assigned a value in your code.

Our big review paper on investigative genetic genealogy for FSI Genetics is now out. It was a pleasure to collaborate with Daniel Kling, @sifta and Andreas Tillmar on this. doi.org/10.1016/j.fsig… #geneticgenealogy #forensics #DNA

@_nicoromano_ Thanks. For example, suppose (a time consuming version of) this code has been run: layout(mat = rbind(c(1,2), c(3,3))) plot(1:5) plot(1:5) Is it now possible to split the 3rd panel before proceeding?

Dear #rstats people, I'm struggling with this: When using layout() to split the plot window, can the layout matrix be modified after the first frame has been plotted? So far, I'm stuck at "no", which is not the answer I'm looking for... 🫤

@nj_tierney Useful and well written.

Little post on a fun use of `dplyr::across()` njtierney.com/post/2022/08/0… #rstats #tidyverse #dplyr

Looking forward to talking about the math of juggling at #IMO2022 today! imo2022.org

So if you need a quick pedigree drawing, here is QuickPed to the rescue: magnusdv.shinyapps.io/quickped/

🎉 It's finally out: My guide on how to create a fixed color palette for #dataviz in organizations! I’ve never worked longer on and interviewed more people for an article: blog.datawrapper.de/colors-for-dat…

Bonsai: An efficient method for inferring large human pedigrees from genotype data New publication from the 23andMe Research Team now in @AJHGNews sciencedirect.com/science/articl…