Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • TLSImplicit TLSImplicit
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • eXlibris
  • XTLS
  • TLSImplicitTLSImplicit
  • Issues
  • #22

Closed
Open
Created Jan 08, 2020 by Benoît LÉ@bleMaintainer

Bug when using single cut with update_displacement_field = 1

When running a computation with the single cut and with the option update_displacement_field = 1 (use of previous displacement field at the begining of a Newton Raphson loop), the computation may abort in the xtls::TLSEnrichment_3::updateValues.

A "quick" fix is to use update_displacement_field = 0, in order not to use the updateValues function. Note that this problem has not been observed with the double cut (tested on the Lshaped test case, with 8 different computations for the single cut and 8 different computations for the double cut).

Assignee
Assign to
Time tracking