nuluh/thesis
1
0
Fork 0
Code Issues 47 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Feed More Data (STFT) #24

New Issue
Closed
opened 2024-10-21 12:16:09 +00:00 by nuluh · 0 comments
nuluh commented 2024-10-21 12:16:09 +00:00 (Migrated from github.com)
Copy Link

Issue

Current approach processes only the TEST1 data for each damage case, resulting in STFT files like stft_data1_1.csv containing data solely from D1_TEST01_01.csv. This excludes data from TEST2 to TEST5, preventing comprehensive analysis across all test runs.

Solution Overview

To achieve the goal, I need to:

  1. Iterate Over All Test Runs:

    • For each damage case, process all test runs (TEST1 to TEST5).

  2. Perform STFT on Each Test Run:

    • Apply the STFT to each test run's vibration data.

  3. Aggregate STFT Results:

    • Concatenate the STFT results from all test runs vertically to form a single DataFrame per damage case and sensor.

  4. Export Aggregated STFT Data:

    • Save the aggregated STFT DataFrame to a CSV file with the appropriate naming convention.
## Issue Current approach processes only the `TEST1` data for each damage case, resulting in STFT files like `stft_data1_1.csv` containing data solely from `D1_TEST01_01.csv`. This excludes data from `TEST2` to `TEST5`, preventing comprehensive analysis across all test runs. ## Solution Overview To achieve the goal, I need to: 1. **Iterate Over All Test Runs:** - For each damage case, process all test runs (`TEST1` to `TEST5`). 2. **Perform STFT on Each Test Run:** - Apply the STFT to each test run's vibration data. 3. **Aggregate STFT Results:** - Concatenate the STFT results from all test runs vertically to form a single DataFrame per damage case and sensor. 4. **Export Aggregated STFT Data:** - Save the aggregated STFT DataFrame to a CSV file with the appropriate naming convention.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 critical
Block Progress
 documentation
Improvements or additions to documentation
 documentclass
Improvements or additions to LaTeX documentclass
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 latex
Related to the writings
 question
Further information is requested
 wontfix
This will not be worked on
No Label enhancement
Milestone
No items
No Milestone Implement STFT as Alternative Workarounds
Projects
Clear projects
No project
Assignees
Clear assignees
nuluh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nuluh/thesis#24
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?