Skip to content

Validation of R

2 messages · Pikounis, Bill, Spencer Graves

#
Hi Rob,
Notwithstanding the disclaimer automatically appended below by my "Big
Pharma" member IT dept on all my email sends, I have not had this problem,
or perhaps more accurately, not allowed it to be a problem when work I have
done in R has made it into drug application filings and responses to FDA and
European regulatory agencies.

"Validation" of software is an ill-defined concept, so I am afraid I cannot
offer anything like a concrete "how-to", not would I be surprised if anyone
else can.  What I would like to suggest is to (1) ask your vendor companies
what specifically they are concerned about, (2) benchmark some guidelines on
how you all or others have "validated" other software.

If you are looking for extensive documentation on whats/hows/whys of R, it
already has it.  If you are looking for it to compute the same values as
"validated" software within realistic numeric accuracy for your procedures,
that is straightforward to do.  And the ultimate key is that anyone can look
at the source code and have a high probability to get it to run on any
reasonably current system, and even many systems not so current. 

On a visible, continuous (daily), *OPEN* basis, there is ongoing review and
input from the R user community, as well as all the highest standards of
software engineering that are met by the R core team and other developers. R
clearly stands up to rigorous, scholastic scrutiny. In my very grateful
view, this makes R at least as reliable as commercial vendor software that
claims "validation" or "compliance", etc., ...and probably, more reliable. 

Hope that helps.
Bill
----------------------------------------
Bill Pikounis, Ph.D.
Biometrics Research Department
Merck Research Laboratories
PO Box 2000, MailDrop RY84-16  
126 E. Lincoln Avenue
Rahway, New Jersey 07065-0900
USA

v_bill_pikounis at merck.com

Phone: 732 594 3913
Fax: 732 594 1565
#
Just to amplify on one of Bill Pikounis' remarks:  I found bugs with 
S-Plus code roughly 16 months ago.  I fixed them myself for my own use. 
  Legally, my modifications could go no further.  If I took the time to 
try to convince the Insightful developers that the bugs were worth 
fixing, they would consider my fixes of develop their own.  However, 
since I modified their functions, it would have been a violation of 
copyright law for me to distribute my fix any further.  If the bug had 
been in C or Fortran, I would have had to develop a correct replacement 
from scratch.

	  Open source is very different.  If I find a bug, I'm encouraged to 
program a fix and offer it to the world.

Spencer Graves
Pikounis, Bill wrote: