• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Is there a way to eliminate undesired data from a psfxl...

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 18270
  • 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

Is there a way to eliminate undesired data from a psfxl file to save area in a maestro output?

scottwatx
scottwatx over 5 years ago

I'm running 6.1.7, and I inadvertently ran a long corner sweep with "save all".  I now have 600 corners with 500MB psfxl files each.  I only use about 6 or 8 waveforms from each corner to create my output eexpressions.  Resetting up and rerunning the test is infeasible.  Is there a way I can save out those key outputs, and delete the rest from the psfxl file, so that I can still reference the data from maestro assember without maintaining 300GB of signals which are of no use to me?

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 5 years ago

    Dear scottwatx,

    scottwatx said:
    Is there a way I can save out those key outputs, and delete the rest from the psfxl file, so that I can still reference the data from maestro assember without maintaining 300GB of signals which are of no use

    If I understand your question correctly, yes this is possible. Open a results browser window and then open the psf directory to which you wrote the simulation data. Select the transient results and then click on the signal(s) you want to save. Using your Right mouse button, you should see an option "Export..." and "Export (see Figure 1). This will allow you to export the waveforms you select into the format you choose. In your case, it appears you want to save them as psfxl - so select that option. As shown in Figure 2, you can then save the selected signals to a new psfxl file.

    Let me know if I understood your question correctly - hope so!

    Shawn

    Figure 1

    Figure 2

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • scottwatx
    scottwatx over 5 years ago in reply to ShawnLogan

    Shawn - thank you for your reply.  I don't think that will do what I want it to do, which is keep the data accessible from maestro, so I can see the outputs all listed by corners, the mins and maxes and which corners meet the specs.  I want to keep that but delete the 10000 other signals that I don't care about:

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • scottwatx
    scottwatx over 5 years ago in reply to ShawnLogan

    Shawn - thank you for your reply.  I don't think that will do what I want it to do, which is keep the data accessible from maestro, so I can see the outputs all listed by corners, the mins and maxes and which corners meet the specs.  I want to keep that but delete the 10000 other signals that I don't care about:

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to scottwatx

    If you're OK with keeping the scalar results but none of the waveforms, you can do that over the history in the history tab of the data view assistant by using Right Mouse->Delete Simulation Data.

    If you want to keep some of the waveforms, then one way (it's going to need a bit of scripting) would be to use the srrextract.sh utility that's in IC618 and ICADVM181. For each leaf psf directory, you could do:

    srrextract.sh -database psf -dataset tran-tran -signal out1 -signal out2 -signal out3 -o psfnew

    You could then move psfnew to be psf (this will only work if you only care about just one analyse's results), or replace the individual PSF XL files in the original psf directory with the files from the new directory (note the names may be tran.tran.tran* in the original and tran.tran* in the new, so you'd need to keep the original names if you do this).

    Back up your data first before trying this! (or try it on something small that doesn't matter first).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • scottwatx
    scottwatx over 5 years ago in reply to Andrew Beckett

    Andrew -

    I finally had the time and the necessity to trim my database.  I used srrextract.sh as you suggested and it worked like a champ.

    Thank you,

    Scott

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • scottwatx
    scottwatx over 5 years ago in reply to Andrew Beckett

    I spoke too soon.  When I leave the file names as tran.tran.* I can't read the files from maestro, but when I change them to tran.tran.tran.* I can't even read the database from the results browser.  Is there any solution for this?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to scottwatx

    It should work if you keep the original psf directory and logFile within that psf directory, and just replace the tran.tran.* files (with the original names) with the newly created files. Essentially the file names must match what is in the logFile.

    I just did this, for example:

    UNIX_4> srrextract.sh -database psf -dataset tran-tran -signal outp -signal outn -signal diffOut -o psfnew
    UNIX_5> ls psfnew
    logFile tran.tran tran.tran.psfxl tran.tran.sig
    UNIX_6> cd psf
    UNIX_7> mkdir old
    UNIX_8> mv tran.tran.tran* old
    UNIX_9> mv ../psfnew/tran.tran tran.tran.tran
    UNIX_10> mv ../psfnew/tran.tran.psfxl tran.tran.tran.psfxl
    UNIX_11> mv ../psfnew/tran.tran.sig tran.tran.tran.sig

    Then in both Explorer and the results browser, I can plot the signals.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • scottwatx
    scottwatx over 5 years ago in reply to Andrew Beckett

    That was my problem, I had used the new logFile instead of leaving the old one

    Thanks again!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information