Add SSL4EO-L Benchmark to docs #1719
Merged
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
github-actions
bot
added
the
documentation
adamjstewart
changed the title
|
Good catch! Should we also add this to Yes, we should have an entry for every family of datasets in both the docs and the tables. |
nilsleh
commented
Nov 10, 2023
adamjstewart
approved these changes
Nov 10, 2023
nilsleh
added a commit
that referenced
this pull request
Nov 10, 2023
* add benchmark SSL4EOL to docs * proposal entry table * readable name * put full number of classes in table
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.
I think we forgot to add the SSL4EO Benchmark Dataset/Datamodule to the Docs. Do you want to put entries for all possible constillations in the csv file?