Computer Science Programming Contest

Transcription

1 Team Member Requirements Cmputer Science Prgramming Cntest By Charltte Scrggs Frmer Cach and UIL CS C-Directr A prgramming team must have exactly three members If a cmputer science team has fur members, the cach decides which three members participate in prgramming Hardware Requirements Each team has ne cmputer cnsisting f a single mnitr, keybard, and CPU Teams may use ne printer, but a printer is nt required Flash drives are the preferred media t send slutins t the judges, but sme cntest sites may use a netwrked system Sftware Requirements The cmputer may be laded with nrmal sftware (such as wrd prcessrs, etc.) Java SDK (7.0( r higher recmmended) a develpment envirnment (such as JCreatr, Eclipse, NetBeans) Permissible ible Items n the cmputer - the dcumentatin fr the Java API's, and the API's themselves tw PUBLISHED printed textbks r reference bks that are reasnably free f handwritten ntes. Prhibited Items 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 are nt allwed A bk n a CD is nt an acceptable reference and shuld be remved frm the cmputer system. Cntest Basics The Prgramming cntest c will cnsist f 12 prgramming prblems f varying levels f difficulty. Teams have tw hurs t cmplete as many slutins as they can. Teams determine the rder f submissin f their slutins.

2 Meet Directr Duties CS Meet Persnnel Appint a cntest directr (a cach is gd) This individual is in charge f the cntest and has final say n issues invlving judging slutins Check cnflict matrix fr a 2 hur slt fr the prgramming cntest. Assign a rm fr the cntest Requirements: Minimum m f 5 feet f table space, 3 chairs, and a pwer surce fr each team. A clck visible fr all cntestants Assign a rm fr the Judging area Separate frm, but near, the cntestants' area t allw a timely flw f slutins and results Determine where the t cntest results will be psted Meet with the CS Cntest Directr (next slides) Meeting between the Meet Directr and the CS Cntest Directr Meeting shuld be early (by mid-january) Determine wh will prvide cmputers hst schl prvide cmputers fr each team r each team t prvide their wn system Appint 1 r 2 additinal judges (caches) wh will als act as Assistants t the Cntest Directr Determine what cmputer system will be used fr the judging rm (1 r 2 systems fr 8 teams) Wh (and hw) will install Java, ther cntest/judging sftware if applicable 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 Meet Directr Duties On the cntest date, have the fllwing ready fr the cntest directr: All materials prvided by the UIL Runners assigned (1 r 2 nn-cmpetitrs) Signs fr each team with team number and schl name Judging, Archive and Screkeeper statins Scratch ch paper and pencils Timer r stpwatch

3 CS Cntest Directr Duties Appint an archivist and a screkeeper These may be separate r cmbined psitins The Cntest Directr and/r the judges may d this The archivist backs up slutins submitted by teams PRIOR t being judged The screkeeper recrds results f cntestant's slutins using the prvided scring prgram Train the runners prir t the cntest start 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 Appint 1 r 2 rm mnitrs check teams in seat them Bth befre and during the cntest, circulate in the rm t see that all teams are adhering t cntest rules Caches r willing w teachers are gd rm mnitrs UIL Prvided Materials Dcuments used t create precntest p team packets fr each team: A team number, 1 t n. "Precntest Materials" envelpe cntaining: a cpy f the dry run prblem (dry run is prblem number 0) 13 Run Sheets filled in with the team number and prblem number 13 Run Envelpes. 3-5 Clarificatin Frms Team Verificatin Frm Sealed Packet f Prblem Sets (1 cpy fr each team; use the remainder fr judging) Judging packet: Sealed envelpe cntaining: Printuts f judge data Judging CD, including UIL judging sftware Judge data Cntestant sample data (make ne disk cpy fr each team) Sample slutins Pst- cntest team packets fr each team: A disk marked Pst- cntest Materials labeled as Pst- cntest Materials DO NOT OPEN UNTIL AFTER THE CONTEST cntaining: the prblem set the sample data files the judges data files Nte: Distribute n UIL Embarg Date

4 CS Cntest Directr Duties Prir t the cntest day See that the judging sftware is installed n the judging statins (Java JDK 7.0 required) Install the scring prgram fr the Screkeeper Install the archiving sftware fr the Archivist run the slutin t the Dry Run t test the judging sftware, the Screkeeper s sftware, and the Archivist s sftwares Day f the cntest: Put up signs identifying each statin and team area Ensure judging, archivist and screkeeper statins are set up Ensure Precntest Material envelpes and Official Cntest Materials envelpes are ready fr distributin Train judges, archivist, and screkeeper n the sftware and their duties Train runners n their duties As teams arrive r 60 minutes prir t the start f cntest: The Dry Run Yu r an assistant will check in teams and cnfirm the members' names give teams their Precntest MaterialsM explain t each team the prcess fr submitting their dry run slutins allw teams t set up their cmputer system allw teams t cmplete the dry run and submit their slutins The dry run is a simple prblem t: insure teams and fficials understand the cntest peratins. make sure all aspects f the cntest are wrking crrectly. Teams submit the surce cde fr the dry run Runners cllect it Archivist archive it Judges judge it Screkeeper recrd the results Runners return the results t the teams 30 minutes prir t the start f cntest Check fr the fllwing All previusly written prgrams remved frm the cntestants' cmputer system Teams have a single cmputer system Teams have n mre than 2 apprved references Extra equipment, resurces, backpacks, bxes, etc. are remved frm the cntest area (mved t frnt f rm) 15 minutes prir t the start f cntest Assemble cntestants and caches fr instructins. G ver cntest rules and prcedures and answer any questins Ask the t caches that are nt helping t run the cntest t leave Distribute Official Cntest Materials

5 CS Cntest Directr Duties Cnducting the Cntest Annunce Start. Cntestants may pen their cntest envelpe and have tw hurs t submit slutins When a team slves 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 Runner takes envelpe t archivist t archive Archivist gives envelpe t judge Judge runs the surce cde and cmpletes the Run Sheet and gives the envelpe t the screkeeper The screkeeper recrds whether it was crrect r nt, awards the apprpriate pints, and returns the envelpe t the runner Runner returns envelpe t the team Cntest Prcedures The judging data will include i test cases nt shwn n the prblem statement sheet. If the slutin is crrect, it is accepted and recrded as being crrect n the run sheet If it fails, a reasn fr rejectin is marked n the run sheet In either case, the slutin disk and the run r sheet are returned t cntestants Ending the Cntest At the tw hur mark teams shall be tld t stp and n mre submissins are accepted A team may turn in a slutin at the stp signal if it is in a run envelpe and in the air Cmplete judging Cmplete scring Cllect team Verificatin frms, cmpare with yur scring, and reslve any discrepancies Cllect all fficial cntest materials. These cntest materials and the Pst- cntest team packets may be returned t teams when ther fficial cntest materials are returned Annunce results CS Cntest Directr 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 Shyamal Mitra at mitra@cs.utexas.edu r (512) if a mre immediate respnse is required

6 N cntent n this page.

7 Caching Tips By Charltte Scrggs Frmer Cach and UIL CS C-Directr UIL Site Resurces science Rules and General Infrmatin Intrductin t the Cmputer Science Cntest (includes general guidelines fr prgramming) Scring Prcedures UIL CS Current Tpics List Useful Links IDEs References Prgramming Practice Prblems Third Party Materials Other Cntests Prgramming Prblems - Types f prblems N input required Manipulate Strings and chars Prcess data using lps Branching (if, switch statements) Use f arrays / ArrayLists Prblems requiring srting Use f matrices Use f Stacks, Queues, Maps Use f recursin

8 Prgramming Prblems - Samples N Input One r tw prblems requiring n input Can generally be slved println statements Output must be EXACT Sample 1 UIL Sample 2 Lucky Number Scanner Class and Output Read int frm a data file Read lines frm a data file Split a line int data elements Frmat utput using printf Sample 3 Huse Numbers Strings and chars Read char s in a String Sample 3 Huse Numbers Read substrings Sample 4 IP Patterns (matches) Ways t Srt Sample 5 Duplicate vwels Arrays.srt Cllectins.srt Trees Sample 6 Butterflies Sample 7. printf Basics Printing String, int, duble variables Runding and printing dubles Left and right justificatin Printing in clumns Reading Data Reading an unknwn number f lines Sample 8 Reading in a matrix f ints Sample 9 Printing a matrix in clumns Sample 9 Sample 9. Using TreeSet Enter chars int a TreeSet t eliminate duplicate chars. Enter wrds int a TreeSet t srt. Practice, Practice, Practice Practice cntests n line and lcal