Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13331
  • 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

Reading points from external script; data limit for ipcReadProcess?

patschouly

Hi,

I'm using ipc* functions to read points for a polygon (layout) from an external script. This works fine, however fails for larger amount of points. I can't boil it down to an exact number (however, it's not the 4000-polygon limit, it's before dbCreatePolygon). What could cause this and how could I solve this? Can I read line-by-line from the script?

Here is what I'm doing (the points are separated by semicolons):

 let(
        (
            pid str pts
        )
        pid = ipcBeginProcess("lua /path/to/script.lua")
        ipcWait(pid)
        str = ipcReadProcess(pid)
        foreach(elem parseString(str ";")
            pts = cons(evalstring(elem) pts)
        )
        dbCreatePolygon(geGetEditCellView() list("QB" "drawing") pts)
    )

Parents
  • Andrew Beckett

    Generally I would recommend that anything that needs to generate a lot of data and send via IPC, that you redirect the output to a file and then read the file. There have been long-standing issues with IPC (unfortunately never resolved) where the buffers overflow and you can lose data if lots of data is output.

    Andrew.

Reply
  • Andrew Beckett

    Generally I would recommend that anything that needs to generate a lot of data and send via IPC, that you redirect the output to a file and then read the file. There have been long-standing issues with IPC (unfortunately never resolved) where the buffers overflow and you can lose data if lots of data is output.

    Andrew.

Children
  • patschouly
    in reply to Andrew Beckett

    Ok, thanks for the insight. I'm now reading from a file, which works perfectly. Thank you for your fast reply.

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.