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

Importing objects from .qpdata including TMA cores can result in an 'invisible' TMA grid #1303

Closed
petebankhead opened this issue Aug 28, 2023 · 1 comment · Fixed by #1345
Assignees
Labels
Milestone

Comments

@petebankhead
Copy link
Member

Bug report

Describe the bug
Importing objects from a .qpdata file containing TMA cores can result in the cores being brought over, but not properly assigned to a TMA grid. As a result, they are 'selectable' and appear under the 'Hierarchy' tab, but are otherwise not visible.

To Reproduce
Steps to reproduce the behavior:

  1. Create a project with 2 images
  2. Add a TMA grid to one (e.g. Specify TMA grid)
  3. Save the data
  4. Open the second image
  5. Drag the .qpdata file from the first image onto the QuPath viewer
  6. See the weird hierarchy behavior

Expected behavior

  1. If there is a TMA grid on the second image already, offer to replace it with the one from the .qpdata file
  2. If there is no TMA grid on the second image, import it 'properly'

Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot 2023-08-28 at 09 33 12

Desktop (please complete the following information):

  • OS: All
  • QuPath Version: v0.4.3 (and likely earlier)

Additional context
See https://forum.image.sc/t/tma-core-missing/85571

@petebankhead petebankhead self-assigned this Sep 11, 2023
@petebankhead petebankhead added this to the v0.5.0 milestone Sep 11, 2023
petebankhead added a commit to petebankhead/qupath that referenced this issue Sep 23, 2023
@petebankhead
Copy link
Member Author

Now 'fixed' in the sense that TMA cores are filtered out when importing objects. That seems better than importing them very very badly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant