Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 384
    • Issues 384
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #777

Closed
Open
Created Mar 19, 2018 by Admin@OpenFOAM-adminMaintainer

enhancement: merge of foundation code for kinematic parcel

I am wondering what your merge strategy with the foundation code nowadays is. I found some nice improvements on kinematic parcels in the foundation code. Do you do a merge a while before a new release or is is it based on nice new feature you guys stumble on when viewing the foundation code? Is it useful for users to point out some improvements from the foundation code or will they end up eventually in this version?

I found some nice features for improving speed and accuracy for the kinematic parcel class:

  1. Improving speed: https://bugs.openfoam.org/view.php?id=2688 https://bugs.openfoam.org/view.php?id=2871

  2. Improving tracking accuracy: https://bugs.openfoam.org/view.php?id=2282 https://bugs.openfoam.org/view.php?id=2666

From what I read in the descriptions, these sounded as really nice improvements and therefore I wanted to point them out.

Assignee
Assign to
Time tracking