Stats

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

ViVA XL export to vcsv failed

ZoltanT

Exporting a waveform into a vcsv file returns the error:

The wsSaveTraceCommand command generated an exception basic_string::_S_construct null not valid.

Only the first row of the vcsv file is created (";Version, 1, 0"). This was the first time I've exported waveforms generated with Assembler. I had no issue before with the combination of ADE L, Parametric sweep and ViVA XL. My project uses ICADV 12.3. I have not found any related forum entry or documentation. How could I export the waveforms in vcsv? Exporting the values into a table and then exporting into a csv works, but my post-processing script was written for vcsv format.

  • Andrew Beckett

    I did a little internal searching, and found an explanation (personally I think we ought to handle this more gracefully). The answer was:

    The error occurs when the waveform being exported does not have a name associated with it. The name is an internal attribute that is setup by the ADE plotting flows after expression evaluation/data access.

    So it may be that your output expressions in Assembler need to have a name specified, and then the error might go away? Can you check that, and if so, maybe contact customer support to suggest that we handle it more gracefully (because it's not obvious a name is required). Of course, if adding a name doesn't work, then also contact customer support!

    Andrew.

  • ZoltanT
    in reply to Andrew Beckett

    I have found another difference. Saving a waveform works as expected if I export a wave family of the same expression. But once I move a few selected waveforms into a new subwindow - example in the picture - and export them into a vcsv file, then the error pops up.



  • Andrew Beckett
    in reply to ZoltanT

    OK - suggest you contact support because clearly there's some buglets here...

    Andrew.

  • ZoltanT
    in reply to Andrew Beckett

    I work at a university where our licence does not allow any issue form creation ("View Content only user"). I could send an email to the local customer address, if the case is interesting for Cadence. Otherwise I will try to solve the issue in a different way.

    Regards,
    Zotlan

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.