Challenge Guidelines

  • Each participant can only be a member of a single team (1 person can be considered a team)
  • Multiple Grand challenge profiles or a member apart of multiple teams will be disqualified.
  • To qualify for ranking on the validation/testing leaderboards, true names and affiliations [university, institute or company (if any), country] must be displayed accurately on verified Grand Challenge profiles, for all participants.
  • Participants of the AortaSeg24 challenge, as well as all non-participating researchers using the training data or test data for benchmarking purposes, CAN NOT publish their own results at any time, during or after the challenge.
  • No additional training dataset is allowed. This ensures fairness and consistency across submissions from all participating teams.
  • Participants affiliated with the organizing institution, 'University of Florida', are not eligible to participate in this challenge.
  • All teams are required to sign a data usage agreement (DUA) before downloading data under the IRB protocol.
  • After the challenge, participating teams can continue to use the data for non-commercial research purposes but must cite the challenge conclusion paper if they incorporate this dataset into their own publications.
  • The organizers of the challenge reserve the right to disqualify any participant or participating team, at any point in time, on grounds of unfair or dishonest practices.
  • All participants have the right to exit the AortaSeg24 challenge at any time.
  • A validation dataset will be available in May, enabling participating teams to develop and validate their models.
  • The performance results of all teams will be made publicly available.
  • To be considered for a participation certificate you must successfully submit your docker containers to the challenge website as well as submit a 4-page technical paper.
  • Participating teams will be required to submit their 4-page technical paper along with a URL link to the GitHub repository containing the code for their implementations, in order to be considered as a co-author of the challenge paper.
  • Teams that achieve a test score higher than the baseline score and submit a 4-page technical paper describing their methods and results will be invited to co-author a journal paper about the challenge.