• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. MSC Nastran
  3. Any issues with many unused spoints/qset?

Following Cadence Design Systems’ acquisition of the Design & Engineering (D&E) business, the D&E Community Forum on the Nexus Community Center has been migrated in the Cadence Physical System Simulation Community. For more details and if you have any questions, please refer to the FAQ.

Stats

  • State Not Answered
  • Replies 3
  • Subscribers 3
  • Views 17
  • Members are here 0
More Content

Any issues with many unused spoints/qset?

AC202603032340
AC202603032340 over 6 years ago
Are there any issues with having an arbitrarily large and mostly unused set of spoints/qset in an EXTSEOUT run? I'm thinking of possible downstream issues.
 
Here's a scenario that would lead one to defining a large set of spoints/qset:
Can't use AUTOQSET
EIGRL with a frequency range
Unknown # of RESVECs
 
  • Sign in to reply
  • Cancel
  • Don.Graff
    0 Don.Graff over 6 years ago
    I have had up to a hundred unused before without any issues (I just tested using 10000 SPOINT's and at least there isn't a limit in the generation run)... the unused ones ought to get autospc'd in the downstream. The only issue I can think of would be ID conflicts if taking up too many available unique ID's!
     
    Also, as a good practice, use the MANQ option to make sure the downstream QSET SPOINT ID is the same as the upstream (otherwise it can be an internally generated ID).
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • AC202603032340
    0 AC202603032340 over 6 years ago
    Sounds good. I assumed as much but wanted to hear some other opinions. Thanks for your insights.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • AC202603032340
    0 AC202603032340 over 6 years ago
    Just a follow up note on this topic. I was doing some EXTSEOUT runs today and noted that having a very large set of spoints/qset led to slow run times. E.g. small set of spoints/qset job took 8 minutes, but when I had a large range of spoints/qsets defined (90000000 THRU  99999999) the same job with no other differences ran for more than 2 hours before I killed it.
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Cadence Guidelines

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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information