Stats

  • Locked Locked
  • Replies 7
  • Subscribers 144
  • Views 19145
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ipcBeginprocess!

imagesensor123

hi, 

  I write a skill function to collect some simulation information, it shows like the following code

procedure(zfGetBeginTime()
readBeginTimeIpc=ipcBeginProcess("date")
simulationBeginTime=ipcReadProcess(readBeginTimeIpc)
fp=outfile("~/skill/timeConsumption.out")
fprintf(fp "%s " simulationBeginTime)
close(fp)
)

but, i found that, i can get the right info if i type these command in CIW one by one. i will get only "t" in the file(pointer) if i run this procedure in CIW, i can't understand it, so please give me some advice if you know this.

Regards,

zfeng

Parents
  • Andrew Beckett

    Didn't you just answer this yourself? ipcIsActiveProcess tells you whether it is running (and not stopped). ipcIsAliveProcess() tells you whether it is running at all (even if stopped - by stopped I mean has been sent a STOP signal - as would happen if you called ipcStopProcess(); if you call that, the process is not active, but is alive).

    It doesn't matter whether the process has been completed via you closing the window or ipcKillProcess being called - in both cases it ends.

    If you use the asynchronous approach with ipcBeginProcess() - i.e. you pass a data, error and exit handler function name, the exit handler will be invoked when the process ends (however it ends).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Didn't you just answer this yourself? ipcIsActiveProcess tells you whether it is running (and not stopped). ipcIsAliveProcess() tells you whether it is running at all (even if stopped - by stopped I mean has been sent a STOP signal - as would happen if you called ipcStopProcess(); if you call that, the process is not active, but is alive).

    It doesn't matter whether the process has been completed via you closing the window or ipcKillProcess being called - in both cases it ends.

    If you use the asynchronous approach with ipcBeginProcess() - i.e. you pass a data, error and exit handler function name, the exit handler will be invoked when the process ends (however it ends).

    Regards,

    Andrew.

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.