Why Clinical Laboratorians Should Embrace the R Programming Language
1–10 of 62 posts
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#2Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#3That said, R had come a long way in recent years and is enjoyable to use. It is very complete as far as statistics go.
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#4I would say you could replace R with Python or Julia and do just fine. Anything must be better than SPSS. That said, R had come a long way in recent years and is enjoyable to use. It is very complete as far as statistics go.
If you like to write lots of code, Python might be better. But if you use it in clinical research, R has probably better packages for whatever you need.
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#5I would say you could replace R with Python or Julia and do just fine. Anything must be better than SPSS. That said, R had come a long way in recent years and is enjoyable to use. It is very complete as far as statistics go.
IME, for production Python rules and for data exploration, graphics, stats and adhoc analysis R rules.
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#6 > Unlike Excel and many other graphical user interface (GUI)-based programs, R’s reliance on text-based structure makes it straightforward to review at any time the commands used in a data processing pipeline to ensure that the correct steps were taken.
> Furthermore, the ability to view the underlying commands facilitates transparency and reproducibility of analyses.
The article seems to be targeted at people with zero programming knowledge. The arguments here are valid, but don't rely on R.
The title could just have been ".... Should Embrace a Programming Language".Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#7Conventional programmers seem to be somewhat reluctant to learn R's syntax and adjust their programming model.
Non-programmer types think in maths even less so they like the python "straightforwardness".
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#8> Unlike Excel and many other graphical user interface (GUI)-based programs, R’s reliance on text-based structure makes it straightforward to review at any time the commands used in a data processing pipeline to ensure that the correct steps were taken. > Furthermore, the ability to view the underlying commands facilitates transparency and reproducibility of analyses. The article seems to be targeted at people with z…
But it's very powerful, it's exactly right for these use cases and its ecosystem is mindbogglingly huge. Also, it tends to be easier to grasp for folks who don't have prior programming knowledge (anecdotal, but I've seen people pick it up very quickly who struggled a lot with, say, Python. And Python is the only language/ecosystem that comes close to R.)
So, yeah, a lot of languages could be used for the use cases in TFA, but R is uniquely suited, weaknesses notwithstanding.
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#9* I can't quite get htmlwidgets and docx formats to work together in bookdown without using separate commands for the interactive tables (DT and flextable).
Re: Why Clinical Laboratorians Should Embrace the R Programming Language
#10I would say you could replace R with Python or Julia and do just fine. Anything must be better than SPSS. That said, R had come a long way in recent years and is enjoyable to use. It is very complete as far as statistics go.
I think that R libraries have edge over Python and Julia in quality and quantity. If you like to write lots of code, Python might be better. But if you use it in clinical research, R has probably better packages for whatever you need.
Python gets scrutiny but most packages are on github and feedback can be received. Although, you should read the source code regardless.
EDIT: And I re-emphasize -- never trust the source code, even if the company you work with indemnifies. One commercial product we used in particular had an insidious bug in one of the new time series packages that got corrected with in later versions, but we never would have found it if model testing requirements didn't also require implementing in R or Python. Since the package didn't exist for Python, and we wrote it ourselves, we found the performance issues.