XSEDE Data Modeling and Simulation Contest

At the moment, I know six+1 of you who have expressed interest
in this contest, (Brian, Eitan, Juan, Ian, Dan, Amir, Alex (alternate). 
That's enough 
to form one team (with room for one more student, possibly).  
It is my understanding that FSU is authorized to send one team, 
so unless another team appears, you can draw your conclusions.

I propose the following schedule:

                    XSEDE is broadcasting some information about Python.
                    I have to sit through this.  If you know Python already,
                    however, this just may be needless torture for you.)
Monday, March 28:   Python training (3-6, Room 499)
Tuesday, March 29:  Python training (3:30-6, Room 499)

Friday, April 1:    I give each team the practice problem.
Monday, April 4:    I collect the reports for the practice problem, and the 
                    judges look them over.  The teams will get an evaluation
                    as well as suggestions about how to improve the reports.

Friday, April 15:   I give each team the decisive problem.
Monday, April 18:   I collect the reports, the judges evaluate them, and
                    decide the winning team.  I give the XSEDE committee
                    the names of the members of the winning team.

July 17-21:         XSEDE conference in Miami, including a final programming
                    "playoff" among the winning teams.
                    It is my understanding that XSEDE will offer travel
                    support to the participating teams.  I hope this will
                    include hotels and car travel (but I doubt they will
                    pay airfare.)

I think most of you go to the Friday afternoon seminar at 3:00.  In that
case, I could try to meet you afterwards and show you some of the sample
problems that have been used in the past.  

The previous XSEDE competitions have included a surprisingly large amount
of documentation and instructions and grading rules.  Our own local problems 
will be much shorter, but you should be aware of what XSEDE might be looking
for.