-
Notifications
You must be signed in to change notification settings - Fork 16
Timeline
On this page you can find information about the projected timeline for the mock data challenge. Dates after the submission deadline are subject to change.
- September 30th, 2021: Public announcement of the mock data challenge MLGWSC-1
- October 12th, 2021: Kick-off meeting (introduction and tutorials)
- December 31st, 2021: Deadline for registration
- April 14th, 2022: Submission deadline
- April 21st, 2022: Validation set result confirmation deadline
- April 27th, 2022: Short summary deadline
- April 29th, 2022: Circulation of the collaboration paper draft
- May 11th, 2022: Change request deadline
- May 16th, 2022: Submission of the collaboration paper to journal
- May 28th, 2022: Wrap up meeting
During the entire time there will be support calls on the first Wednesday of every month at 10am, 3pm, and 5pm Berlin time. These support calls start on November 3rd, 2021. For details, please refer to the support page.
Details on the individual items can be found below.
The recording of the kick-off meeting can be found here. The first block with "Welcome and introduction", "Questions & Feedback", and "Introduction to the codebase" spans the time from 0:00:00 - 1:16:42. The gravitational wave tutorial is presented from 1:17:15 - 1:51:34 and the machine learning tutorial is presented from 1:52:30 - 2:59:32.
The kick-off meeting will be used to once again present the goals of this project as well as provide a few basic tutorials. During the kick-off meeting we want to enable groups to get to know each other as well as provide useful information to those who are not yet familiar with gravitational-wave searches based on machine learning. The tutorials will cover only the very basics, such as the expected signal morphologies for the different data sets, the noise characteristics of the detector, or a very basic example of training a neural network to search for gravitational waves. Details on the tutorials can be found here.
Below you can find the schedule
| Time (CEST) | Topic |
|---|---|
| 15:00 - 15:30 | Welcome and introduction |
| 15:30 - 16:00 | Questions and feedback |
| 16:00 - 16:30 | Introduction code base and example code |
| 16:30 - 16:45 | Break |
| 16:45 - 17:30 | Tutorial: Gravitational-wave basics |
| 17:30 - 17:45 | Break |
| 17:45 - 18:30 | Tutorial: Machine learning basics |
Registration is officially closed. However, since we still have capacity, please get in touch with us prior to the Submission deadline at [email protected] if you would still like to participate. You will not yet need to submit any algorithms!
This is the deadline at which you will need to have submitted your algorithm. For details on the submission procedure refer to this page. It is enough to submit your network by this date. The results on the validation set must not yet be confirmed. (See next section for details on the validation results confirmation deadline)
Once you have submitted your algorithm, we will run it on a validation set. The results on this set will be returned for you to validate that the algorithm behaves as expected (for details please refer to this page). This date specifies the last opportunity to give us the okay that the algorithm performs as expected. Any results which were not validated by this date will not be considered for the final publication.
We ask each group to provide a summary of their work of up to three paragraphs. This date is the deadline to provide this summary to the organization team. Please send the summary to [email protected]
We plan to circulate the finished draft of the collaboration paper on this date. Through this groups will get to know the performance of their algorithm on the final test set. Any group may propose changes to the text or retract their contribution. For details on the structure and contents of the paper, please refer to this page.
Up to this date we allow for change requests to be made. Afterwards we will implement the comments to the best of our abilities. Contributions may be retracted even after this deadline.
We plan to host a second meeting once the project is finished. At this meeting we want to give all participants the opportunity to present their work and highlight key-points of their approach. We also want to help connect the community at large.