Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T TurTLE
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • 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
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TurTLE
  • TurTLE
  • Issues
  • #7

Closed
Open
Created Apr 25, 2017 by Cristian Lalescu@clalescuMaintainer

NavierStokes vs NSVorticityEquation

We're using tests/test_vorticity_equation.py to compare the "old code" with the "new code".

Status:

  1. library compiles, both codes seem to run using 1 thread per process on 'tolima' and 'chichi-P' (my desktop machine, opensuse something, I can look up details if needed, and my laptop, debian rolling release something). Also, on machine that @bbramas is using.
  2. NSVE crashes on 'tolima' when using 2 threads per process, it seems to work on the other ones.
  3. trajectories obtained with the two codes look different: trajectories.pdf

I'd say (3) takes priority over everything else, since in the past problems in the algorithm led to segfaults and other crash-causing behavior.

Assignee
Assign to
Time tracking