GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Creating new competition gives non-meaningful error message: 'data' · Issue #2320 · codalab/codalab-competitions

Creating new competition gives non-meaningful error message: 'data' #2320

New issue
Copy link
New issue
Copy link
Closed
Closed
Creating new competition gives non-meaningful error message: 'data'#2320
Copy link
Assignees
Tthomas63

Description

@nightrome
nightrome
opened on Jun 30, 2018
Issue body actions

Hi, I am trying to create a new challenge and after uploading the zip bundle it gives me the error message

Oops! There was a problem creating the competition: 'data'

I have also tried taking today's dump from my previous challenge, which results in the same error. Any ideas why this is? I noticed that a number of things changed on Codalab since I created the previous challenge (Sept. 2017).

This is the yaml file I am uploading:

title: COCO 2018 Stuff Segmentation Challenge
description: This challenge is designed to push the state of the art in semantic segmentation
  of stuff classes.
start_date: 2018-06-30 00:00:00+00:00
end_date: 2050-01-01 00:00:00+00:00
competition_docker_image: False
image: logo.png
has_registration: True
force_submission_to_leaderboard: False
disallow_leaderboard_modifying: False
enable_detailed_results: True
admin_names: null
html:
  evaluation: evaluation.html
  overview: overview.html
  terms: terms.html
phases:
  0:
    auto_migration: null
    color: white
    datasets:
      0:
        description: ''
        name: Data 1
        url: http://cocodataset.org
    description: The two example images provided in the COCO Stuff API repository.
      The results file can be created by running the pngToCocoResultDemo script. Evaluation
      should take approximately 2 minutes.
    is_scoring_only: true
    label: examples
    max_submissions: 999
    max_submissions_per_day: 999
    phasenumber: 1
    reference_data: reference_data_1.zip
    scoring_program: scoring_program_1.zip
    start_date: 2018-06-30 00:00:00+00:00
leaderboard:
  columns:
    FIOU:
      label: FIOU
      leaderboard: &id001
        label: Results
        rank: 1
      rank: 1
      sort: desc
    FIOUS:
      label: FIOUS
      leaderboard: *id001
      rank: 1
      sort: desc
    MACC:
      label: MACC
      leaderboard: *id001
      rank: 1
      sort: desc
    MACCS:
      label: MACCS
      leaderboard: *id001
      rank: 1
      sort: desc
    MIOU:
      label: MIOU
      leaderboard: *id001
      rank: 1
      sort: desc
    MIOUS:
      label: MIOUS
      leaderboard: *id001
      rank: 1
      sort: desc
    PACC:
      label: PACC
      leaderboard: *id001
      rank: 1
      sort: desc
    PACCS:
      label: PACCS
      leaderboard: *id001
      rank: 1
      sort: desc
  leaderboards:
    Results: *id001

Activity

  1. Tthomas63 commented on Jul 2, 2018

    @Tthomas63
    Tthomas63
    on Jul 2, 2018
    Collaborator
    More actions

    Hello @nightrome,

    Sorry for the inconvenience you've experienced, however it should be an easy fix!

    The main cause of the error you're seeing is a required html file is not defined in your YAML for your competition. The reason the error reads 'data' is because that is the missing key-name is it looking for. The error can be fixed by adding a key called data to the HTML fields, with a value of the name of your desired html file. (See YAML below) The HTML file itself can be blank in this case I believe.

    I've also identified a bug in the competition dump process that makes any boolean field that is currently False, output as null which causes issues in the un-packing process. This is why your competition dump wasn't working, and I should have a fix for this shortly.

    There was also some minor syntax errors in your YAML file that may have been causing some issues for the interpreter. Here's the YAML file I had working for testing:

    title: COCO 2018 Stuff Segmentation Challenge
    description: This challenge is designed to push the state of the art in semantic segmentation of stuff classes.
    start_date: 2018-06-30 00:00:00+00:00
    end_date: 2050-01-01 00:00:00+00:00
    competition_docker_image: ''
    image: logo.png
    has_registration: true
    force_submission_to_leaderboard: false
    disallow_leaderboard_modifying: false
    enable_detailed_results: true
    admin_names: null
    html:
      evaluation: evaluation.html
      overview: overview.html
      terms: terms.html
      data: data.html
    phases:
      0:
        auto_migration: false
        color: white
        datasets:
          0:
            description: null
            name: Data 1
            url: http://cocodataset.org
        description: The two example images provided in the COCO Stuff API repository. The results file can be created by running the pngToCocoResultDemo script. Evaluation should take approximately 2 minutes.
        is_scoring_only: true
        label: examples
        max_submissions: 999
        max_submissions_per_day: 999
        phasenumber: 1
        reference_data: reference_data_1.zip
        scoring_program: scoring_program_1.zip
        start_date: 2018-06-30 00:00:00+00:00
    leaderboard:
      columns:
        FIOU:
          label: FIOU
          leaderboard: &id001
            label: Results
            rank: 1
          rank: 1
          sort: desc
        FIOUS:
          label: FIOUS
          leaderboard: *id001
          rank: 1
          sort: desc
        MACC:
          label: MACC
          leaderboard: *id001
          rank: 1
          sort: desc
        MACCS:
          label: MACCS
          leaderboard: *id001
          rank: 1
          sort: desc
        MIOU:
          label: MIOU
          leaderboard: *id001
          rank: 1
          sort: desc
        MIOUS:
          label: MIOUS
          leaderboard: *id001
          rank: 1
          sort: desc
        PACC:
          label: PACC
          leaderboard: *id001
          rank: 1
          sort: desc
        PACCS:
          label: PACCS
          leaderboard: *id001
          rank: 1
          sort: desc
      leaderboards:
        Results: *id001
    

    Please let me know if you're still experiencing issues after trying the above YAML changes.
    Thanks, and best regards,
    Tyler

  2. Tthomas63
    self-assigned this
    on Jul 2, 2018
  3. nightrome commented on Jul 3, 2018

    @nightrome
    nightrome
    on Jul 3, 2018
    Author
    More actions

    Wow. You are a life saver. The challenge is up and running now. (removed my other request)

  4. nightrome commented on Jul 3, 2018

    @nightrome
    nightrome
    on Jul 3, 2018
    Author
    More actions

    I have a few more questions:

    • Is it possible to not show "Get data" and "Files" on the "Participate" page?
    • When importing - but not actually using - matplotlib I get the following warning on your server. Do you know how to fix that?
    /opt/conda/lib/python2.7/site-packages/matplotlib/font_manager.py:273: UserWarning: Matplotlib is building the font cache using fc-list. This may take a moment.
      warnings.warn('Matplotlib is building the font cache using fc-list. This may take a moment.')
    
  5. Tthomas63 commented on Jul 3, 2018

    @Tthomas63
    Tthomas63
    on Jul 3, 2018
    Collaborator
    More actions

    Hello @nightrome,

    Glad to help! It is possible to not show these pages, by removing them via the competition edit page. However if you create a competition dump and try to re-upload it, you will experience the data error again but it can be fixed the same way.

    Also the matplotlib warning is just letting you know the font-cache is being re-built and may take some time. This happens every run because of how we run submissions in a closed environment. (I think this will affect a code submission's overall execution time)

    See: matplotlib/matplotlib#5640

    Thanks, and best regards,
    Tyler

  6. nightrome
    closed this as completedon Jul 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @Tthomas63
    Tthomas63

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402520 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.