line / line/lighthouse

Uniform predictions (identical saliency scores) during TVSum dataset evaluation with Lighthouse pipeline

Open
#50 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
269
Forks
20
Avg merge
7h 3m
Merged PRs (30d)
2

Description

When evaluating the Lighthouse model on the TVSum dataset using the provided scripts, the model outputs identical highlight scores across all time windows, despite following the tutorial steps.
eval_command:
python /lighthouse/training/evaluate.py --model uvcom --dataset tvsum --feature i3d_clip --domain BK --split val --model_path checkpoints/results/uvcom/tvsum/i3d_clip/BK/best.ckpt --eval_path data/tvsum/tvsum_val_release.jsonl
I printed out the saliency score predictions during the evaluation, and a screenshot is attached below to show the output.

![Image](https://github.com/user-attachments/assets/0a01c1d2-f4f4-406f-a26a-ddee1a55bf78)

1.Are there known issues with TVSum evaluation in the current version?

2.Could the problem stem from data loading or post-processing steps or shape problem of loaded features? \
However, i downloaded all the checkpoints and extracted-features from the link on lighthouse repo page.
Appreciate your guidance to resolve this issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with training/evaluate.py and reproduce the issue using the provided TVSum evaluation command, checkpoint, and JSONL path. Inspect the loaded i3d_clip feature shapes, data loading, and post-processing while comparing the predicted scores across time windows. Done means identifying the cause of the identical predictions and confirming that evaluation produces non-uniform scores.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-vision, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.