Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
son is forced to observe
I'm sorry to hear that. What level of education is that establishment supposed to provide? What would the son prefer to do instead?
The stuff is currently done less or more in R which is considered being pain in the ass.

There are probably faster ways of easing the pain in the ass than rewriting everything in Perl. After all, the math involved is complicated, so re-implementing it from scratch in likely to result in a lot of bugs, but it's already been done by a well-known member of the community and relied upon by a lot of people. R is a bit confusing after Perl because of its pass-by-value nature and generics-based OOP, but it can be written in all kinds of paradigms, and the CRAN code quality is really high, especially for packages reviewed by ROpenSci.

The end result is that the desired plot could be a one-liner in R, depending on the format of the available data and one package being installed: plot(survival::survfit(Surv(time, status) ~ x, data = read.table('data.txt')))

Care to share your frustrations? Or would you like to send a mail to the R-help mailing list? It's mostly friendly, like PerlMonks.


In reply to Re: Any perlish hints about Kaplan-Meier Estimator? by aitap
in thread Any perlish hints about Kaplan-Meier Estimator? by karlgoethebier

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (6)
As of 2024-04-26 08:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found