Stats

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

layoutXL Gen from source doesn't give correct sizes.

MarkTown

 If I place my Pcell by hand the cell works fine. Sizes are what I expect them to be.

Gen from source gives me small values that can't be laid out.

The symbol though has "90n M" which doesn't match other tech files I've worked with "90n"

 I've tried two different ways of doing the CDF:

    cdfCreateParam( cdfId
        ?name           "w"
        ?prompt         "width"
        ?defValue       "0.2n"
        ?parseAsNumber  "yes"
        ?type           "string"
        ?units          "lengthMetric"
    )
 

 

I've also tried the following default value:

minMosWidth = 0.2 * 1e-6

?defValue       sprintf(nil "%g" minMosWidth)
 

Neither gives me the desired result.  Any thoughts?

 

Mark

Parents

  • Mark,

    The type of the pcell parameters is float, but the type in the CDF is string - so you have a mismatch. They need to be consistent, and ideally the default values should be consistent. In this case you have the w in the pcell in microns, but the CDF in metres. Consistency is the key.

    You could define the default values in the pcell as also being strings, and then use something cdfParseFloatString() in the pcell code to convert to a number, and do whatever scaling you need.

    Regards,

    Andrew.

Reply

  • Mark,

    The type of the pcell parameters is float, but the type in the CDF is string - so you have a mismatch. They need to be consistent, and ideally the default values should be consistent. In this case you have the w in the pcell in microns, but the CDF in metres. Consistency is the key.

    You could define the default values in the pcell as also being strings, and then use something cdfParseFloatString() in the pcell code to convert to a number, and do whatever scaling you need.

    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.