IBM Support

HD79668: CANNOT SELECT INTERSECT(RESULT:CONTOUR) AS PROFILE OF PAD

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as user error.

Error description

  • Cannot select Intersect(Result:Contour) as Profile
    of Pad
    Scenario:
    1. Start CATIA.
    2. Open the CATPart attached to the PMR
    3.Click Pad icon.
    4. Select Intersect.2 as Profile/Surface.
    ==> Cannot select it with the following error
    message.
    -------------------------------------------
    Feature Definition Error
    The selected sketch isn't valid for
    the feature you want to create.
    -------------------------------------------
    Additional Information:
    Intersect.1 is the same as Intersect.2, the only
    difference is that the intersect result is computed
    with the option Surface-Part Intersection Result =
    surface for intersect.1 and contour for Intersect.2
    The Pad accepts the Intersect.1 but the Intersect.2.
    Both should be accepted.
    .
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • Incident Diagnosis
    The intersect operator works consistantly
    in both
    the modes. This is justified because, if you
    compute
    the intersection in the Surface mode, and
    then take the
    boundary of the surface. The PAD
    does not accept this boundary
    as well, throwing the
    same error (input profile is self
    intersecting). So
    there is no problem with the working of
    intersect
    operation.
    Correct Application
    Basically the
    behavior of the PAD feature is not the
    same when you are
    giving the 2D profile as input
    or the surface as input. So you
    get the expected
    behavior of PAD while specifying intersection
    as
    input to the PAD.
    Documentation Reference
    Getting Started
    

APAR Information

  • APAR number

    HD79668

  • Reported component name

    CATIA V5 NT>XP

  • Reported component ID

    569151000

  • Reported release

    518

  • Status

    CLOSED USE

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-13

  • Closed date

    2009-10-07

  • Last modified date

    2009-10-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"518","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 October 2009