Stats

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

Question regarding data read and write in Ocean/Skill

Yasso

Hello! 

I have a question regarding the data read and write in ocean using skill. Currently I simulate different matrix of pixels and in each simulation I have to read a voltage. When the matrix is 320x240 the data write is slow, the simulation can be 30 mins but the data takes 2 hours into writing. I'll post the code here. My version of cadence is 6.1.8-64b (2018)

File = outfile("File.txt" "w")
for(i 1 76800
sprintf(g "/I%d/Vp" i)
ocnPrint(?output File  value(VT(g) 30m) ?numberNotation 'none)
)

close(File )

Takes way too long when you have bigger matrix, the values reported in the .txt are good and that's why I still use it but for the long run I'd like it to be quicker. What I understand is that ADE writes each value when the loop starts and ends. Is there a way of doing this faster? for example printf doesnt do it quicker. Thanks for the help in advance.

PS: I made a question not long ago (1month~) and still can't figure how to do it in ocean, any help would be appreciated 

community.cadence.com/.../save-data-for-each-iteration-monte-carlo-using-ocean

Parents

  • The issue is likely to be the time taken to read the entire waveform using VT() or to find the value at 30m - if there are a very large number of points in the transient waveform, then the data will take a long time to read in and a long time to search for the value at that time.

    One way to make this much quicker could be to directly write it from the simulator. You can do this by defining an info analysis - in ADE this would be done on the Outputs->Save All and adding a row like this:

    which would be equivalent to adding an entry in a spectre file with this syntax:

    snapshot info what=oppoint optype=ic where=file file="snapshot.txt"

    Then on the transient analysis, you can set infotimes=30m and infoname=snapshot (on the Output tab of the transient options form). If the file is not a full path, it will write it into the netlist directory.

    It will include all nodes in the circuit, not just those you want, but a simple bit of post-processing of the text file using perl, python or even just grep would give you what you want quickly I think?

    Finding a faster way with OCEAN probably needs a better understanding of quite where the performance limits are currently, and for that you should contact customer support.

    Regards,

    Andrew

  • in reply to Andrew Beckett

    Thanks! Now it generates a 2gb file, and I could process the text to extract the data I find necesary. It takes 10 min of writting instead of 2~3 hours. One last thing, I can't contact directly with customer support (I have an EuroPractice license, and first I'd need to contact them through my work IT service), that's why the forum helps me a lot in these kind of situations. 

    PS: Could you lend me a hand with the question I have about the Monte Carlo analysis attached? If it is possible of course, I posted it a while ago, and I can't find it to work properly.

    Thanks again and best regards,

    Yassin

Reply
  • in reply to Andrew Beckett

    Thanks! Now it generates a 2gb file, and I could process the text to extract the data I find necesary. It takes 10 min of writting instead of 2~3 hours. One last thing, I can't contact directly with customer support (I have an EuroPractice license, and first I'd need to contact them through my work IT service), that's why the forum helps me a lot in these kind of situations. 

    PS: Could you lend me a hand with the question I have about the Monte Carlo analysis attached? If it is possible of course, I posted it a while ago, and I can't find it to work properly.

    Thanks again and best regards,

    Yassin

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.