Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • Nektar Nektar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 62
    • Merge requests 62
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Nektar
  • NektarNektar
  • Merge requests
  • !1164

WIP: Spectral sensor

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Julian Marcon requested to merge feature/spectral-sensor into master Jul 10, 2020
  • Overview 0
  • Commits 2
  • Changes 3

I'm trying to define a "spectral sensor" and see if that can help identifying a shock vs smooth flow. Instead of only looking at s_p = ||q_{p-1}-q_p|| / ||q_p||, I look at s_i for i = 0,...,n, such that \Sum_{i} s_i = 1. The idea is that the error (i.e. s_i) should decay exponentially fast at shocks and slower everywhere else. I've tested that on a couple of test cases so far and haven't seen anything. But I was using p=4 and p=5 and I wonder if this behaviour only appears at even higher order.

Edited Jul 10, 2020 by Julian Marcon
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/spectral-sensor