5 Replies Latest reply on Sep 29, 2014 12:14 PM by lpaul1

    Generic CES Import


      Mentor Graphics’ Constraint Editor System has extensive capabilities for importing and exporting constraint data, as well as reusing constraint data. However, in recent discussion with customers, we’ve found that there are several use cases where the existing mechanisms don’t meet the needs well.


      Mentor plans to implement the use case of generic import of constraints into CES and would like to hear from users if this meets their needs to import data into CES.


      The rough plan is to allow CES users to import data from sources which are convenient for customers. We are considering .csv (comma separated values) file as an input file generated for example from Excel as the most often used one.


      We will not allow import of layers stackup or connectivity while we will allow an import of their constraints.


      CES will not import:

      o    Layout data (via definitions, stackup definition)

      o    Connectivity (electrical nets, differential pairs definitions, pin pairs, from-tos)


      CES will import:

      o    Physical rules representing routing technology guidelines (net classes, clearance rules, area schemes)

      o    Constraints related to stackup and connectivity


      Before import is started CES will backup data.


      Until import operation is finished and user confirms its correctness CES will not update iCDB database and keep the data locked.


      Users will be able to (via xml configuration file) choose which column should be imported and how they map to CES rules.


      During the entire import process CES will maintain data integrity and fill in missing relationships with needed values (either selected by user or technology defaults).


      CES import will be available either from CES user interface or from the command line tool to allow batch processing. User will be able to seed more than one design using generic import process.


      After import is finished CES will generate a report file with data logs and eventually highlight issues for review.


      We encourage you to post your comments about the desired data flow and your data import scenarios…. Thanks!

        • 1. Re: Generic CES Import

          CES  should support  the connectivity of electrical nets, differential pairs definitions, pin pairs, from-tos because the main of electrical constraints established on these objects.



          • 2. Re: Generic CES Import

            It is very confusing when you say, "we will not allow import of layers stackup or connectivity while we will allow an import of their constraints." You explicitly state the connectivity and stackup data that will not import but are very vague about what will. Can you please clarify? This stands to be very useful if done well. After all, the source of this tool update is that the current one is not useful to your customers.


            Also, I can speak for the majority of my colleagues when I say that if you launch a command-line tool you will not have a single adopter, no matter how useful that may be.

            • 3. Re: Generic CES Import

              Where do those electrical constraints come from that you could import them?

              • 4. Re: Generic CES Import

                Our initial goal is to import clearance constraints (basic, class to class, package to package, Z-axis), and widths. Command line tools are for those who want to develop script solutions for many users, and is not intended to be used by individual designers.


                Will you please expand on the comment: "...source of this tool update is that the current one is not useful to your customers?"

                • 5. Re: Generic CES Import

                  I'd like to see the option to import Noise Rules seperately or in addition to other CES constraints. Will there be an option to import partial constraint files to merge with existing constraints? Also, will we be able to export constraits and Actuals into a spreadsheet friendly format without having to decrypt the file?