Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 426
    • Issues 426
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1612
Closed
Open
Issue created Feb 27, 2020 by Mark OLESEN@markMaintainer

improve controls for nastran surface output

Currently have a scale parameter, which scales all fields (including label fields such as Ids!), but no mechanism for scaling the geometry on output (eg, meter to millimeter).

This was noticed while working on the abaqus portion of #1600 (closed). Since we starting fresh there, it makes more sense to define the following:

formatOptions
{
    abaqus
    {
        scale   1000;     // [m] -> [mm]
        fieldScale
        {
            "p.*"   0.01;  // [Pa] -> [mbar]
        }
    }

Using scale for geometry scaling is consistent with input via a triSurfaceMesh. Using a dictionary format allows better control and different field scaling (eg, something for pressure, none for velocity).

Aligning the Nastran output would be a breaking change, but could be worthwhile in the long-term. May also wish to change how the field tuples are handled as well?

The scale keyword was added 2013 (9e5e2c8b), so unfortunately no gitlab audit trail.

Edited Feb 27, 2020 by Mark OLESEN
Assignee
Assign to
Time tracking