Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integrate wave type classification #17

Closed
rgutzen opened this issue Apr 7, 2020 · 3 comments
Closed

integrate wave type classification #17

rgutzen opened this issue Apr 7, 2020 · 3 comments

Comments

@rgutzen
Copy link
Collaborator

rgutzen commented Apr 7, 2020

  1. calculating velocity vector field (on amplitude or phase signal)
  2. detect waves via VVF or via trigger times
  3. classify and label wave types
  4. filter for wave types

One key issue here is how to integrate the wave type classification in the wavefront_detection stage and how to combine it with the wavefront definition via trigger times.

@rgutzen rgutzen added this to the v0.1 milestone Apr 7, 2020
@rgutzen
Copy link
Collaborator Author

rgutzen commented May 27, 2020

Stage04_Flowchart

@gulpgiulia
Copy link
Collaborator

(maybe issue #17 (this one) and issue #32 could be merged)

@rgutzen rgutzen removed this from the v0.1 milestone Mar 13, 2024
@rgutzen
Copy link
Collaborator Author

rgutzen commented Mar 13, 2024

There hasn't evolved a general enough classification approach of labeling waves according to classes. Instead, the pipeline focuses on the characterization of the waves with measures such as planarity, which can be used to apply some custom wave classification on the pipeline output that is appropriate for the specific data and use case.
Furthermore, we integrated the block wave_mode_clustering that presents a general approach to wave type classification by clustering together similar waves into groups without the need to define or label these groups.

Closing this issue for now. However, the discussion if we want to include further wave-type classification blocks may be reopened in the future.

@rgutzen rgutzen closed this as completed Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants