ADAMS

From GICL Wiki
Revision as of 23:15, 15 December 2008 by Jmo34 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Title(s): ADAMS

Version(s): - Information about the version of the engineering format.

  • Version ID: - Identification or version number of the engineering format.
  • Date released: - Date that the version was released.

Date: - Date the format was created (YYYY-MM-DD)

Creator(s): - The creator or original author of the engineering format.

Contributor(s): - The current maintainers of the engineering format.

Description: - Main description of the format, which can give extra information not categorized.

Example(s): - Information and example models of the engineering format.

  • File: - Links to examples of the engineering format, in file format.
  • Text: - Description of the file being used as an example.
  • Creation date: - The date that the file was created.
  • Modification date: - The most recent date that the file was modified.

Identifier: - A URL or other identifier that refers to the engineering format.

Documentation: - Information in general about the engineering format.

  • URL: - Web site address of the documentation (on our server or on another server).
  • Name: - Name of the original developer. Examples: Autodesk, Inc.
  • Type {Company, Organization, Person}: - Type of developer.
  • Physical address(es): - Physical addresses of the developer.
    • Physical address: - Physical address of the developer.
      • Name
      • Address line 1
      • Address line 2
      • City
      • State
      • Zip
      • Country
  • Email address(es): - E-mail addresses of the developer.
  • Website(s): - Website of the developer.

File Extensions: adm

Applications: - Applications that the engineering format uses.

  • Native application(s): - Applications which are designed to specifically run this engineering format.
    • Name(s): - Names of the application.
      • Name: - Name of the application.
    • Version: - Version of the application.
    • Author(s): - Authors of the application.
      • Entity: - Author of the application.
    • Current owner(s): - Current owners of the application.
      • Entity: - Current owner of the application.
    • Description: - Description of the application.
    • Geometric modeling kernels: - Geometric modeling kernel of the application. A geometric modeling kernel is the software component that performs the 3D modeling. Examples: ACIS, Granite, Parasolid, Romulus
    • Computer platform(s): - Platform information for this application.
      • Operating system: - Operating systems that the application supports. Examples: Linux, Ubuntu 8, Mac OS X, Windows XP
      • Processor architecture: - The architecture of the supported processor. Examples: x86, x86-64, PowerPC
    • Can read: - Can the application read files with the format?
    • Can write: - Can the application write files using the format?
  • Interoperable applications: - Applications which are not designed to specifically run this engineering format, but can.
    • Name(s): - Names of the application.
      • Name: - Name of the application.
    • Version: - Version of the application.
    • Author(s): - Authors of the application.
      • Entity: - Author of the application.
    • Current owner(s): - Current owners of the application.
      • Entity: - Current owner of the application.
    • Description: - Description of the application.
    • Geometric modeling kernels: - Geometric modeling kernel of the application. A geometric modeling kernel is the software component that performs the 3D modeling. Examples: ACIS, Granite, Parasolid, Romulus
    • Computer platform(s): - Platform information for this application.
      • Operating system: - Operating systems that the application supports. Examples: Linux, Ubuntu 8, Mac OS X, Windows XP
      • Processor architecture: - The architecture of the supported processor. Examples: x86, x86-64, PowerPC
    • Can read: - Can the application read files with the format?
    • Can write: - Can the application write files using the format?

Parent formats: - Any direct ancestors of the engineering format, has the same information saved with it as a regular engineering format.

Magic numbers: - Unique identifying characters at the beginning of files for this engineering format.

Format(s): - The MIME file types.

Rights: - The name or type of the license for the engineering format. Examples: BSD-style license, Apache License, Proprietary license

File classification: - Specific properties that pertain to this engineering format.

  • Type {Binary, Text}: - The type of file, choices are binary and text.
  • Raster data: - Section describes whether or not the engineering format supports raster data.
    • Raster data 2D: - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Raster data 3D: - Can the format support 3D raster data? Example: A format that can contain 2D pixelated data of a 3D model supports 3D raster data.
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Geometric representation: - Section describes whether or not the engineering format supports geometric representations.
    • Implicit representation: - Section describes whether or not the engineering format supports implicit representations.
      • Implicit surfaces: - Can the format support implicit surfaces? Example: A format that can contain surfaces that are generated with mathematical equations that contain the independent variables x, y, and z, like x^2 + y^2 + z^2 * R^2 = 0, supports implicit surfaces.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Implicit curves: - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Point set: - Can the format support point sets? Example: A format that supports surfaces and lines that are generated by points that form triangles supports point sets.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
    • Mesh: - Section describes whether or not the engineering format supports mesh.
      • Manifold surface meshes: - Can the format support manifold surface meshes? Example: A format that supports surfaces that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Manifold volume meshes: - Can the format support manifold volume meshes? Example: A format that supports volumes that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Non-manifold meshes: - Can the format support non-manifold meshes? Example: A format that supports meshes that are not manifolds
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
    • Parametric representation: - Section describes whether or not the engineering format supports parametric representations.
      • Parametric surfaces: - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
      • Parametric curves: - Can the format support parametric curves? Example: A format that can contain curves that are generated with parametric equations supports parametric curves.
        • Is Supported: - Is the feature supported in the engineering format?
        • Description: - This field is used to describe the support or lack of support of the feature.
    • Contour sets: - Can the format support contour sets?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • NURBS: - Can the format support Non Uniform Rational Basis Splines? Examples: The engineering formats IGES, STEP, ACIS, and PHIGS
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Multi-resolution models: - Can the format support models with multiple resolutions? Examples: A format that supports a highly detailed and lowly detailed model simultaneously supports multi-resolution models.
    • Is Supported: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.
  • Dynamics:
    • Kinematics:
      • Is Supported: true
      • Description:
    • Assembly: - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Force(s): - Can the format support forces? Example: Does the format support acceleration forces?
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Boundary representation - Can the format support models with boundary representations?
    • Manifold surface boundary representations: - Can the format support manifold surface boundary representations? Example: The engineering format STEP
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Manifold volume boundary representations: - Can the format support manifold volume boundary representations? Example: The engineering format STEP
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
    • Non-manifold boundary representations: - Can the format support non-manifold boundary representations? Example: The engineering format STEP
      • Is Supported: - Is the feature supported in the engineering format?
      • Description: - This field is used to describe the support or lack of support of the feature.
  • Material transparency: - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
    • Is Supported: - Is the feature supported in the engineering format?
    • Description: - This field is used to describe the support or lack of support of the feature.