Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Hi,I've got the following problem with some skill code I've written that should export more than one place bound per component to IDF. The code so far seems stable, but I have issues with calculating the arc radius if it is not between 10 and 170 degrees or 0/180 degrees.I've created a test case that exhibits the issue. It is attached as boards.zip it contains 2 board files. Case2.brd which is the original board in millimeters and micron_2decimals.brd which is a conversion of case2.brd with 2 decimal points. Looking at this there should be precisely a factor 1000 in difference, this is however not the case, I can get better precision after the translation. Here's the arc data that I can get out using the attached skill program
Hi Ole,Your code is quite complex - and involves lots of floating point maths - so you will probably get lots of floating point rounding errors. See the discussion about that problem in this forum.I have written a similar routine for exporting IDF and get the same results as Cadence.See attached.Cheers, Dave
Hi Dave,Thanks very much for the code, although I've got problems figuring out how you actually calculate the angle. I've looked all over the documentation for the atan2 function but I cannot find anything about it, except that it takes 2 arguments but how will that help me?Another thing is the sign of the angle, it is consequently the wrong sign compared to running this on a larger board with several arcs. It may be easy to change, but as written above I've got some problems figuring out exactly what you do and why?I know my code is also pretty complex and this is due to the fact that getting the correct angle when using normal atan is dependent on the start and end points position relatively (depending on the quadrant of the coordinate system). I can see that you get the correct angle each time, only issue is the sign, so maybe you've got another approach than I have?I've attached an example that exhibits this issue so you can see it for your self. The angle figure is the same but the sign in your case is negative whereas it is positive in the Cadence case.Best regards,Ole
Hi Ole,I'll take a look at the angle sign issue. I have had problems with that in the past and possibly need to improve my code for it to work in every case.atan2 gets around the problem with atan where the adjacent line length is 0.i.e. atan(o / a) returns an "Attempted to divide by zero" error if a is 0. atan2(o a) correctly returns pi / 2 if a is 0.I don't know why atan2 isn't documented. I never use atan.Cheers, Dave
Hi Dave, Thanks for the explanation. This problem was actually one of the reasons I had to make the code more complex.Best regards,Ole