meva-data-repo issueshttps://gitlab.kitware.com/meva/meva-data-repo/-/issues2023-03-21T11:42:35-04:00https://gitlab.kitware.com/meva/meva-data-repo/-/issues/6Public data not available on AWS2023-03-21T11:42:35-04:00Bhavay MalhotraPublic data not available on AWSI tried downloading the public dataset available on the AWS website. I used AWS-CLI and Boto3 but I'm not able to download the data using both. Is anybody else having this issue and knows possible solution? Is the data still publicly ava...I tried downloading the public dataset available on the AWS website. I used AWS-CLI and Boto3 but I'm not able to download the data using both. Is anybody else having this issue and knows possible solution? Is the data still publicly available on aws?https://gitlab.kitware.com/meva/meva-data-repo/-/issues/5CMU-v2 track-id (id1) in activities.yaml not found in geom.yaml2021-09-13T14:29:02-04:00Jeffrey ByrneCMU-v2 track-id (id1) in activities.yaml not found in geom.yamlThere are a large number of track-ids (id1) referenced in activities.yaml that have no associated geometry in the geom.yaml. Is this expected? For example:
vipy/dataset/meva.py:224: UserWarning: ActorID 9238 referenced in activity yam...There are a large number of track-ids (id1) referenced in activities.yaml that have no associated geometry in the geom.yaml. Is this expected? For example:
vipy/dataset/meva.py:224: UserWarning: ActorID 9238 referenced in activity yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-activities.yml" not found in geom yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-geom.yml" - Skipping
vipy/dataset/meva.py:224: UserWarning: ActorID 9239 referenced in activity yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-activities.yml" not found in geom yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-geom.yml" - Skipping
vipy/dataset/meva.py:224: UserWarning: ActorID 9240 referenced in activity yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-activities.yml" not found in geom yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-geom.yml" - Skipping
vipy/dataset/meva.py:224: UserWarning: ActorID 9241 referenced in activity yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-activities.yml" not found in geom yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-geom.yml" - Skipping
vipy/dataset/meva.py:224: UserWarning: ActorID 9242 referenced in activity yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-activities.yml" not found in geom yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-geom.yml" - Skipping
vipy/dataset/meva.py:224: UserWarning: ActorID 9243 referenced in activity yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-activities.yml" not found in geom yaml "annotation/DIVA-phase-2/MEVA/contrib/CMU-v2/2018-03-09/10/2018-03-09.10-30-00.10-35-00.hospital.G479-geom.yml" - Skipping
https://gitlab.kitware.com/meva/meva-data-repo/-/issues/4Invalid bounding boxes2021-09-13T13:52:43-04:00Jeffrey ByrneInvalid bounding boxesHello,
The following are invalid bounding boxes in the current meva_annotations. Easily ignored, but probably worth fixing in the authoritative annotations.
[vipy.dataset.meva][5/266]: Parsing "/divamnt/0066/mevadata-public-01/meva-...Hello,
The following are invalid bounding boxes in the current meva_annotations. Easily ignored, but probably worth fixing in the authoritative annotations.
[vipy.dataset.meva][5/266]: Parsing "/divamnt/0066/mevadata-public-01/meva-data-repo/annotation/DIVA-phase-2/MEVA/meva-annotations/2018-03-07/17/2018-03-07.17-25-00.17-30-00.bus.G506.activities.yml"
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=59.0, width=-22.0, height=-38.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=56.0, width=-22.0, height=-32.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=53.0, width=-21.0, height=-27.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=51.0, width=-21.0, height=-22.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=48.0, width=-21.0, height=-16.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=45.0, width=-21.0, height=-10.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=42.0, width=-20.0, height=-5.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1613.0, ymin=40.0, width=-20.0, height=0.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=37.0, width=-19.0, height=6.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=34.0, width=-18.0, height=11.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=31.0, width=-18.0, height=17.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=28.0, width=-18.0, height=23.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=26.0, width=-18.0, height=28.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=23.0, width=-17.0, height=33.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1612.0, ymin=20.0, width=-17.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1611.0, ymin=20.0, width=-15.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1610.0, ymin=20.0, width=-12.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1609.0, ymin=20.0, width=-10.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1607.0, ymin=20.0, width=-7.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1606.0, ymin=20.0, width=-4.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - Ignoring
/proj/diva3/visym/vipy/vipy/dataset/meva.py:140: UserWarning: Invalid bounding box: id1=1674167344722454400, bbox="<vipy.geometry.boundingbox: xmin=1605.0, ymin=20.0, width=-2.0, height=39.0>", file="2018-03-07.17-25-00.17-30-00.bus.G506.geom.yml" - IgnoringRoddy CollinsRoddy Collinshttps://gitlab.kitware.com/meva/meva-data-repo/-/issues/3still having problems merging my branch2020-02-04T22:09:41-05:00Lisa Brownstill having problems merging my branchI’m still having trouble with merging the new annotations from all the teams - I been trying to get help but so far no replies - I created the new merge request - selected my branch - when it “checks” it gives me a “something went wrong”...I’m still having trouble with merging the new annotations from all the teams - I been trying to get help but so far no replies - I created the new merge request - selected my branch - when it “checks” it gives me a “something went wrong” msg (and I am logged in as lisabrster@gmail.com) - thanks for your help and getting this question to the right personJonathan FiscusJonathan Fiscus2020-02-10https://gitlab.kitware.com/meva/meva-data-repo/-/issues/2problem with merge request2020-01-27T09:09:09-05:00Lisa Brownproblem with merge requestI have been unable to make a merge request - I choose my changes but when I hit compare branches and continue - I get the "whoops something went wrong"
I am trying to add all the current annotations from all teams.
Thanks for your help...I have been unable to make a merge request - I choose my changes but when I hit compare branches and continue - I get the "whoops something went wrong"
I am trying to add all the current annotations from all teams.
Thanks for your help,
LisaRoddy CollinsRoddy Collinshttps://gitlab.kitware.com/meva/meva-data-repo/-/issues/1access to push2020-01-21T12:14:51-05:00Lisa Brownaccess to push
Hi -
I would like to add new annotation to the mevadata repo
my username on gitlab.kitware.com is lisabrster@gmail.com
I was able to git clone, create the branch - but I was not able to push my new branch.
Also - We made yml files ...
Hi -
I would like to add new annotation to the mevadata repo
my username on gitlab.kitware.com is lisabrster@gmail.com
I was able to git clone, create the branch - but I was not able to push my new branch.
Also - We made yml files according to your specs but not for each video/date.
Lisa Brown
IBM DIVA team