Closed
Conversation
Collaborator
|
The existing data source https://github.com/allenai/rslearn/blob/master/rslearn/data_sources/aws_google_satellite_embedding_v1.py also pulls from the Source Cooperative data but using it from their AWS S3 bucket, is there a substantial difference with this one? For the bands, since we have |
Collaborator
Author
|
I wasn't aware of the existing data source, will switch to using that (although no immediate plans to use it again). Thanks |
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
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.
use_all_bands_in_order_of_band_set_idxso AlphaEarth embeddings can be consumed in model configs without repeating band names.-2.0in dequantized mode and-128in raw mode when nodata_vals is not specified.ingest: falsebecause annual TIFFs are large, and clarified dequantized embedding semantics, including that exact unit norm is only approximate after quantization and that optional L2 re-normalization may be useful for cosine-based workflows.num_bandswith a custom prefix, start index, and zero padding, allowing AlphaEarth’s 64 bands to be configured without listing them explicitly.Example config
Materialised raster