Skip to content

Conversation

adamjstewart
Copy link
Member

@adamjstewart adamjstewart commented Feb 3, 2025

Related to #1263

The current plotting method works great for our dataset, but fails as soon as normalization is added (e.g., via our data module). By using percentile normalization, both the dataset and data module should work.

P.S. We should do this for all datasets if anyone is ever bored and looking for an easy contribution. I only did EuroSAT because it's used throughout our tutorials.

@adamjstewart adamjstewart added this to the 0.6.3 milestone Feb 3, 2025
@github-actions github-actions bot added the datasets Geospatial or benchmark datasets label Feb 3, 2025
@calebrob6
Copy link
Collaborator

I don't think percentile normalization is a good way to get around whatever effects that the augmentations/normalization step adds. In some cases (e.g. I'm augmenting color or brightness) I'd like to be able to see differences between samples clearly. Having a reverse augmentation step is a better way to handle that case.

image = np.clip(image / 3000, 0, 1) produces very reasonable looking output that you can compare between images, why change this?

@adamjstewart
Copy link
Member Author

I'm also fine with a reverse normalization in the trainer/task/module/thingy. I've never actually tried it before, how straightforward is it to use? Does it have issues with cropping? Let me see how much work this is to do.

@adamjstewart adamjstewart marked this pull request as draft February 3, 2025 12:50
@adamjstewart adamjstewart removed this from the 0.6.3 milestone Feb 23, 2025
@adamjstewart
Copy link
Member Author

Superseded by #2560

@adamjstewart adamjstewart deleted the datasets/eurosat branch February 23, 2025 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datasets Geospatial or benchmark datasets
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants