Difference between revisions of "Judging/Apply"

Line 312: Line 312:
  
 
<p class="question">3.1 If not, please indicate which days/times you are available to attend.</p>
 
<p class="question">3.1 If not, please indicate which days/times you are available to attend.</p>
 +
 +
<div style="width:50%;float:left;">
 
<table>
 
<table>
 +
<tr> <th> Day </th> <th>Morning </th> <th> Evening </th> </tr>
 +
 
<tr>
 
<tr>
−
<th>Thu Nov 9, Evening</th>
+
<th>Thursday <br> November 09</th>
−
<th>Fri Nov 10, Morning</th>
+
<td></td>
−
<th>Fri Nov 10, Evening</th>
+
−
<th>Sat Nov 11, Morning</th>
+
−
<th>Sat Nov 11, Evening</th>
+
−
<th>Sun Nov 12, Morning</th>
+
−
<th>Sun Nov 12, Evening</th>
+
−
<th>Mon Nov 13, Morning</th>
+
−
</tr>
+
−
<tr>
+
 
<td><label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br />
 
<td><label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="no"> No</label>
 
</td>
 
</td>
 +
 +
</tr>
 +
 +
<tr>
 +
<th>Friday <br> November 10</th>
 
<td><label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br />
 
<td><label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="no"> No</label>
Line 333: Line 334:
 
<label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="no"> No</label>
 
</td>
 
</td>
 +
 +
</tr>
 +
 +
 +
 +
<tr>
 +
 +
<th>Saturday <br> November 11</th>
 +
 
<td><label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br />
 
<td><label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="no"> No</label>
Line 339: Line 349:
 
<label><input type="radio" name="Availability Sat Oct 29, Evening" data-form-field="available_sat_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Sat Oct 29, Evening" data-form-field="available_sat_eve" value="no"> No</label>
 
</td>
 
</td>
 +
 +
</tr>
 +
 +
<tr>
 +
<th>Sunday <br> November 12</th>
 
<td><label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br />
 
<td><label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="no"> No</label>
Line 345: Line 360:
 
<label><input type="radio" name="Availability Sun Oct 30, Evening" data-form-field="available_sun_eve" value="no"> No</label>
 
<label><input type="radio" name="Availability Sun Oct 30, Evening" data-form-field="available_sun_eve" value="no"> No</label>
 
</td>
 
</td>
 +
</tr>
 +
 +
<tr>
 +
<th>Monday <br> November 13</th>
 
<td><label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br />
 
<td><label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br />
 
<label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="no"> No</label>
 
<label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="no"> No</label>
 
</td>
 
</td>
 +
<td></td>
 
</tr>
 
</tr>
 +
 
</table>
 
</table>
  
−
<div class="highlightBoxB">
+
 
 +
</div>
 +
 
 +
 
 +
<div style="width:50%;float:left;">
 +
 
 
<h3> Note</h3>
 
<h3> Note</h3>
 
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2017 <a href="https://2017.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 27-31). <b>iGEM currently cannot provide travel funding</b> for judges to attend.</p>
 
<p>If you are selected as a judge, you <b>MUST</b> attend the iGEM 2017 <a href="https://2017.igem.org/Giant_Jamboree">Giant Jamboree</a> in Boston (October 27-31). <b>iGEM currently cannot provide travel funding</b> for judges to attend.</p>
Line 357: Line 383:
 
<p>If you are not on the roster of a 2017 iGEM team, <b>your Jamboree attendance fee will be waived</b>.</p>
 
<p>If you are not on the roster of a 2017 iGEM team, <b>your Jamboree attendance fee will be waived</b>.</p>
 
</div>
 
</div>
−
 
+
</div>
 
</fieldset>
 
</fieldset>
  

Revision as of 18:07, 24 March 2017

MENU
Loading...


You have JavaScript disabled.

This page requires JavaScript in order to function correctly. Please enable JavaScript in your browser, then try again.

NOTE: This page is under development

Apply to be a Judge

Judging in iGEM is a lot of fun, but it does require a strong commitment. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree in September, we would love to have you on board!

We need judges who understand iGEM, and judges who are willing to learn about iGEM. We will provide educational resources to help judges learn how to evaluate teams, and we will help you get up to speed if you are selected.

Lastly, I'm afraid that if you are a student on a 2017 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!

Please email kim [AT] igem [DOT] org if you have questions!

We're looking for:

  • iGEM instructors and advisors
  • People who have judged iGEM in the past
  • People in the synthetic biology industry
  • Synthetic biology researchers who are new to iGEM
  • iGEM alumni who want to stay involved

If you have colleagues who you think should apply, please feel free to direct them to this form.

NEW: Instructor judges will receive a 50% discount on their Jamboree attendance fee!

This form has been submitted.

You can unsubmit the form if you wish to make further edits.

Click here to dismiss this message

-- Please choose a team

Judge Application Form

1 General Information

Full name: -

Username: -)

1. Email

2. Age

3. Gender

4. Institution

5. Institution type

6. Position

7. Region Where you currently live/work :

8. Number of years of iGEM experience as a:

Judge:

Instructor / PI:

Advisor:

Student:

Volunteer:

2 Jamboree Information

Please complete this section as well as you can. You will be asked to check or update this information prior to the Jamboree.

1. Sweatshirt Size:

2. Dietary restrictions If you have other dietary restrictions, please contact iGEM HQ

3. Are you available to attend the entire Giant Jamboree (November 9 - 11 2017, in Boston)?

3.1 If not, please indicate which days/times you are available to attend.

Day Morning Evening
Thursday
November 09
Friday
November 10

Saturday
November 11

Sunday
November 12

Monday
November 13

Note

If you are selected as a judge, you MUST attend the iGEM 2017 Giant Jamboree in Boston (October 27-31). iGEM currently cannot provide travel funding for judges to attend.

If you are registered as a Primary PI, Secondary PI, Instructor, or Advisor for a 2017 iGEM team, you will receive a 50% discount on your Giant Jamboree registration fee if you are selected as a judge. As both an instructor and a judge, your primary role must be as an instructor. We ensure that your judging assignments do not conflict with your own team's presentation.

If you are not on the roster of a 2017 iGEM team, your Jamboree attendance fee will be waived.

3 Conflicts of Interest

There are many possible reasons why you might be unable to judge some teams impartially. For example:

  • If you are a PI or instructor for the team
  • If the team comes from a school that you attended, or a school where you work
  • If you mentored or advised the team informally

These situations could lead to a conflict of interest. iGEM takes conflicts of interests very seriously. Judges are not permitted to judge teams for which they have a conflict of interest. If you are a PI or instructor, your first responsibility is to your team, and we will schedule your judging assignment so that you are able to attend your team's presentation.

Please tell us about your conflicts of interest here.

Team Affiliations:
Please select any teams you are officially affiliated with (i.e. you are listed on the team roster as a PI, Instructor, or Advisor).

Conflicts of Interest:
Please select any teams for which you have a conflict of interest for another reason. (For example, a team that you mentored informally, or a team from the university where you were an undergrad student.)

To select multiple teams, use Ctrl-click or Cmd-click.

Don't recognize a team name? Look it up in the Team List.

If you have any other conflicts of interest that are not indicated above, please describe them:

4 Motivation

Please answer these questions in detail, especially if this is your first IGEM judging application.

Did you apply to judge last year? View your answers from last year.

Why do you want to be a judge in iGEM?

What professional experience do you have that's relevant to iGEM (e.g., synthetic biology, hardware, software, human practices)?

Have you judged student competitions other than iGEM before? If so, which ones? (e.g. FIRST, BIOMOD, Science Olympiad)

What features of an iGEM team and their project make them worthy of recognition?

(New judges may want to familiarize themselves with the 2015 Judging Handbook Part 1. The 2017 Judging Handbook will be available later this year.)

5 Track Preferences

iGEM teams compete in several "tracks", based on the topics of their projects. Please see the Track page for more information on each track.

When we assign judges to teams, we will try to assign you your first preferences wherever possible. However, we can't anticipate how many teams will be in each track, so it may not always be possible to assign you your first choice. Therefore, you can indicate how you feel about each track. The more first choices you select, the more likely it is that you will be assigned teams in those tracks. If you are unable to evaluate teams in some track areas (software or measurement, for example), please put "Avoid" for those tracks.

Please indicate how highly you prefer each track. You may select multiple first, second, and third preferences.

Track First Second Third Neutral Avoid
Art and Design
Diagnostics
Energy
Environment
Food and Nutrition
Foundational Advance
Hardware
High School
Information Processing
Manufacturing
Measurement
New Application
Software
Therapeutics

Thank you!

Thank you for filling out this form. We look forward to picking a strong judging team for 2017!

Finished?

Need to make changes?