Open
Conversation
added 7 commits
March 13, 2026 14:38
Changed to: - Output a parquet file metadata instead of a csv - Use one channel url per row
Add a downloader for JUMP pilot TIFF images that builds download jobs from metadata, validates required columns, and maps S3 URLs to local output paths. Supports dry-run previews, optional overwrite behavior, parallel or serial execution, progress logging, and a structured summary of downloaded/skipped/failed files.
Changed channel names of files based on the url names, and added the data
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In this pr the JUMP image metadata is downloaded and processed. Then the image metadata can be filtered to download the desired images from aws S3 using a python utility.
There is an example of how to do this, but I didn't include it in this pr yet. When you review this pr, please let me know where you think this example would fit best. Similarly, I named the utility
4.download_images_from_metadata.pyfor now, but I'd appreciate any feedback on where you think this utility would belong. It will likely be used for both the anomalyze and nuclear speckle prediction projects in the future.Also, I think I am processing the image metadata correctly, however please let me know if I'm not.