phases dates are not able to sync for challenge

[displace2026]

Dear Codabench Support Team,

I hope you are doing well.

I am writing to seek your kind assistance regarding the scheduling of Phase 2 for our challenge, DISPLACE-M Challenge (Challenge ID: 13833), hosted on Codabench.

Phase 1 of the challenge has been successfully completed, and we are now preparing to initiate Phase 2. We intend to set the Phase 2 timeline from April 1, 2026, to May 1, 2026. However, due to the current phase configuration and platform constraints, we are facing difficulties in updating the Phase 2 dates accordingly.

We kindly request your support in helping us resolve this issue or guiding us on how to properly configure the phases so that we can proceed smoothly with the next stage of the challenge.

For your reference, the challenge can be accessed here:
https://www.codabench.org/competitions/13833

We sincerely appreciate your time and assistance, and we look forward to your guidance.

Thank you for your support.

Warm regards,
DISPLACE Organiser

[Didayolo]

Dear @displace2026,

What issue are you facing with the scheduling?

You can set the start and end times of each phase in the editor.

Go to "EDIT", then "Phases":

Then click on the blue logo to edit the phase and set the dates:

Once everything is set, save the changes.

Note that all phases' dates must be coherently set (without intersection) before you can save.

[displace2026]

Dear Codabench Support Team,

Thank you for your previous response and guidance.

Based on your suggestion, we understand that the phases can be structured sequentially as follows:

Track 1 Phase II → April 1 – April 10
Track 2 Phase II → April 10 – April 20
Track 3 Phase II → April 20 – April 25
Track 4 Phase II → April 25 – May 1

While this approach is clear and workable, our original intention is to schedule Phase 2 for all four tracks concurrently, within the common time window of April 1, 2026, to May 1, 2026.

However, due to the current phase configuration—initially defined via a YAML file—the platform has accepted a structure where phases are arranged sequentially across tracks. As a result, we are now facing difficulties in assigning the same Phase 2 timeline to all tracks. The system enforces a strictly sequential phase order, which prevents overlapping or parallel Phase 2 schedules.

In this context, we kindly request your guidance and support in resolving this issue. Specifically, we would appreciate your assistance in either:

1. Enabling a configuration that allows Phase 2 to run simultaneously across all tracks, or

2. Advising on the best way to restructure the phases without impacting the already completed Phase 1.

Your support will be invaluable in helping us proceed smoothly with the next stage of the challenge.

Thank you very much for your time and assistance.

Warm regards,
DISPLACE Organiser

[Didayolo]

Dear @displace2026,

The phase system of Codabench only allows sequential phases.

You need either to:

• Do everything inside one phase April 1 --> May 1 (e.g. with several tasks associated to the same phase)
• Have a separate Codabench competition (and URL) for each concurrent track

Once you know which solution is better in your case, we can discuss how to implement this together if needed.

[displace2026]

Dear Codabench Support Team,

Thank you for your previous response and guidance.

Do everything inside one phase April 1 --> May 1 (e.g. with several tasks associated to the same phase)

It would be great if you suggest how to proceed for this step.

Thanks

DISPLACE Organiser

[Didayolo]

I can see that you have distinct tasks for each "phase":

• Diarization Eval Phase II Task
• ASR Eval Phase II Task
• Topic Identification Eval Phase II Task
• Summarization Eval Phase II Task

You can edit/create a task with the right dates and add all tasks to it from the interface:

That means that all new submissions will automatically be forwarded to all selected tasks.

The remaining question is: Can each task accept the same submission? Otherwise you'll need to group the submissions to all tasks inside every submission, and have the evaluation program of each task able to read the code/results they need.

The second case is annoying if you wanted participants to be able to submit independently to each task. (Submitting independently to each task is an interesting feature but is not implemented in the current version of Codabench #1711).

If that is problematic, the alternative is having a separate competition for each track.