[EXP] CANDELS big mosaic visualization #113
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome! I'll take a look. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This notebook is an example to visualize a CANDELS mosaic image that is a single-extension FITS with the file size of 4.9 GB. The conclusion of this exercise is that I think Ginga can handle big mosaic natively as-is. I am not sure if this PR needs to be merged; I opened this so others can play around with this notebook on different machines and report back any problems. I did not notice any spikes in memory usage; I think the
memmaphelps a lot here.p.s. Similar conclusion for Ginga standalone GUI but I did not try using all the plugins on this data, just
PickandHistogram.cc @hcferguson
Example screenshot