At iDEC, we encourage participants to organize and present their research results in preprint publication. iDEC will establish a preprint publishing system for participating teams.
This means that the contestants should communicate their experimental methods and data as a meaningful story, and present their results, whether positive or negative, in a logical and professional manner.
The report should contain all the information relevant for scoring towards awards. Your report should be written in the format of an academic article, including an abstract (150 words), introduction (500 words), results (2000 words), discussion (500 words), methods, references, and supplementary information.
We encourage the teams to upload raw data and experiment records to data repositories.
The supplementary information should include supplementary figures, sequence information (if not deposited at sequence repositories), or any other necessary information to support the conclusion.
Wikis for iDEC serve two functions.
First, it ensures that all information pertaining to the research conducted, including but not limited to, experiment logs and responsible research forms, are properly documented and remain accessible.
We encourage the teams to upload raw data and experiment records to public data repositories.
Second, it communicates the project's intention, significance and outcome to both the scientific community and the lay public. Therefore, the contents of wiki pages should not be merely a web adaptation of the academic report. That is, it does not need to contain all the results, descriptions, or discussions. Instead, it should be as accessible, clear, and enjoyable as possible. Interactive multimedia, such as animations, short videos and cartoons, are much encouraged.
The wiki space will be available starting in June 2022.
The poster should be in the format of an academic poster.
The poster must include the iDEC Logo, a project title, a QR code that links to the team wiki, a list of authors, the participating institute or organization, and any other necessary team information.
Other than the above, teams are free to determine the layouts of their posters.
Every team should prepare a presentation that will be completed within 20 mins, and then attend a Q&A session that will last no more than 10 mins.
There will be additional requirements associated with the Challenge Track.
The advisory groups who set the challenges can ask teams to perform directed evolution on specified genetic elements.
The advisory groups may also provide standard protocols and control samples through which the teams should verify their results with.
In some scenarios, a particular circuit design may be assigned for result verification.
Experiment records are integral to the competition. Teams will be required to document experiment details and define the contributions of team members at every stage. An online experiment log will be judged and will be credited to the final score when qualifying for the general awards. The experiment record should be uploaded to the team wiki space.
All experiment records should log the dates and the researchers who execute the experiments, and include the details on the protocols used as well as the result generated. There should also be a table stating which experiment contributed to which Report figure.
Data used to generate the experiment results should be deposited to research data repositories. Example repositories include Open Science Foundation and Zendo. Teams should also select the correct repositories according to the type of data. For instance, DNA sequences should be submitted to repositories like the NCBI Nucleotide database instead of general repositories. The deposit of data must comply with GDPR requirements.
Computing codes should be submitted to source-code repositories.
Teams should generate dois for citing data and codes. iDEC will show these dois alongside the display items stated above.
iDEC requires participating teams to declare that all data, computing codes, and biological materials are available upon request.
If the methods, raw data, code, and sequence information disclosed concern GDPR, they should be addressed appropriately in the Data Accessibility Statements.