Stats

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

Using ipwlf with a file input

mhkvy4

Hello,

I am using virtuoso 6.1.9 release. I was looking for documentation for how to include a file in an ipwlf instance on the support site but was unable to find one. I am looking to add the current loading profile from my circuit to the output of a regulator. I had the some questions about using IPWLF as an instance.

1) what kind of file formats does the ipwlf recognize? .txt or .csv etc. 

What would be best file format to export my data from ViVA and then use it as a file for IPWLF instance?

2) There doesn't appear to be a browse button to select a file. Should I just use the absolute path to the file if it is located in my home directory? Would virtuoso recognize the file and the data it contains?

3) A colleague pointed out that the exported data should be two columns of time stamps and the respective current values with a space in between. I was also told that the time stamps should be monotonic and unique but in my file I have the same time stamp with different values? Any way to clean up this saved simulation data or plot it in ViVA so that each time stamp has a discrete value?

Thanks

Parents

  • Was hoping someone could provide with an example of the usage of IPWLF and how the data used in it has to be formatted. 

  • in reply to mhkvy4

    If this was urgent, you could have contacted customer support or maybe even read the documentation. If you read "spectre -h isource" it tells you the format. Whilst that says that it supports space or tab between the time and value, it also supports comma.

    To answer your questions:

    1. I effectively answered this already - either is fine - space, tab or comma-separated
    2. In general, I'd suggest giving a local path (no directory) and then specifying the directory part via Setup->Simulation Files->Include Path - this makes it easier to relocate the files without having to change the path in the schematic. Or it could be a full path - it's up to you.
    3. Well, it makes no sense to have two values at the same time - you wouldn't get that from simulation anyway, and it would be a bad idea as that would result in the simulator needing to have two different solutions at the same time, which makes no sense. So I don't see why you'd need to clean it up since it should never be like that in the first place! You could sample the data on export from ViVA (the Export form has the option to do that) so you could sample it on a regular time step instead.

    Regards,

    Andrew 

Reply
  • in reply to mhkvy4

    If this was urgent, you could have contacted customer support or maybe even read the documentation. If you read "spectre -h isource" it tells you the format. Whilst that says that it supports space or tab between the time and value, it also supports comma.

    To answer your questions:

    1. I effectively answered this already - either is fine - space, tab or comma-separated
    2. In general, I'd suggest giving a local path (no directory) and then specifying the directory part via Setup->Simulation Files->Include Path - this makes it easier to relocate the files without having to change the path in the schematic. Or it could be a full path - it's up to you.
    3. Well, it makes no sense to have two values at the same time - you wouldn't get that from simulation anyway, and it would be a bad idea as that would result in the simulator needing to have two different solutions at the same time, which makes no sense. So I don't see why you'd need to clean it up since it should never be like that in the first place! You could sample the data on export from ViVA (the Export form has the option to do that) so you could sample it on a regular time step instead.

    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.