Skip to content

Add multilingual QA report support - #16242

Open
paarthneekhara wants to merge 4 commits into
NVIDIA-NeMo:2608_tts_trainingfrom
paarthneekhara:pneekhara/tts-report-qa-support
Open

Add multilingual QA report support#16242
paarthneekhara wants to merge 4 commits into
NVIDIA-NeMo:2608_tts_trainingfrom
paarthneekhara:pneekhara/tts-report-qa-support

Conversation

@paarthneekhara

Copy link
Copy Markdown
Collaborator

No description provided.

@copy-pr-bot

copy-pr-bot Bot commented Sep 11, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

DistributionMetricsRegistry: list[DistributionMetricSpec] = [
DistributionMetricSpec("cer", "CER", True, True, (0.0, 0.3)),
DistributionMetricSpec("utmosv2", "UTMOS v2", False),
DistributionMetricSpec("pred_context_ssim", "SSIM (pred vs context)", False),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we want to remove this one? i feel it is a useful indicator for decision making.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The report unconditionally loads pred_context_ssim for every benchmark to run statistical tests and boxplots. If either evaluation lacks that per-sample field, report generation fails (for text context only manifests I think).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gotcha. then the ideal way is to add a condition to keep this pred_context_ssim for audio context only. what do you think?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we separate it into two? One report for audio and one report for text? It would require 2 constants folders though

@blisc

blisc commented Sep 11, 2026

Copy link
Copy Markdown
Collaborator

I'm good to merge to the training branch. But we should think about how to merge to main if we want to merge to main

@XuesongYang

XuesongYang commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator

this PR fix is not enough to ensure success of supplying new eval artifact dir structure. So i would expect more fixes.

  • previous working eval artifacts structures: {RUN_DIR}/<ckpt>_<inferenceid>_SV_titanet_{DATASET}/{DATASET}_metrics_0.json
  • new failed eval artifacts strcutures: {RUN_DIR}/{DATASET}/<ckpt>_<inferenceid>_SV_titanet_{DATASET}/{DATASET}_metrics_0.json

@paarthneekhara

paarthneekhara commented Sep 12, 2026

Copy link
Copy Markdown
Collaborator Author

The failed artifact structures are because our inference script parallelizes things across datasets so it creates a separate directory per dataset. This way concurrent processes don't try to overwrite the same all metrics csv file. I have updated the slurm eval script to create simlinks once each benchmark eval finishes to create a directory structure that works with our existing report generation tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants