Two reasons why I think that it won't work, if talk about
an extracted view, extracted netlist after parasicit extraction.

-  Schematic vs. Extracted Layout

1. Your extracted view, extracted netlist contains additional
  paristic elements which originates form the layout, but which
  are not included in the schematic.

2.a. If you use a extracted view the interconnects are usually drawn
  on the layer purpose 'net', whereas the extraction rules consider
  most of the time the layer purpose 'drawing', like used in the layout
  view.

2.b. If you use a extracted view not sure if the it contains all layers at
    all which are necessary for device extraction defined in the extraction
    rules.


Bernd  

Quote:



Indeed that can be done by selecting
Output 'LVS Extracted View' only in the Assura RXC GUI
or by using '?lvsExtracted “t”' in the RSF file.

But then there are still 2.a, 2.b to worry about, but you can try
it.

What do you exactly want to check the LVS command rules
or the parasitic extraction?
And why do you doubt there are not correct?
Who does provide you with the rules?


Bernd

In general an RCX run is based on a clean LVS run,
because the tools are using their LVS database for
parasitic extraction.

Assura uses a so called 'procfile' where the process
topology is defined and the resulting files
'RCXspiceINIT', 'paxfile_coeff' and 'cap_coeff.dat'
as run scripts and capacitance models.
So the parasitic results have nothing to do with
the SKILL like exctract.rul file.

The shorts and open caps can be possibly removed by
changing the run specific setting in Assura e.g.
?excludeFloatingNets.

Did you run an Assura LVS?
Did the Assura LVS pass and is it clean?

It's not a good idea to use two different tools
one for LVS and the next for RXC!

Quote:


So the should be correct, I assume other customers are also using them.

I would suggest to check you Assura RCX run settings rather than try
debugging the command rules and related files.

Bernd