[FEAT] Add export to csv method for DataProcessor in convert.py #40

Closed
opened 2025-03-22 13:30:39 +00:00 by nuluh · 0 comments
nuluh commented 2025-03-22 13:30:39 +00:00 (Migrated from github.com)

Problem Statement

Working with direct object processed data seems quite a lot of effort to put in when it comes to STFT processing pipeline in the current ipynb (stft.ipynb) that use CSV file with pre-defined format naming.

Proposed Solution

Add new method like export_to_csv that retrieve arguments like output_path. The method should follow the current python notebook CSV file format naming as its input pipeline.

Alternatives Considered

No response

Component

Data Processing

Priority

Critical (blocks progress)

Implementation Ideas

No response

Expected Benefits

This will save time to try the model accuracy as soon as possible using outside of its training data.

Additional Context

No response

### Problem Statement Working with direct object processed data seems quite a lot of effort to put in when it comes to STFT processing pipeline in the current ipynb (stft.ipynb) that use CSV file with pre-defined format naming. ### Proposed Solution Add new method like `export_to_csv` that retrieve arguments like `output_path`. The method should follow the current python notebook CSV file format naming as its input pipeline. ### Alternatives Considered _No response_ ### Component Data Processing ### Priority Critical (blocks progress) ### Implementation Ideas _No response_ ### Expected Benefits This will save time to try the model accuracy as soon as possible using outside of its training data. ### Additional Context _No response_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nuluh/thesis#40