Add CCAgT dataset
NONE
_The documentation is not available anymore as the PR was closed or merged._
2022-06-15T13:52:46Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1156503852
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5E7tks
https://api.github.com/repos/huggingface/datasets/issues/comments/1156503852/reactions
2022-07-04T14:37:03Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1156503852
https://avatars.githubusercontent.com/u/99929124?v=4
https://api.github.com/users/HuggingFaceDocBuilderDev/events{/privacy}
https://api.github.com/users/HuggingFaceDocBuilderDev/followers
https://api.github.com/users/HuggingFaceDocBuilderDev/following{/other_user}
https://api.github.com/users/HuggingFaceDocBuilderDev/gists{/gist_id}
https://github.com/HuggingFaceDocBuilderDev
HuggingFaceDocBuilderDev
U_kgDOBfTMJA
https://api.github.com/users/HuggingFaceDocBuilderDev/orgs
https://api.github.com/users/HuggingFaceDocBuilderDev/received_events
https://api.github.com/users/HuggingFaceDocBuilderDev/repos
https://api.github.com/users/HuggingFaceDocBuilderDev/starred{/owner}{/repo}
https://api.github.com/users/HuggingFaceDocBuilderDev/subscriptions
User
https://api.github.com/users/HuggingFaceDocBuilderDev
public
COLLABORATOR
Hi! Excellent job @johnnv1! There were typos/missing words in the card, so I took the liberty to rewrite some parts to make them easier to understand. Let me know if you are ok with the changes. Also, feel free to add some info under the `Who are the annotators?` section.

Additionally, I fixed the issue with streaming and renamed the `digits` feature to `objects`.

@lhoestq Are you ok with skipping the dummy data test here as it's tricky to generate it due to the splits separation logic?
2022-06-15T14:00:49Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1156513639
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5E7v9n
https://api.github.com/repos/huggingface/datasets/issues/comments/1156513639/reactions
2022-06-15T14:00:49Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1156513639
https://avatars.githubusercontent.com/u/47462742?v=4
https://api.github.com/users/mariosasko/events{/privacy}
https://api.github.com/users/mariosasko/followers
https://api.github.com/users/mariosasko/following{/other_user}
https://api.github.com/users/mariosasko/gists{/gist_id}
https://github.com/mariosasko
mariosasko
MDQ6VXNlcjQ3NDYyNzQy
https://api.github.com/users/mariosasko/orgs
https://api.github.com/users/mariosasko/received_events
https://api.github.com/users/mariosasko/repos
https://api.github.com/users/mariosasko/starred{/owner}{/repo}
https://api.github.com/users/mariosasko/subscriptions
User
https://api.github.com/users/mariosasko
public
NONE
I think I can also add instance segmentation: by exposing the segment of each instance, so it will be similar with object detection:

- `instances`: a dictionary containing bounding boxes, segments, and labels of the cell objects 
  - `bbox`: a list of bounding boxes
  - `segment`: a list of segments in format of `[polygon]`, where each polygon is `[x0, y0, ..., xn, yn]`
  - `label`: a list of integers representing the category

Do you think it would be ok?
2022-06-15T14:46:24Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1156568633
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5E79Y5
https://api.github.com/repos/huggingface/datasets/issues/comments/1156568633/reactions
2022-06-15T14:47:11Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1156568633
https://avatars.githubusercontent.com/u/20444345?v=4
https://api.github.com/users/johnnv1/events{/privacy}
https://api.github.com/users/johnnv1/followers
https://api.github.com/users/johnnv1/following{/other_user}
https://api.github.com/users/johnnv1/gists{/gist_id}
https://github.com/johnnv1
johnnv1
MDQ6VXNlcjIwNDQ0MzQ1
https://api.github.com/users/johnnv1/orgs
https://api.github.com/users/johnnv1/received_events
https://api.github.com/users/johnnv1/repos
https://api.github.com/users/johnnv1/starred{/owner}{/repo}
https://api.github.com/users/johnnv1/subscriptions
User
https://api.github.com/users/johnnv1
public
NONE
Don't you think it makes sense to keep the same category IDs for all approaches? 

Now we have:
 - nucleus category ID equals 0 for object detection and instance segmentation
 - background category ID equals 0 (on the masks) for semantic segmentation
2022-06-15T16:54:58Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1156712654
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5E8gjO
https://api.github.com/repos/huggingface/datasets/issues/comments/1156712654/reactions
2022-06-15T16:54:58Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1156712654
https://avatars.githubusercontent.com/u/20444345?v=4
https://api.github.com/users/johnnv1/events{/privacy}
https://api.github.com/users/johnnv1/followers
https://api.github.com/users/johnnv1/following{/other_user}
https://api.github.com/users/johnnv1/gists{/gist_id}
https://github.com/johnnv1
johnnv1
MDQ6VXNlcjIwNDQ0MzQ1
https://api.github.com/users/johnnv1/orgs
https://api.github.com/users/johnnv1/received_events
https://api.github.com/users/johnnv1/repos
https://api.github.com/users/johnnv1/starred{/owner}{/repo}
https://api.github.com/users/johnnv1/subscriptions
User
https://api.github.com/users/johnnv1
public
COLLABORATOR
I find it weird to have a dummy label in object detection just to align the mapping with semantic segmentation. Instead, let's explain in the card (under Data Fields -> annotation) what the pixel values mean (background + object detection labels)
2022-06-15T17:39:06Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1156753707
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5E8qkr
https://api.github.com/repos/huggingface/datasets/issues/comments/1156753707/reactions
2022-06-15T17:39:06Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1156753707
https://avatars.githubusercontent.com/u/47462742?v=4
https://api.github.com/users/mariosasko/events{/privacy}
https://api.github.com/users/mariosasko/followers
https://api.github.com/users/mariosasko/following{/other_user}
https://api.github.com/users/mariosasko/gists{/gist_id}
https://github.com/mariosasko
mariosasko
MDQ6VXNlcjQ3NDYyNzQy
https://api.github.com/users/mariosasko/orgs
https://api.github.com/users/mariosasko/received_events
https://api.github.com/users/mariosasko/repos
https://api.github.com/users/mariosasko/starred{/owner}{/repo}
https://api.github.com/users/mariosasko/subscriptions
User
https://api.github.com/users/mariosasko
public
NONE
Ok, I can do that in the next few days. I will create a `lapix` organization, and I will add this dataset and also #4565
2022-07-01T11:55:45Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1172266331
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5F311b
https://api.github.com/repos/huggingface/datasets/issues/comments/1172266331/reactions
2022-07-01T11:55:45Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1172266331
https://avatars.githubusercontent.com/u/20444345?v=4
https://api.github.com/users/johnnv1/events{/privacy}
https://api.github.com/users/johnnv1/followers
https://api.github.com/users/johnnv1/following{/other_user}
https://api.github.com/users/johnnv1/gists{/gist_id}
https://github.com/johnnv1
johnnv1
MDQ6VXNlcjIwNDQ0MzQ1
https://api.github.com/users/johnnv1/orgs
https://api.github.com/users/johnnv1/received_events
https://api.github.com/users/johnnv1/repos
https://api.github.com/users/johnnv1/starred{/owner}{/repo}
https://api.github.com/users/johnnv1/subscriptions
User
https://api.github.com/users/johnnv1
public
NONE
So, I think we can close this PR? I have already moved these files there.

The link of CCAgT dataset is: https://huggingface.co/datasets/lapix/CCAgT

🤗 
2022-07-01T12:38:48Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1172302830
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5F3-vu
https://api.github.com/repos/huggingface/datasets/issues/comments/1172302830/reactions
2022-07-01T12:38:48Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1172302830
https://avatars.githubusercontent.com/u/20444345?v=4
https://api.github.com/users/johnnv1/events{/privacy}
https://api.github.com/users/johnnv1/followers
https://api.github.com/users/johnnv1/following{/other_user}
https://api.github.com/users/johnnv1/gists{/gist_id}
https://github.com/johnnv1
johnnv1
MDQ6VXNlcjIwNDQ0MzQ1
https://api.github.com/users/johnnv1/orgs
https://api.github.com/users/johnnv1/received_events
https://api.github.com/users/johnnv1/repos
https://api.github.com/users/johnnv1/starred{/owner}{/repo}
https://api.github.com/users/johnnv1/subscriptions
User
https://api.github.com/users/johnnv1
public
MEMBER
Woohoo awesome !

closing this PR :)
2022-07-04T14:25:45Z
https://github.com/huggingface/datasets/pull/4486#issuecomment-1173882166
https://api.github.com/repos/huggingface/datasets/issues/4486
IC_kwDODunzps5F-AU2
https://api.github.com/repos/huggingface/datasets/issues/comments/1173882166/reactions
2022-07-04T14:25:45Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1173882166
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public
As described in #4075 

I could not generate the dummy data. Also, on the data repository isn't provided the split IDs, but I copy the functions that provide the correct data split. In summary, to have a better distribution, the data in this dataset should be separated based on the amount of NORs in each image.