Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N NIFTy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

On Thursday, 7th July from 1 to 3 pm there will be a maintenance with a short downtime of GitLab.

  • ift
  • NIFTy
  • Issues
  • #207

Closed
Open
Created Jan 04, 2018 by Martin Reinecke@mtrOwner

Meaning of Field methods mean(), var() and std() is unclear

Are we sure that the Field reduction methods mean(), var() and std() are doing what we expect from them?

Currently, mean() computes a straightforward average over all entries, without taking volume factors into account. Is this what we want? For GLSpaces, the result may not be the desired one.

@theos, @kjako, @dpumpe, @reimar: what are the official/intended semantics?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking