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

Issue 53 spline segmentation export #63

Closed

Conversation

jpdefrutos
Copy link
Collaborator

Rescaled the spline segmentations to match the spacing of the original image (if this is anisotropic).

To correct the alignment, the 'Offset' attribute of MHD images was exposed in the MetaImage class. This is then set in the segmentation image metadata.

jpdefrutos and others added 18 commits November 18, 2021 19:26
Define the "CopyContentButton" block in those apps that need this functionality. See boundingbox\process_image.html

views.py --> removed typo
Removed qoutation marks from CopyContentButton onclick (boundingbox/process_image.py)
Added ; to lines in copyToNext function (annotationweb.js)
I noticed that when hovering over the canvas and scrolling, the current frame number incremented/decremented beyond the range of frames (for me, below 0 and above the total number of frames). The same bug happened with key left/right presses.

I added an if-statement in annotationweb.js that seems to fix the problem.
# Conflicts:
#	annotationweb/models.py
#	annotationweb/settings.py
#	annotationweb/urls.py
…xporting anisotropic data. This will happen whenever the metadata of the original image is provided in the new optional argument image_metadata of the method save_segmentation().

Exposed the attribute Offset from the MHD header. This can be used to correctly align the annotations to the frame when exporting the data.

When exporting non-mhd images, skip loading the image metadata when saving the segmentations.
@jpdefrutos jpdefrutos closed this Apr 28, 2023
@jpdefrutos jpdefrutos reopened this Apr 28, 2023
@jpdefrutos jpdefrutos closed this Apr 28, 2023
@jpdefrutos
Copy link
Collaborator Author

Lot of merge conflicts. Need to PR the base first, and then code the fix for issue #53

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