[R] Fwd: Please help(immediate) - How to simulate transactional data for reliability/survival analysis

Bert Gunter bgunter.4567 at gmail.com
Wed Jun 28 05:53:05 CEST 2017


There is no member id. Anyone can sign up to post on this list. I
already responded to your prior post.

-- Bert


Bert Gunter

"The trouble with having an open mind is that people keep coming along
and sticking things into it."
-- Opus (aka Berkeley Breathed in his "Bloom County" comic strip )


On Tue, Jun 27, 2017 at 8:20 PM, Sunny Singha
<sunnysingha.analytics at gmail.com> wrote:
> I apologise as I had mistakenly posted this message via non- member mail. So I'm reposting it with member id. I need help in this case.
>
>> Hi friends,
>> I haven't done such a simulation before and any help would be greatly appreciated. I need your guidance.
>>
>> I need to simulate end to end data for Reliability/survival analysis of a Pump ,with correlation in place, that is at 'Transactional level' or at the granularity of time-minutes, where each observation is a reading captured via Pump's sensors each minute.
>> Once transactional data is prepared I Then need to summarise above data for reliability/ survival analysis.
>>
>> To begin with below is the transactional data format that i want prepare:
>> Pump-id| Timestamp | temp | vibration | suction pressure| discharge pressure | Flow
>>
>> Above transactional data has to be prepared with below failure modes
>> Defects :
>> (1)    Cavitation – very high in frequency but low impact
>> (2)    Bearing Damage – very low in frequency but high impact
>> (3)    Worn Shaft – medium frequency but medium impact
>>
>> I have used survsim package but that's not what I need here.
>> Please help and guide.
>>
>> Regards,
>> Sandeep
>>
>
> ______________________________________________
> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.



More information about the R-help mailing list