Eon Tuner fails to identify my axes

Report bugs
, , ,
#1

Question/Issue:
When running Eon Tuner, I receive multiple logs (>50) as the one shown bellow, and the searching process fails:

“WARN: failed to process 735229/split/r2b_vibracao_carcaca_e_Ia_torque_40_ensaio_10.s2.json.5v5gq9cn.ingestion-7d8b657c77-bmm5g.json: Cannot process file, impulse requires axis “csv”, but not present in this file (found: “Vibracao”, “Corrente”) - note: axes are case sensitive.”

Project ID:
735229

Context/Use case:
It happens whenever I try to use my data (that I upload through csv wizard).

Summary:
Eon Tuner fails because the impulse expects axis "csv", but the uploaded data via CSV Wizard has axes "Vibracao" and "Corrente" (case-sensitive mismatch).

Steps to Reproduce:

  1. Upload data through csv wizard (each file has 2 columns of data)
  2. Select, in the DSP blocks, only one data column
  3. Run Eon Tuner

Expected Results:
Eon Tuner should complete its search.

Actual Results:
Eon tuner fails in each search trial.

Reproducibility:

  • [ X] Always
  • [ ] Sometimes
  • [ ] Rarely

Environment:

  • Platform: [e.g., Raspberry Pi, nRF9160 DK, etc.]
  • Build Environment Details: [e.g., Arduino IDE 1.8.19 ESP32 Core for Arduino 2.0.4]
  • OS Version: [e.g., Ubuntu 20.04, Windows 10]
  • Edge Impulse Version (Firmware): [e.g., 1.2.3]
    To find out Edge Impulse Version:
  • if you have pre-compiled firmware: run edge-impulse-run-impulse --raw and type AT+INFO. Look for Edge Impulse version in the output.
  • if you have a library deployment: inside the unarchived deployment, open model-parameters/model_metadata.h and look for EI_STUDIO_VERSION_MAJOR, EI_STUDIO_VERSION_MINOR, EI_STUDIO_VERSION_PATCH
  • Edge Impulse CLI Version: [e.g., 1.5.0]
  • Project Version: [e.g., 1.0.0]
  • Custom Blocks / Impulse Configuration: [Describe custom blocks used or impulse configuration]
    Logs/Attachments:
    [Include any logs or screenshots that may help in diagnosing the issue]

Logs/Attachments:
[Include any logs or screenshots that may help in diagnosing the issue]

Additional Information:
[Any other information that might be relevant to the issue]

#2

Hi @Alan_S_G7 - welcome to the forum! I’ve asked our engineering team for some additional support on this one.

#3

While we wait for some more info. Let’s try a couple of things.

Looking at your tuner template, it looks like you created it from an existing impulse?

In the DSP block section of your template, for each block configuration that you want to test, could you please manually add the axes you want to include:

"dspBlocks": [
      {
        "type": "spectral-analysis",
        "implementationVersion": 4,
        "normalizeData": [
          "normalize-channel-standard-scaler"
        ],
        "id": 19,
        "axes": ["Corrente"],
     
        ...

        }

        ...

],