UIL Computer Science District Hands On Contest Pilot District Meet Director's Guide

Transcription

1 UIL Cmputer Science District Hands On Cntest Pilt District Meet Directr's Guide District and Cmputer Science Cntest Directrs The cntest directrs are designated UIL fficials, and as such have the authrity t make decisins regarding the management f the cntest t ensure that it is cnducted accrding t UIL rules. The Cntest Directr als has the authrity t settle any disputes that might arise in accrdance with UIL rules If a situatin shuld cme up that yu are nt sure hw t reslve, r if yu have any questins regarding rules, prcedures, etc., please feel free t cntact Mike Sctt at scttm@cs.utexas.edu r (512) if a mre immediate respnse is required Intrductin: Thank yu fr agreeing t participate in the pilt f the UIL Cmputer Science Handsn prgramming cmpetitin at the district level. The pilt is being cnducted t determine if it feasible t include a hands n prtin as an fficial part f the district level cntest at sme future date. The pilt als allws districts t gain experience in running a hands n prgramming cntest. As a pilt, the result f the hands n cmpetitin has n effect n which individuals and team advance t the reginal cmpetitin. Nr des it affect the district sweepstakes cmpetitin. At the district level, thse results are based slely n the results f the written test. If yu have any questins abut these instructins please cntact Mike Sctt at scttm@cs.utexas.edu r (512) The rest f this guide cnsists f tw parts. The first details the District Meet Directr duties. The secnd details duties f the Cmputer Science Cntest Directr, wh is appinted by the District Meet Directr. Included with the duties f the Cmputer Science Cntest Directr are the instructins fr and the duties f ther persnnel needed t run the Cmputer Science Hands-n cntest. Fundamental Cntest Rules Teams: In a Hands-n prgramming cntest, teams cnsist f three members. If a team has fur members the cach decides which three members participate in the Hands-n cmpetitin. There must be at least 3 members n the team t cmpete in the Hands-n cmpetitin. Hardware: Each team has ne cmputer cnsisting f a single mnitr, keybard, and system. If laptps with external keybards are used, the laptp keybard must be cvered in sme way. Teams may use ne printer, but a printer is nt required. Sftware: The cmputer may be laded with nrmal sftware (such as wrd prcessrs, etc.), the Java SDK, a develpment envirnment (such as JCreatr, Eclipse, NetBeans, r whatever IDE the team chses), Allwed resurces: The dcumentatin fr the Java API's, and the API's themselves may be installed n a team's cmputer. Teams may als have tw textbks r references that are reasnably free f written ntes. Nn-allwed resurces: It is imprtant that the cmputer system be free f any cde written by the cntestants prir t the cntest such as slutins t practice prblems, slutins t prir cntest prblems, r prgrams written in class. A bk n a CD r n a team's hard drive is nt an acceptable reference and shuld be remved frm the cmputer system. District Cmputer Science Pilt Hands-n Cntest Instructins Page 1

2 District Meet Directr Duties (As early as pssible befre the cntest date) Appint a Cmputer Science Cntest Directr (a Cmputer Science cach is gd) The Cmputer Science cntest directr in charge f the cntest and has final say n issues invlving judging slutins. Meet with the CS Cntest Directr (CSCD) early. Schedule the cntest time slt. (Check cnflict pattern fr a 2 hur slt fr hands n). Assign a rm fr the cntest. Each team shuld have at least 5 feet f table space, 3 chairs, and a pwer surce. There shuld be a clck visible fr all cntestants. The judging area shuld be separated frm the cntestants' area but clse by t allw a timely flw f slutins and results. Determine where the cntest results and Queries will be psted. Determine if the hst schl will prvide a cmputer system fr each team r require each team t prvide their wn system (EXACTLY ONE cmputer system per schl - each team usually prvides their wn). Discuss wh will make team packets and when (the CSCD is recmmended). Determine what cmputer system will be used fr the judging rm (1 r 2 systems fr 8 teams) and wh will install Java 6.0. Determine what judging platfrm yu will use: Cmpile and run the prgram and manually check the results against the Judges packet. Use the prgram prvided by the UIL. Use PC 2. As sn as Cntest Materials arrive, give the Hands-n Pilt Cntest Materials t the CSCD. District Meet Directr Duties (On the cntest date befre the cmpetitin) Have the fllwing ready fr the cntest directr: signs with team number and schl name. scratch paper and pencils. timer r stp watch. signs fr judging, archive and screkeeper statins. name tags fr cntest persnnel. Recrd results. District Cmputer Science Pilt Hands-n Cntest Instructins Page 2

3 UIL Cmputer Science District Hands On Cntest - Pilt Cmputer Science Cntest Directr's Guide The fllwing is a chrnlgical list f duties fr the Cmputer Science Cntest Directr. CS Cntest Directr (CSCD) Duties (befre the cntest day) Appint additinal persnnel t assist in running the district Hands-n cntest. Fr a 6-8 team district the CSCD will need: 1 r 2 assistant judges - The CSCD alng with the additinal judges will judge slutins submitted by the cntestants. Caches frm district schls are encuraged t act as judges. Appint a screkeeper and archivist - These may be separate r cmbined psitins r the CSCD and the assistant may d this. The archivist backs up slutins submitted by teams prir t them being judged The screkeeper recrds results f cntestant's slutins using the prvided scring prgram Appint 1 rm mnitr (Caches r willing teachers are gd rm mnitrs) The rm mnitr will assist with checking teams in and then seat them. The rm mnitr will circulate in the rm t see that all teams are adhering t cntest rules bth befre and during the cntest. The rm mnitr will supervise the runners when they are in the cntest area. Appint 1 r 2 runners t wrk under the supervisin f the rm mnitr (this may be the 4th nn-prgramming team member frm district teams) The runners pick up slutins frm the cntestants and take them t the judging area t be archived, judged, and scred The runners als return judged submissins t the teams Create Precntest team packets. Fr each team yu will need the fllwing. An envelpe (10 x 13) clearly marked "Precntest Materials" that cntains: One cpy f the dry run prblem (dry run is prblem number 0). 3 manila run envelpes (9x12). 7 run sheets with team number and prblem number (Dry Run and 1-6) filled in. 4 Query sheets. (clred paper). One Verificatin sheet (a different clred paper). One disk with the student data fr the dry run prblem. (This is n the Cntest CD the cntest directr must make ne cpy per team). Label the Precntest team packet envelpe with the team's name and number. Create Official Cntest team packets. Fr each team yu will need: An envelpe (10 x 13) clearly marked "Official Cntest Materials DO NOT OPEN UNTIL TOLD TO BY THE CONTEST DIRECTOR. In each envelpe, put: One cpy f the prblem set 6 sheets f clean paper fr teams t use fr scratch paper. A disk cntaining the sample data files as stated in the prblems. (This is n the Cntest CD the cntest directr must make ne cpy per team). Create Judges packet. fr the grading rm:. One envelpe (10 x 13) clearly marked Judging Dcuments DO NOT OPEN UNTIL TOLD TO BY THE CONTEST DIRECTOR. Keep secure until the cntest begins. In this envelpe, put: One cpy f the prblem set fr each judge. One cpy f the judges utput fr each judge t use fr grading. One envelpe with 7 cpies f the Acceptance slips fr each team. (if yu have 5 teams, yu need 35) and pens, sticky ntes, etc. needed fr grading. District Cmputer Science Pilt Hands-n Cntest Instructins Page 3

4 Create pst-cntest team packets. Fr each team yu will need: A disk marked Pst-cntest Materials (Clearly label the dist as Pst-cntest Materials DO NOT OPEN UNTIL AFTER THE CONTEST ). On each disk, put the fllwing files: the prblem set. the sample data files. the judges data files. See that the judging sftware is installed n the judging statins (Java JDK 6.0 required) It is strngly recmmended yu install and verify the judging envirnment wrks several days prir t the day f the cntest. This will allw yu enugh time t reslve any prblems yu may encunter due t yur schl's cmputer systems and / r security measures. Install the scring prgram fr the Screkeeper. Install the archiving sftware fr the Archivist. Install the judge's data n the judging statins. If yu use the prvided judging envirnment, the judging data shuld be installed autmatically. Test the judging envirnment by running the slutin t the dry run. This will test the judging sftware. A slutin t the dry run is prvided n the judging disk r can de dwnladed frm the UIL web site at Test the Screkeeper s sftware, and the Archivist s sftware. If yu wish t use the prvided scring prgram install that sftware n the cmputer that will be used by the archivist / screkeeper. Instructins fr the scring prgram are n a separate sheet. CS Cntest Directr Duties (cntest day) Obtain signs frm the Meet Cntest Directr and pst them t identify each statin and team area. Ensure judging, archivist and screkeeper statins are set up. Ensure Precntest Material packets are ready fr distributin as students check in. Ensure Official Cntest Materials packets are ready fr distributin at the beginning f the cntest. Train judges, archivist, and recrder n the sftware and their duties. Train runners n their duties. Ensure Judges packets are ready fr distributin after the cntest begins. Ensure Pstcntest packets are ready fr distributin after the cntest ends. Give name tags t cntest persnnel. CS Cntest Directr Duties (60 minutes prir t the start f cntest) Check-in: CSCD r an assistant will check teams in and cnfirm the members' names. Team Members: In a Hands-n prgramming cntest, teams cnsist f three members. If a team has fur members the cach decides which three members participate in the Hands-n cmpetitin. There must be at least 3 members n the team t cmpete in the Hands-n cmpetitin. Precntest Packets: Give the teams their Precntest Materials packet as they check-in. Dry run: At check-in, explain t each team the prcess fr submitting their dry run slutins. The dry run prblem is a simple prblem t insure understanding f the cntest peratins and t be sure the cntestants, the runners, archivist, judge and recrder are all wrking tgether.. The dry run prblem is in the Team Precntest Materials packet and is als psted n the UIL Cmputer Science site. Teams shuld have a wrking versin f the slutin prir t cming t the cntest. If nt, they shuld write the slutin as sn as they have their system set up. After the teams have their cmputer system set up, they are t place the surce cde fr their slutin t n a flppy disk and place the disk and their cmpleted dry run run sheet int the dry run run envelpe and give it t a runner. The runner will take the run envelpe t the archivist, wh will archive it and give it t the judge t be judged. The judge will cmpile and run the cntestant's slutin using the judging data. Expected results are cmpared t the actual results frm the cntestant's slutin. District Cmputer Science Pilt Hands-n Cntest Instructins Page 4

5 The judges will then recrd n the run sheet if slutin is accepted r rejected and cmplete an Acceptance sheet if the slutin is crrect. Then place the disk, run sheet, and Acceptance sheet, if earned, int the run envelpe. Give the run envelpe t the screkeeper. The screkeeper will recrd the results and give the run envelpe t the runner wh will return it t the cntestants. Teams may cntinue t submit slutins t the dry run prblem until they get it crrect r until the time fr submitting the dry run is ver. Cntestants may cnfer with their cach in the cntest rm during the dry run prcess. Mnitring: The CSCD r an assistant will mnitr the cntest rm as teams set up their cmputer systems and cmplete their dry run. CS Cntest Directr Duties (30 minutes prir t the start f cntest) Ensure teams have a single cmputer system. Each team is allwed ne cmputer cnsisting f a single mnitr, keybard, and system. If laptps with external keybards are used, the laptp keybard must be cvered in sme way. Teams may use ne printer, but a printer is nt required. The team may have a back-up cmputer system prvided it is stred in a near-by area (e.g. frnt f rm). Ensure all previusly written prgrams have been remved frm the cntestants' cmputer systems. Allwed Sftware: The cmputer may be laded with nrmal sftware (such as wrd prcessrs, etc.), the Java SDK, a develpment envirnment (such as JCreatr, Eclipse, NetBeans, r whatever IDE the team chses), Allwed resurces: The dcumentatin fr the Java API's, and the API's themselves may be installed n a team's cmputer. Teams may als have tw textbks r references that are reasnably free f written ntes. Nn-allwed resurces: It is imprtant that the cmputer system be free f any cde written by the cntestants prir t the cntest such as slutins t practice prblems, slutins t prir cntest prblems, r prgrams written in class. A bk n a CD r n a team's hard drive is nt an acceptable reference and shuld be remved frm the cmputer system. CS Cntest Directr Duties (15 minutes prir t the start f cntest) Assemble cntestants and caches fr instructins. G ver cntest rules n the frnt cver f the cntest prblems and g ver any pertinent prcedures frm the Cmputer Science sectin f the UIL C & CR. There are 6 prblems n the test. Explain the scring. Each crrect slutin will scre 60 pints. Each incrrect slutin will scre -5 pints nly if a crrect slutin is eventually submitted. The cntest will last fr 60 minutes. Teams may wrk n the prblems in any rder. G ver the cntest mechanics. When they have a slutin: Cmplete a run sheet with their team number and prblem number n it Save the surce cde (,java file) t a disk Label the disk with the team number and prblem number. Place bth the run sheet and the disk in the run envelpe fr that prblem. Hld the envelpe HIGH in the air fr a runner t cllect. The runner will return the prblem as sn as it is judged and recrded. Query frm - The Query frm is used t pass infrmatin between a team and the judges. The Query frm is filled ut by a team and given t a runner t take t the cntest directr. The purpse f the frm is t reslve ambiguities r misstatements in a prblem. They are nt t be used t give teams an advantage, extra infrmatin, r hints n hw t slve a prblem. The cntest directr must decide n the apprpriate respnse in cnsultatin with the ther judges. It may well be that the apprpriate respnse is fr the team t read the prblem statement mre carefully and lk at the given examples. If a clarificatin is in fact required District Cmputer Science Pilt Hands-n Cntest Instructins Page 5

6 due t ambiguity r a prblem misstatement, all teams shuld be made aware f the resulutin. The judging data will include test cases nt shwn n the prblem statement sheet. When the 60 minutes is ver, yu will say "Stp". At this time, yu will nly accept slutins that are already in a run envelpe and the run envelpe is in the air. When the cntest is ver, teams will assemble their Acceptance sheets and cmplete their Verificatin sheet. Each team will then give their Verificatin sheet t a runner wh will take it t the judging rm. Students may nt disassemble their cmputers until all judging is cmplete and all prtests have been reslved. Once a team disassembles their cmputer system, they frfeit their right t prtest. Instruct the teams t delete their dry run slutin frm their cmputers. Answer any final questins. Ask the caches that are nt helping t run the cntest t leave r be rm mnitrs. Distribute Official Cntest Materials. Instruct students nt t pen them until they are tld t "Start". CS Cntest Directr Duties (Cnducting the Cntest) Pass ut the Official Cntest packets. Set the timer t 60 minutes. Annunce "Start" and start the stpwatch. This is the fficial start f the cntest and cntestants may pen their cntest envelpe and have ne hur t submit slutins. When a team has a pssible slutin t a prblem, they place the surce cde n a disk, place the disk in a run envelpe with a run slip and give it t runner. The runner takes envelpe t archivist. Archivist Duties: The archivist: Recrds the team number and prblem number fr the submissin. Recrds the time the prblem was submitted. Backs up the slutin submitted. Gives the run envelpe t a judge. Judges Duties: Submissins shuld be maintained in a first in first ut rder. As judges becme available they shuld judge the ldest submissin. If using the judging envirnment prvided, fllw the instructins n the "Hw t Use the Judging Envirnment" instructin sheet. If nt using the judging envirnment: Create a flder fr each team. Cpy the file t the team's flder. Remve the disk frm yur flppy drive. Cmpile and run the prgram submitted. In either case, use these judging guidelines: White space differences at the end f lines r after the last line f utput are never significant and shuld never cause a prblem t be judged as incrrect If the differences d nt seem material t the prblem being slved, err n the side f accepting the slutin. Fr instance, if a prblem is abut perfrming a cmplex calculatin, be flexible with utput frmatting. On the ther hand, if the prblem is all abut frmatting, then be a stickler. Abve all, be cnsistent with yur judging. If a submissin is crrect, mark accept n the run sheet and cmplete an Acceptance sheet. If a submissin is incrrect, mark reject n the run sheet and mark ne f the cmments n the run sheet. At the state meet we generally nly use a small number f the available cmments: "Des Nt Cmpile" is used fr submissin that suffer cmpile errrs. "Run-time Errr" is used fr submissins that suffer a runtime errr r exceptin. "Failed Judges' Test Data" is used fr any cases where the submissin cmpiles and runs but whse utput des nt match the expected answers. District Cmputer Science Pilt Hands-n Cntest Instructins Page 6

7 "Time-Limit Exceeded" is used when a submissin results in an infinite lp r the prgram des nt end. Nne f the prblems in the district prblem set require a large amunt f cmputatin. A guideline fr when t halt a team's prgram is 2 minutes. After judging the slutin and marking the run sheet, the submissin disk, run sheet, and if earned, the Acceptance sheet g back int the run envelpe which is given t the Screkeeper. Screkeeper Duties: The screkeeper recrds successes and failures f the cntestant's slutin using the prvided scring prgram and then returns the run envelpe t the runner. Crrect slutins are awarded 60 pints less any penalty pints. Incrrect slutins are penalized 5 pints fr EACH time an incrrect slutin is submitted ONLY WHEN the crrect slutin is finally submitted. Fr example: Team A submits tw incrrect slutins fr prblem 3 and never submits a crrect slutin. Team A will receive n pints and will be accessed n penalty pints fr prblem 3. If Team B submits tw incrrect slutins fr prblem 4 and then submits a crrect slutin, Team B will receive 50 pints fr prblem 4.This is 60 pints fr submitting the crrect slutin minus 5 pints fr EACH incrrect submissin (a ttal f 10 penalty pints). The runner returns the run envelpe t the team. If a team's slutin is judged incrrect, the team may rewrk their slutin and resubmit their new slutin. Teams may make as many submissins fr a given prblem as they wish. All teams shuld be ntified when 15 minutes is remaining inf the cntest. Nte: Caches may fill any f these psitins and ne persn may serve in mre than ne f these psitins. CS Cntest Directr Duties (Ending the Cntest) At the ne hur mark teams shall be tld t stp. Accept any slutins in a run envelpe that was in the air when the signal t stp was given. N mre submissins are t be accepted. Tell students t leave their cmputers set up until judging is cmplete. Failure t d this will cause a team t frfeit their right f appeal. Have teams t cmplete their Verificatin frms and turn them in t the rm mnitr. Cmplete judging. Cmplete scring. Teams are ranked based n pints earned. The maximum pssible scre is 360. Ties are nt brken. Please remember, the results f the Hands-n cntest d nt affect which individuals r which team advance t the reginal cmpetitin and it des nt affect the district sweepstakes cmpetitin. At the district level thse are based slely n the results f the written test. Verify grading with cntestant's Verificatin frms and reslve any discrepancies. Cllect all fficial cntest materials. These may be returned t teams when ther fficial district materials are returned. Assemble caches and cntestants again and annunce results. District Cmputer Science Pilt Hands-n Cntest Instructins Page 7

8 Other Issues: Reslving Cnflicts: As cntest directrs, yu are designated UIL fficials. As such, yu have the authrity t make decisins regarding the management f yur cntest t ensure that it is cnducted accrding t UIL rules. Yu als have the authrity t settle any disputes that might arise in accrdance with UIL rules, thugh we certainly hpe there wn't be any f thse. Hwever, if a situatin shuld cme up that yu are nt sure hw t reslve, r if yu have any questins regarding rules, prcedures, etc., please feel free t cntact Mike Sctt at scttm@cs.utexas.edu r (512) if a mre immediate respnse is required. Acceptable Media: A few wrds n what media t use fr submissin f material: The suggested media is flppy disks but alternatives t flppy disks fr hands-n prgramming may be used. Cntest rules d nt require that cntestants use flppy disks, but we cntinue t recmmend a flppy disk as the best media fr the cntest -- cpy times are faster than fr burning CD's and they are mre readily re-usable, and they are still much cheaper than flash drives. We d realize that many new cmputers d nt include flppy drives. We recmmend that teams bring an external flppy drive, but yu may have sme teams shw up wh d nt have ne and want t use ther media. There is nthing in the rules that wuld prhibit the use f ther types f media, but they need t be aware f the ptential disadvantages. Fr example, yu may have prepared yur sample data fr distributin t cntestants n flppy disk, and it may nt be feasible fr yu t make cpies in ther frmats. In that case, cntestants withut flppy drives wuld need t create their wn sample input data using what's printed in the prblem set. (What they get n disk is identical t the sample data printed in the prblem set.) Fr flash drives, they need t understand that they're nt ging t get their drives back immediately, s if they nly have ne r tw flash drives it may make it difficult fr them t submit multiple slutins. Judging shuld always be "first in, first ut" regardless f media type, s a team with a flash drive shuld nt receive pririty ver a team using flppies. In terms f judging with different types f media, the nly cnsideratin is being sure that yu're reading frm the crrect drive. The judging script is set up t read frm a single drive, nrmally the A drive. If there is a mix f submissin media ne slutin is t change the lcatin fr the judging prgram t a directry n the judging cmputer and cpy all submissins t that lcal directry. Feedback: Finally, we wuld like yur feedback. Please cmplete the UIL Cmputer Science District Hands-n Pilt Evaluatin Frm. Yu may mail, , r fax yur cmments. If yu want t mail yur cmments please mail the cmpleted frm t: Mike Sctt Department f Cmputer Sciences Taylr Hall University Statin C0500 Austin, TX Or, fax it t Mike Sctt at (512) Or, scttm@cs.utexas.edu (there is an electrnic versin f the frm n the materials CD. Thank yu fr yur willingness t participate in the pilt f the UIL Cmputer Science hands n prgramming cmpetitin at the district level and all f yur hard wrk. District Cmputer Science Pilt Hands-n Cntest Instructins Page 8