Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heatmap not working after update to 1.1.9 #184

Open
piotrvidal opened this issue Nov 4, 2022 · 2 comments
Open

Heatmap not working after update to 1.1.9 #184

piotrvidal opened this issue Nov 4, 2022 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@piotrvidal
Copy link

Describe the bug
Heatmap not showing up when activated in the "display" menu.

To Reproduce
Steps to reproduce the behavior:

  1. Start program with command-line 'trex'
  2. Open an already converted video (a video converted with 1.1.9 version)
  3. Click on display > heatmap
  4. No heatmap appears

If possible, please also include the full terminal output as a file attachment:
[10:13:58] Property('gui_show_heatmap') = true
[10:13:58] Creating a grid of size 1x1 (for image of size 1280x720)
[10:13:58] -------------------
[10:13:58] STATS (frame 0, [])
Grid::clear: 0.000984ms
Grid::fill: 0.949012ms
Heatmap::update_data(): 1.3736ms

[10:13:58]

A grid of size 1x1 for image size 1280x720 seems weird?

Expected behavior (if it is not a simple crash)
The heatmap appears over the video, like in 1.1.6 version.

Computer (please complete the following information):

  • Operating system: Parrot OS
  • Build hash: 4ce4be1
  • Terminal used: Mate Terminal
@piotrvidal piotrvidal added the bug Something isn't working label Nov 4, 2022
@piotrvidal
Copy link
Author

To add further info on this issue:

On 1.1.6, when activating the heatmap, the terminal outputs:

[06:33:31] Creating a grid of size 2048x2048 (for image of size 1280x720)

mooch443 pushed a commit that referenced this issue Nov 30, 2022
@mooch443
Copy link
Owner

mooch443 commented Dec 5, 2022

Took some time, but I added a fix to the development branch. You can try it out in the trex-beta channel (e.g. conda create -n beta -c trex-beta trex), if you like. Not sure if it is fixed since it seems to be particular to this resolution somehow, but let's hope that it is :-) Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants