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

Track renderer regions does not properly adjust the region if the dataset extents get larger without moving #3527

Closed
StasJ opened this issue Jan 24, 2024 · 6 comments · Fixed by #3529 or #3572
Assignees
Labels

Comments

@StasJ
Copy link
Collaborator

StasJ commented Jan 24, 2024

This might be the case in a particle dataset

@StasJ
Copy link
Collaborator Author

StasJ commented Mar 15, 2024

Test:

  1. Import both timesteps in Bugs/3527 on glade
  2. Add/enable a particle renderer
  3. The particle renderer domain should continue encompass the entire data domain when changing timesteps.

@shaomeng
Copy link
Collaborator

VAPOR crashes when following the steps above to advance time steps.

@shaomeng shaomeng reopened this Mar 18, 2024
@StasJ
Copy link
Collaborator Author

StasJ commented Mar 18, 2024

Do you have any additional steps to reproduce the crash? It works for me.

@shaomeng
Copy link
Collaborator

Do you have any additional steps to reproduce the crash? It works for me.

Hmm, really no additional steps. To be clear, it renders particles at step 0 when the particle renderer is enabled. It crashes upon clicking on the "next step" button. Could @sgpearse @NihanthCW see if they can reproduce the issue?

@sgpearse
Copy link
Collaborator

I am reproducing the crash on casper when following the steps above :(

@StasJ
Copy link
Collaborator Author

StasJ commented Mar 18, 2024

I tested the appimage installer and it does crash on casper. I also tested the old-style installer (https://app.circleci.com/pipelines/github/NCAR/VAPOR/7362/workflows/d68ca9a2-ec1d-4f95-9cde-8b41664c4b46/jobs/18309) generated for the last 3.9.2 code commit (991dcb0) on casper and it does not crash. Either way, investigating this further probably will depend on #3551

StasJ added a commit that referenced this issue Apr 1, 2024
NihanthCW pushed a commit that referenced this issue Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants