Vote toi have Catia-SW-Abaqus-Cosmos entirely interoperating

Discussion in 'CATIA' started by vnhjvnj, May 28, 2005.

  1. vnhjvnj

    vnhjvnj Guest

    all in the title ... the aim is to have access to mechanical analysis tools
    from middle to high level from "low" to "high" price
    vnhjvnj, May 28, 2005
  2. I didn't know they were having an election.

    Sign me up for a half dozen,,,,or,,,,,whatever.

    Mark Mossberg, May 29, 2005
  3. vnhjvnj

    vnhjvnj Guest

    Don't really vote but speak of...
    Users can be listened if they continuously list their problems to the

    The aim is only to be able to do physical or mechanical analysis as simpler
    as possible and to avoid complicate import-export functions.
    vnhjvnj, May 29, 2005
  4. vnhjvnj

    Cliff Guest

    Which ones do you wish to see discontinued? Why?
    Define "interoperating".

    Consider: Catia & SW have different kernels. No system can
    really have more than one, no matter what jb says. And Cosmos
    probably needs none at all (it's been a long, long time since I
    used it).
    Cliff, May 29, 2005
  5. vnhjvnj

    wurz Guest

    wurz, May 29, 2005
  6. vnhjvnj

    vnhjvnj Guest

    We need bicycle, cars, trucks...
    We use Notepad, Framemaker, Word and we can copy and paste, perhaps we could
    have such middle and high level softwares... with copy and paste!
    vnhjvnj, May 29, 2005
  7. vnhjvnj

    TOP Guest

    Well, Abaqus does pretty well at interoperating using Python. SW knows
    Python via Cosmic Blobs. SRAC could have had Cosmos/M working in a
    similar manner. Don't get your hopes up that Abaqus will run inside SW
    however. Abaqus needs a preprocesser to create the mesh. And it
    typically needs a pretty decent system to run the solver. Given that
    most SW users are going to try to analyze everything but the kitchen
    sink putting Abaqus into SW would leave a lot of people underimpressed.
    TOP, May 30, 2005
  8. vnhjvnj

    vnhjvnj Guest

    Microsoft and Dassault Systèmes to Align XML formats

    3D XML to support and extend Microsoft’s XAML format

    Redmond, Wash., USA, and Paris, France - April 14, 2005 - Microsoft
    Corp. and Dassault Systèmes (DS) (Nasdaq: DASTY; Euronext Paris: #13065,
    DSY.PA) today announced that, as part of their strategic alliance and
    commitment to jointly delivering value to their customers, they will
    collaborate to support Microsoft’s Extensible Application Markup Language
    (XAML) format in Dassault Systèmes’ 3D Extensible Markup Language (XML)
    format. XAML is the format for "Avalon," the code name of the next
    presentation subsystem for the Microsoft® Windows® operating system.

    "Avalon" provides the foundation for building applications and
    high-fidelity experiences, blending together user interfaces, documents and
    media content while exploiting the full power of users’ computers. "Avalon"
    provides native support for declarative, markup-based programming with XAML,
    making it simpler to build, customize and enrich Windows-based applications.

    3D XML is a universal, lightweight XML-based format that enables users
    to capture and share live, accurate 3D data quickly and easily. Dassault
    Systèmes will use the 3D XML format in its entire line of products: CATIA,
    DELMIA, ENOVIA, SMARTEAM, SolidWorks, and Spatial.

    Compatibility between 3D XML and XAML will enable users of 3D
    solutions to view, modify and customize 3D objects in an environment of
    unmatched openness and take advantage of this 3D experience in any
    XAML-based application.

    "3D XML is a universal, lightweight XML-based format that enables users to
    capture and share live, accurate 3D data quickly and easily" Material data
    also exist under xml (matxml). So xml Geometry, xml material behavior, xml
    boundary conditions, xml loads ... = xml FE
    vnhjvnj, May 30, 2005
  9. vnhjvnj

    Cliff Guest

    Still awaiting jb's opine on the XML kernel ....
    Cliff, May 31, 2005
  10. vnhjvnj

    wurz Guest

    Not a stretch for the imagination really as ABAQUS uses text "input
    decks" to run analyses. Input decks contain the option cards that
    describe the mesh, BC's, loads, materials etc. Converting this to some
    form of XML would IMHO be of questionable value. I'd rather see what
    Dassault do in terms of pre- and post-processing.

    ABAQUS is a VERY different beast if all you've ever done is linear
    statics analysis. There are s**tloads of options, tweaks and analysis
    types (they don't send you 14 manuals for nothing...).

    Long as I can have a pre-processor as good as I-DEAS (or Hypermesh)
    inside SW, I'll be a happy man (as well as 1xseat of I-DEAS maintenance
    better off) :-o

    wurz, May 31, 2005
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.