Computer Aided Design Services Avatar
  1. OMG Specification

Computer Aided Design Services — Closed Issues

  • Acronym: CAD
  • Issues Count: 43
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
CAD-15 What are units for 'angle' field in TessParametersStruct CAD 1.0b1 CAD 1.0 Resolved closed
CAD-14 TessellationStruct normals field should be VectorStructSeq CAD 1.0b1 CAD 1.0 Resolved closed
CAD-13 Should there be a get_parameter_set function at the Model interface level? CAD 1.0b1 CAD 1.0 Resolved closed
CAD-12 CadBrep Edge.nearest_points function needs clarification CAD 1.0b1 CAD 1.0 Resolved closed
CAD-11 CadBrep Edge.nearest_points function incorrect CAD 1.0b1 CAD 1.0 Resolved closed
CAD-10 CAD Services IDL issue (02) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-9 CAD Services IDL issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-8 Binding for Face.nurbs_representation needs major design overhaul/removal CAD 1.0b1 CAD 1.0 Resolved closed
CAD-7 CAD Services needs to clarify 'exact' for nurbs_representation functions CAD 1.0b1 CAD 1.0 Resolved closed
CAD-6 Edge.nurbs_representation should h. 'tolerance' argument declared as inout CAD 1.0b1 CAD 1.0 Resolved closed
CAD-5 Surface.nurbs_approximation should 'tolerance' argument declared as inout CAD 1.0b1 CAD 1.0 Resolved closed
CAD-4 Surface.nurbs_approximation should be renamed nurbs_representation CAD 1.0b1 CAD 1.0 Resolved closed
CAD-3 Need to add a "ColorStruct color;" to the PresentationStruct CAD 1.0b1 CAD 1.0 Resolved closed
CAD-2 IDL extracts in document are inconsistent about showing module declarations CAD 1.0b1 CAD 1.0 Resolved closed
CAD-1 CAD FTF issue regarding UML which looks kind of like CORBA profile CAD 1.0b1 CAD 1.0 Resolved closed
CAD-43 Incompletely specified operations - issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-42 Several properties in the CadBrep::PropertyStruct need clarification. CAD 1.0b1 CAD 1.0 Resolved closed
CAD-41 problems in the EntityCreation interface. CAD 1.0b1 CAD 1.0 Resolved closed
CAD-40 Entity Factory issue (Function 5) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-39 Entity Factory issue (Function 4) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-38 Entity Factory issue (Function 3) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-37 Entity Factory issue (Function 2) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-36 Entity Factory issue (Function) CAD 1.0b1 CAD 1.0 Resolved closed
CAD-35 interface for STEP open shel CAD 1.0b1 CAD 1.0 Resolved closed
CAD-34 Deletion of CadFourndation::Entity descendants CAD 1.0b1 CAD 1.0 Resolved closed
CAD-33 Entity.Position() returns PointStructure instead of TransformationStructure CAD 1.0b1 CAD 1.0 Resolved closed
CAD-32 There is no way to delete any CadFoundation::Entity interface child. CAD 1.0b1 CAD 1.0 Resolved closed
CAD-31 CadFoundation::Entity interface CAD 1.0b1 CAD 1.0 Resolved closed
CAD-30 Surface.intersect_ray argument error CAD 1.0b1 CAD 1.0 Resolved closed
CAD-29 CadSystem Properties issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-28 I haven't found any way to create ModelInstance CAD 1.0b1 CAD 1.0 Resolved closed
CAD-27 Replace #include "CadFeature.idl with #include "CadFoundation.idl" CAD 1.0b1 CAD 1.0 Resolved closed
CAD-26 Method names in topological entities are not everywhere unified CAD 1.0b1 CAD 1.0 Resolved closed
CAD-25 how to add new topological entities to existing model with sharing of exist CAD 1.0b1 CAD 1.0 Resolved closed
CAD-24 method of CadMain::EdgeLoop has to be renamed CAD 1.0b1 CAD 1.0 Resolved closed
CAD-23 we have to generalize is_manifold() methods in all BRep entities CAD 1.0b1 CAD 1.0 Resolved closed
CAD-22 adding an attribute to the entity group CAD 1.0b1 CAD 1.0 Resolved closed
CAD-21 Section 3.4, Editorial CAD 1.0b1 CAD 1.0 Resolved closed
CAD-20 Sections 1.8, 2.8, 3.1, 3.2, Editorial CAD 1.0b1 CAD 1.0 Resolved closed
CAD-19 Support for STEP input / output? CAD 1.0b1 CAD 1.0 Resolved closed
CAD-18 Body.property_info, several values are calculated. What is the return accur CAD 1.0b1 CAD 1.0 Resolved closed
CAD-17 BodyTessellationStruct issue CAD 1.0b1 CAD 1.0 Resolved closed
CAD-16 Model level parameters for geometry creation issue CAD 1.0b1 CAD 1.0 Resolved closed

Issues Descriptions

What are units for 'angle' field in TessParametersStruct

  • Key: CAD-15
  • Legacy Issue Number: 4538
  • Status: closed  
  • Source: Westinghouse Electric ( Jim Jones)
  • Summary:

    adGeometry IDL comment documents the 'angle' field in CadGeometry.TessParametersStruct
    as "deviation between normals of facets".

    Neither the IDL nor the CAD Services spec. indicate what angular units should be used.

  • Reported: CAD 1.0b1 — Mon, 27 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This oversight was corrected by indicating the required use of degrees for angle units.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

TessellationStruct normals field should be VectorStructSeq

  • Key: CAD-14
  • Legacy Issue Number: 4537
  • Status: closed  
  • Source: Westinghouse Electric ( Jim Jones)
  • Summary:

    The type of the 'normals' field in TessellationStruct should be VectorStructSeq
    instead of PointStructSeq.

  • Reported: CAD 1.0b1 — Mon, 27 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. IDL modified.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Should there be a get_parameter_set function at the Model interface level?

  • Key: CAD-13
  • Legacy Issue Number: 4528
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Should there be a get_parameter_set function at the Model interface level?

  • Reported: CAD 1.0b1 — Mon, 20 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadBrep Edge.nearest_points function needs clarification

  • Key: CAD-12
  • Legacy Issue Number: 4493
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Edge.nearest_points function needs clarification for
    'nearest_points' argument.

    How are the nearest_points defined? It is declared as a PointStructSeq,
    but no further details are provided. Will there always be 2? Is the
    first point of the sequence a point on the given edge and the second
    point a point on the edge corresponding to the input argument? What is
    the expected behavior if there are multiple locations that the 2 edges
    have an identical minimum distance?

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadBrep Edge.nearest_points function incorrect

  • Key: CAD-11
  • Legacy Issue Number: 4492
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Edge.nearest_points function incorrectly defines the
    'nearest_points' argument as 'in'.

    CAD Services spec documents Edge.nearest as 'Determines the minimum
    distance, and corresponding closest points, between this Edge and the input
    Edge. The returned value is the minimum distance'. The 'nearest_points'
    argument should be declared as 'out'.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Resolved through removing the nearest_points operation. See issue 4493.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CAD Services IDL issue (02)

  • Key: CAD-10
  • Legacy Issue Number: 4491
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Edge IDL defines a 'start_vertex()' function, but not
    an 'end_vertex()' function.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. An operation was added to the Edge interface.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CAD Services IDL issue

  • Key: CAD-9
  • Legacy Issue Number: 4490
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CadBrep Oriented Edge IDL defines an 'end_vertex()' function,
    but not a 'start_vertex()' function.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. An operation was added to the OrientedEdge interface

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Binding for Face.nurbs_representation needs major design overhaul/removal

  • Key: CAD-8
  • Legacy Issue Number: 4489
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Binding for Face.nurbs_representation needs major design overhaul or
    removal.

    IDL indicates the function returns a CadUtility.NurbsSurfaceStruct. A
    simple NURBS surface structure cannot represent arbitrary faces w/
    irregular boundaries, both outer and inner.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CAD Services needs to clarify 'exact' for nurbs_representation functions

  • Key: CAD-7
  • Legacy Issue Number: 4488
  • Status: closed  
  • Source: Anonymous
  • Summary:

    CAD Services specification needs to clarify 'exact' for
    nurbs_representation functions.

    nurbs_representation indicates that if the NURBS is exact, then tolerance
    is returned as negative value. Is that exact geometrically or exact
    geometrically AND parametrically?

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Edge.nurbs_representation should h. 'tolerance' argument declared as inout

  • Key: CAD-6
  • Legacy Issue Number: 4487
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Edge.nurbs_representation should h. 'tolerance' argument declared as
    'inout' instead of 'in'.

    CAD Services specification indicates that 'If the representation is exact -
    tolerance will be returned as a negative value.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. This corrections involved a minor modification of the IDL.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Surface.nurbs_approximation should 'tolerance' argument declared as inout

  • Key: CAD-5
  • Legacy Issue Number: 4486
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Surface.nurbs_approximation should have 'tolerance' argument declared as
    'inout' instead of 'in'.

    CAD Services specification indicates that 'If nurbs representation is
    exact, tolerance will be returned as a negative'. By the way, the 'NURBS'
    acronym should be capitalized in the spec and IDL when used in this
    context.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Surface.nurbs_approximation should be renamed nurbs_representation

  • Key: CAD-4
  • Legacy Issue Number: 4485
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Surface.nurbs_approximation should be renamed nurbs_representation to be
    consistent w/ Curve.nurbs_representation.

  • Reported: CAD 1.0b1 — Mon, 6 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agree. Representation is a better description

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Need to add a "ColorStruct color;" to the PresentationStruct

  • Key: CAD-3
  • Legacy Issue Number: 4433
  • Status: closed  
  • Source: Anonymous
  • Summary:

    I was building a Java3d display for CadServices data and I realized that
    > we do not return the object color in the PresentationStruct. We return
    > the color of the highlight (specular_color), and various parameter about
    > reflectance - but we do not include the base color of the object.
    >
    > I think we need to add a "ColorStruct color;" to the PresentationStruct.

  • Reported: CAD 1.0b1 — Fri, 27 Jul 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

IDL extracts in document are inconsistent about showing module declarations

  • Key: CAD-2
  • Legacy Issue Number: 4415
  • Status: closed  
  • Source: Distributed Models Pty Ltd ( Keith Duddy)
  • Summary:
    • IDL extracts in the document are inconsistent about showing module
      declarations.
  • Reported: CAD 1.0b1 — Sat, 14 Jul 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Module declarations added to the document

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CAD FTF issue regarding UML which looks kind of like CORBA profile

  • Key: CAD-1
  • Legacy Issue Number: 4414
  • Status: closed  
  • Source: Distributed Models Pty Ltd ( Keith Duddy)
  • Summary:

    UML looks like Corba profile, but is not quite. In particular the
    <<Interface>> stereotype should be <<CORBAInterface>>. There may also
    be some "in" tags in the wrong place.

  • Reported: CAD 1.0b1 — Sat, 14 Jul 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    CORBA UML diagrams throughout the document were updated to an appropriate format

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Incompletely specified operations - issue

  • Key: CAD-43
  • Legacy Issue Number: 4985
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Mikhail Kazakov mentioned that some of the Cad Services interfaces may be under-specified. Here is a list of operations needing additional documentation:
    1. CadMain:: open_model( Â…) - the question involves whether this operation loads the specified model into memory or are all the available models in memory and the open_model() operation merely returns an object reference to the model.

    Recommendation: the documentation should include the following: The open_model() operation loads the specified model into memory and can be unloaded by invoking close_model() on the Model object reference.

    2. CadMain:: top_level_entities (in CadUtility::TypeCodeSeq entity_types) - what happens when an empty TypeCodeSeq is passed? One could respond with all top level entities or none.
    Recommendation: Documentation shall state that an empty TypeCodesSeq will result in a system exception (BAD_PARAM).

    3. unsigned long unique_entities_count (in CadUtility::TypeCodeSeq entity_types) raises (NotValidCadType, CadUtility::CadError); - what happens when an empty TypeCodeSeq is passed? One could respond with all entites or none.
    Recommendation: Documentation shall state that an empty TypeCodesSeq will result in a system exception (BAD_PARAM).

    4. CadFoundation::EntitySeq unique_entities (in CadUtility::TypeCodeSeq entity_types) raises (NotValidCadType, CadUtility::CadError); – what happens when an empty TypeCodeSeq is passed? One could respond with all entites or none.
    Recommendation: Documentation shall state that an empty TypeCodesSeq will result in a system exception (BAD_PARAM).

  • Reported: CAD 1.0b1 — Mon, 18 Mar 2002 05:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    The identified recommendations were agreed.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Several properties in the CadBrep::PropertyStruct need clarification.

  • Key: CAD-42
  • Legacy Issue Number: 4653
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    double inertial_moment_spherical;
    double gyration_radius_spherical;
    CadUtility::VectorStruct first_moments_centroidal;
    CadUtility::VectorStruct inertial_moments_centroidal;
    CadUtility::VectorStruct inertial_products_centroidal;
    CadUtility::VectorStruct principle_moments_centroidal;
    CadUtility::VectorStruct gyration_radii_centroidal;

    are unclear.

    Jim Stevens identified the following:

    The "centroidal" moments are the various mass properties with respect to the center of mass for the body. This is the more "typical" case for mass properties. They correspond to similar mass property calculations in the structure that are with respect to a specific coordinate system.
    Principle moments are moments inertia along the principle axes through the center of gravity of an object.
    When defining a moment of inertia around an arbitrary axis thru the center of mass you end up with product terms. There is
    one axis definition for which the product terms are zero, which is called the principle axis and the moments of inertia when
    using that axis definition are the principle moments.
    Radius of gyration is related to the moments of inertia and the mass along each axis.
    I am not sure about the meaning of first moments. I am pretty sure that inertial_moment_spherical and
    gyration_radius_spherical have to do with representing the model with a single sphere that would have
    the same overall inertial characteristics as the analyzed body.
    Jim Stephens

    Based on Jim's comments I am not certain that we need the first moments or the spherical inertial moment and gyration radius.

  • Reported: CAD 1.0b1 — Wed, 31 Oct 2001 05:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

problems in the EntityCreation interface.

  • Key: CAD-41
  • Legacy Issue Number: 4632
  • Status: closed  
  • Source: TranscenData ( Jim Jones)
  • Summary:

    Here is a quick itemization of necessary changes (most from Sergey and
    a few additional). Following the list is a modified section of the IDL
    that can be used to replace the corresponding lines in the existing
    CadMain.idl file. *** NOTE: Also need to add 'typedef sequence<LongSeq> LongSeqSeq;'
    to CadUtility.idl.

    index_faces:
    Needs 'SeqSeq' of oriented_eloops instead of 'Seq'
    For consistency, arg should probably be 'oriented_edge_loops' instead of 'oriented_eloops'
    Does not need eloops, edges.
    index_edge_loops:
    Needs 'SeqSeq' oriented_edges instead of 'Seq'
    index_shells:
    Needs 'SeqSeq' oriented_faces instead of 'Seq'
    index_bodies:
    Needs 'SeqSeq' oriented_shells instead of 'Seq'
    index_vertex_loops:
    Ok (just included in IDL below for easier replacement of old IDL section)
    index_oriented_edges
    Need 'BooleanSeq senses'
    index_oriented_faces
    Need 'BooleanSeq senses'
    No vertices or vLoops needed
    index_oriented_edge_loops
    For consistency, should probably be 'index_oriented_edge_loops' not 'index_oriented_edgeloops'
    Need 'Seq edge_loops' not 'Seq edges'
    Need 'BooleanSeq senses'
    index_oriented_shells:
    Need 'Seq shells' not 'Seq ofaces'
    Need 'BooleanSeq senses'
    No vloops needed

    CadUtility::LongSeq index_faces(in CadUtility::LongSeqSeq oriented_edge_loops,
    in CadUtility::LongSeq vertex_loops, in CadUtility::LongSeq surfaces)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_edge_loops(in CadUtility::LongSeqSeq oriented_edges)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_shells (in CadUtility::LongSeqSeq oriented_faces)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_bodies (in CadUtility::LongSeqSeq oriented_shells)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_vertex_loops (in CadUtility::LongSeq vertices)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_edges(in CadUtility::LongSeq edges,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_faces(in CadUtility::LongSeq faces,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_edge_loops(in CadUtility::LongSeq edge_loops,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);
    CadUtility::LongSeq index_oriented_shells(in CadUtility::LongSeq shells,
    in CadUtility::BooleanSeq senses)
    raises (IncorrectIndex, CadUtility::CadError);

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Entity Factory issue (Function 5)

  • Key: CAD-40
  • Legacy Issue Number: 4631
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    5. Function
    CadUtility::LongSeq index_oriented_faces(in CadUtility::LongSeq faces,
    in CadUtility::LongSeq vertices,
    in CadUtility::LongSeq vloops)

    Maybe instead of this, the description should be something like this:

    index_oriented_faces(in CadUtility::LongSeq faces,
    in CadUtility::BooleanSeq senses)?

    For what reason should you put the vertices and vloops in parameters?

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Entity Factory issue (Function 4)

  • Key: CAD-39
  • Legacy Issue Number: 4630
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    4. Function
    CadUtility::LongSeq index_oriented_xxxxxxxx

    For functions which create oriented entities, boolean flags "sense" should be present in parameters, i.e. like BooleanSeq senses.

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Entity Factory issue (Function 3)

  • Key: CAD-38
  • Legacy Issue Number: 4629
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    3. Function
    CadUtility::LongSeq index_shells (in CadUtility::LongSeq oriented_faces)
    raises (IncorrectIndex, CadUtility::CadError);

    The same situation. "In" parameter orieneted_faces should be CadUtility::LongSeqSeq, because shell is a set of faces.

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Entity Factory issue (Function 2)

  • Key: CAD-37
  • Legacy Issue Number: 4628
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    2. Function
    CadUtility::LongSeq index_edge_loops(in CadUtility::LongSeq oriented_edges)

    Edge loop is described by list of edges, because of this, the "in" parameter oriented_edges should be CadUtility::LongSeqSeq.

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Entity Factory issue (Function)

  • Key: CAD-36
  • Legacy Issue Number: 4627
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Function
    CadUtility::LongSeq index_faces(in CadUtility::LongSeq oriented_eloops,
    in CadUtility::LongSeq eloops, in CadUtility::LongSeq edges,
    in CadUtility::LongSeq vertex_loops, in CadUtility::LongSeq surfaces)

    Could you describe, please, the reason of presence of "eloops" and "edges" in the parameters?

  • Reported: CAD 1.0b1 — Tue, 23 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Please see resolution in issue 4632

  • Updated: Fri, 6 Mar 2015 20:58 GMT

interface for STEP open shel

  • Key: CAD-35
  • Legacy Issue Number: 4595
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Suggest interface for STEP open shell, ie a collection of faces that do not enclose a volume.

  • Reported: CAD 1.0b1 — Fri, 5 Oct 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This functionality is available in the current CadGeometry::Shell interface.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Deletion of CadFourndation::Entity descendants

  • Key: CAD-34
  • Legacy Issue Number: 4573
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    Possible resolution:

    Add methods:

    interface CadSystem

    { void delete_model(in string modelname) raises (InvalidModel, PermissionDenied, CadUtility::CadError); // Removes model from CadSystem void delete_model(in CadMain::Model model) raises (InvalidModel, PermissionDenied, CadUtility::CadError); // Removes model from CadSystem }

    interface Model

    { exception EntityOutOfModel; void delete_entity(in long uid) raises (EntityOutOfModel, NotIndependent, UidUnsupported, PermissionDenied, CadUtility::CadError); // Removes ModelInstance, BrepEntity, Curve or Surface from the model void delete_entity(in CadFoundation::Entity entity) raises (EntityOutOfModel, NotIndependent, PermissionDenied, CadUtility::CadError); // Removes ModelInstance, BrepEntity, Curve or Surface from the model }
  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This is essentially the same issue as involved with 4571.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Entity.Position() returns PointStructure instead of TransformationStructure

  • Key: CAD-33
  • Legacy Issue Number: 4572
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    Replace
    CadUtility::PointStruct position () raises (CadUtility::CadError);
    // Returns a struct of the coordinates of a single, reference location on
    // the entity that should be unique relative to neighboring entities.
    method by
    CadUtility::TransformationStruct location () raises (CadUtility::CadError);
    // Returns a struct of the applied transformation, which represents
    // the location (position, turn, scale) of the entity according the global coordinates

    In that case, we will be able to refer the entity according any other entities.
    This method doesn't return the "last applied transformation", but "the superposition
    of all applied transformations". In that case, location of the entity in 3D space will be returned.

  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Duplicate

  • Updated: Fri, 6 Mar 2015 20:58 GMT

There is no way to delete any CadFoundation::Entity interface child.

  • Key: CAD-32
  • Legacy Issue Number: 4571
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    There is no way to delete any CadFoundation::Entity interface child.
    We shall add the possibility to delete:

    Model
    ModelInstance
    BrepEntity
    Curve
    Surface

  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadFoundation::Entity interface

  • Key: CAD-31
  • Legacy Issue Number: 4570
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    There is no "3D Location" function in Entity interface.
    There is only Entity.Position(), which returns PointStructure,
    but it is not enough to describe a 3D transformation.
    It's necessary to return TransofmrationStruct from such a function.
    It's necessary also to mention, that Entity interface has a method for
    transformation.

    However, if Position() has another goal, than 3D location of Entity, it
    shall be described in the document.

  • Reported: CAD 1.0b1 — Thu, 20 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Surface.intersect_ray argument error

  • Key: CAD-30
  • Legacy Issue Number: 4566
  • Status: closed  
  • Source: Westinghouse Electric ( Jim Jones)
  • Summary:

    The 'intersection_parameters' argument in Surface.intersect_ray() must be type 'CadUtility::UvStructSeq' instead of 'CadUtility::DoubleSeq'.

  • Reported: CAD 1.0b1 — Thu, 13 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

CadSystem Properties issue

  • Key: CAD-29
  • Legacy Issue Number: 4564
  • Status: closed  
  • Source: Anonymous
  • Summary:

    In the CadServer interface we have the ability to inquire launch
    properties for the CadSystem, and then pass in a set of properties
    when we call connect() or connect_with_password().

    Once the CadSystem is running we do not have a way to query or
    change the properties.

    As an example - UG has a property for the search path for files.
    You can set this property when you initially start up the CadSystem.
    If it needs to be changed during a session the only choice is to
    shut down the CadSystem with disconnect() then call connect()
    again.

    Also, if you connect to an already running CadSystem you
    cannot determine what properties were used during the original
    connect().

    I think I would propose adding something like "get_properties"
    and "set_properties" for the CadSystem interface. These calls
    would basically allow a query and update of the properties
    provided to the CadServer via the connect() calls.

    CosPropertyService::Properties get_properties();
    void set_properties( in CosPropertyService::Properties props );

  • Reported: CAD 1.0b1 — Thu, 6 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    The proposed operations were added to the CadSystem interface.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

I haven't found any way to create ModelInstance

  • Key: CAD-28
  • Legacy Issue Number: 4563
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    7. Creation of ModelInstances. I haven't found any way to create ModelInstance. And it's not explained in the specification.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Replace #include "CadFeature.idl with #include "CadFoundation.idl"

  • Key: CAD-27
  • Legacy Issue Number: 4562
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    6. #include list of CadGeometry module contain:
    #include "CadFeature.idl"
    that has to be replaced by #include "CadFoundation.idl".
    CAD Geometry never use features explicitly.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    This is a good observation. The #include was modified.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Method names in topological entities are not everywhere unified

  • Key: CAD-26
  • Legacy Issue Number: 4561
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    5. Method names in topological entities are not everywhere unified. To return a single entity we use normally prefix get_entity.
    To return a sequence we use no prefix normally: for example

    Shell get_shell () raises (CadUtility::CadError);
    OrientedFaceSeq oriented_faces () raises (CadUtility::CadError);

    Not all method names in CadBrep module satisfy this rule.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    All operations that did not follow the standard naming procedure were changed.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

how to add new topological entities to existing model with sharing of exist

  • Key: CAD-25
  • Legacy Issue Number: 4560
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    3. It is not clearly described in the specification document, how to add new topological entities to existing model with sharing of existing entities.
    Let's say we have 2 vertexes already created and we would like to add an edge.
    While implementing EntityFactory interface, a developer have to care about this sharing. Otherwise vertexes won't be shared.
    And from my point of view we have to speak about that in the document.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

method of CadMain::EdgeLoop has to be renamed

  • Key: CAD-24
  • Legacy Issue Number: 4559
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    OrientedEdgeLoopSeq edge_loop() raises (CadUtility::CadError); method of CadMain::EdgeLoop has to be renamed to
    OrientedEdgeLoopSeq oriented_edge_loop() raises (CadUtility::CadError);
    for unification.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    The operation is renamed.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

we have to generalize is_manifold() methods in all BRep entities

  • Key: CAD-23
  • Legacy Issue Number: 4558
  • Status: closed  
  • Source: Open Cascade ( Mikhail Kazakov)
  • Summary:

    1. Perhaps we have to generalize is_manifold() methods in all BRep entities. I propose to have is_manifold() only in BrepEntity interface, but not in each interface. The only restriction is vertex, which can return anytime TRUE.

  • Reported: CAD 1.0b1 — Wed, 5 Sep 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

adding an attribute to the entity group

  • Key: CAD-22
  • Legacy Issue Number: 4551
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Our entity groups in Cad Services don't have any form of an
    identifier or name that can be retrieved through the interface.
    The only returned data is either a list of entities in the group or
    the count. It makes it difficult to present this information to a
    user.

    We might consider adding an attribute to the entity group,
    however that means it gets inherited to the layer.

    readonly attribute string native_label;

  • Reported: CAD 1.0b1 — Thu, 30 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    A readonly attribute was added to the EntityGroup interface.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section 3.4, Editorial

  • Key: CAD-21
  • Legacy Issue Number: 4548
  • Status: closed  
  • Source: NIST ( Mr. David Flater)
  • Summary:

    Section 3.4, Editorial: Although the description of interaction with
    PDM Enablers is fairly clear, a sequence diagram (or several, for
    the several cases) would increase the likelihood of
    interoperability.

  • Reported: CAD 1.0b1 — Mon, 20 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Appropriate sequence diagrams were added to the specification.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Sections 1.8, 2.8, 3.1, 3.2, Editorial

  • Key: CAD-20
  • Legacy Issue Number: 4547
  • Status: closed  
  • Source: NIST ( Mr. David Flater)
  • Summary:

    Sections 1.8, 2.8, 3.1, 3.2, Editorial: Compliance points / levels
    and optional interfaces are spread around the document in a way that
    would hamper formal claims of conformance.

  • Reported: CAD 1.0b1 — Mon, 20 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Support for STEP input / output?

  • Key: CAD-19
  • Legacy Issue Number: 4544
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Support for STEP input / output?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Body.property_info, several values are calculated. What is the return accur

  • Key: CAD-18
  • Legacy Issue Number: 4543
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Body.property_info, several values are calculated. What is the return accuracy? Should a separate accuracy for each separate property be returned? Should accuracy be returned at all?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

BodyTessellationStruct issue

  • Key: CAD-17
  • Legacy Issue Number: 4542
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Should Shell.tessellation return a similar structure to Body.tessellation? Currently shell tessellation returns a FaceTessellationStructSeq while body tessellation returns a BodyTessellationStruct. Shell tessellation results are the only tessellation results that do not have an object reference to underlying topology. Rename BodyTessellationStruct to something like ConnectedFaceTessellationStruct?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Model level parameters for geometry creation issue

  • Key: CAD-16
  • Legacy Issue Number: 4541
  • Status: closed  
  • Source: NASA ( Russ Claus)
  • Summary:

    Model level parameters for geometry creation. Should the model creation operation support new parameters?

  • Reported: CAD 1.0b1 — Wed, 29 Aug 2001 04:00 GMT
  • Disposition: Resolved — CAD 1.0
  • Disposition Summary:

    Agreed. A Model creation operation was modified in the CadSystem interface.

  • Updated: Fri, 6 Mar 2015 20:58 GMT