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
  • #1

Closed
Open
Created Sep 17, 2016 by Cristian Lalescu@clalescuMaintainer

particle checkpoints vs sampling

Low priority.

Particle "state" and "rhs" data is required for continuing DNS. It should be saved in double precision. Sampled fields come from single precision computations, it makes sense to save them in single precision. Also full particle trajectories only need to be saved in single precision as far as postprocessing is concerned, since the quantities we're interested in will not be affected by lack of precision.

What needs to happen is:

  • modify HDF5 datatype used in _particles.h5 file for sampled fields.
  • modify existing method into "checkpoint", and generate an adequate method for "sampling states" (i.e. write same data to different datasets).
Assignee
Assign to
Time tracking