Enhancement: Getting a result from the FFT API

AKMaily commented 2 months ago

Location: Generate Training data menu , send button

After the user pressed the send button the waveform he selected is send to the FFT API as a JSON Object. Right now the /check-request endpoint is used.

The enhancement is to change the /check-request endpoint to the /analyze endpoint. The /analyze endpoint gives back a result described in the documentation of the FFT API. This result should be saved in a new .csv file called Analysis_"old measurement_name" in a /analysis folder in the directory where the OmniView.exe is saved. In this .csv file the result is saved as two columns, the first one is the frequency and the second one is the corresponding amplitude.

R-Abbasi commented 1 month ago

Using current code, https://api.auto-intern.de/analyze's response to sending a .csv file is Internal Server Error. Is the API code under development, please? Capture1

R-Abbasi commented 1 month ago

As well as, the Validation Error with the array loc with values of heterogeneous types looks a little unusual to me.

 "detail": [
    {
      "loc": [
        "string",
        0
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}

dobe-1 commented 1 month ago

There was an issue with the type declaration of the sampling rate. The sampling rate must be an integer and not a float and must always be specified in hertz. The fixed version will deployed soon as possible.

The Validation Error is a predefined error class of the pydantic library that we use for input validation.

R-Abbasi commented 1 month ago

https://github.com/skunkforce/OmniView/pull/116

skunkforce / OmniView

Enhancement: Getting a result from the FFT API #115