TAU 2012 Power Grid Simulation Contest

[Announcements] [Contest Benchmarks and Results] [Contact Information] [Schedule] [Submission Information] [Evaluation and Ranking] [Utility Scripts] [Frequently Asked Questions] [Benchmark Format] [Participating Teams] [Call for Participation]

Announcements


Contest Benchmarks and Results

  1. Test benchmarks: ibmpg1t and ibmpg2t from this site.
  2. Final benchmarks will be released after the contest.
  3. TAU 2012 Contest Presentation with Results.

Contact Information


Schedule

July 13, 2011 Annoucement of 2012 Contest.
Aug 30, 2011 Release of first benchmark.
Sep 9, 2011 Registration deadline.
Oct 9, 2011 Receive alpha (preliminary) binaries from all teams
Each team is expected to generate the solutions on one test benchmark with the same input and output format by that date.
Dec 4, 2011 Deadline for final binaries from all teams.
Dec, 2011 to Jan 12, 2012 TAU 2012, Announce contest results.

Submission Information

  1. Please name your binary as your solver name. We do not want to have 5 "solver" and 5 "main" binaries.
  2. You do not need to print extra information if that takes runtime. All we need is the solution file and we will count the runtime ourself.
  3. If you have any special performance tuning parms, please remove them or hardcode inside your program. For the contest, we only take two options, one is for input file and one is for output file.
  4. Please provide an arg to your program so that I can specify the solution file name.
  5. Please try to submit a statically-linked binary as it helps with portability. (use gcc -static).
  6. Each team is allowed to submit a single binary that should run on all the benchmarks.
  7. We encourage the participants to explore parallel implementations of the simulation algorithms. Our machine has 32 cores, 64 threads and supports OpenMP. Note that we do not restricts with OpenMP implementation though.
  8. No precomputed information can be used to influence the current run. The run directories will be cleaned prior to each run.
  9. Purpose of alpha (preliminary) binary submission:
    The purpose of the alpha binary submission is: (a) to verify that I can run your binary on the contest machine. (b) to test that your binary is able to produce required formats on the test benchmarks.
  10. Memory limit per job: 700GB RAM, 300GB swap memory
  11. Machine configuration for the contest:
    • OS: Red Hat Enterprise Linux Server release 5.6 (Tikanga)
    • CPU: 64-bit Intel(R) Xeon(R) CPU X7560 @ 2.27GHz
    • GCC version: gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)
      Thread model: posix Target: x86_64-redhat-linux
    • BLAS: versio 3.0, release 37.e15. lapack version 3.0, release 37.e15
    • Tcl: 8.4.13, release 4.e15
    • Information from /proc/cpuinfo:
      processor	: 0
      vendor_id	: GenuineIntel
      cpu family	: 6
      model		: 46
      model name	: Intel(R) Xeon(R) CPU           X7560  @ 2.27GHz
      stepping	: 6
      cpu MHz		: 1064.000
      cache size	: 24576 KB
      physical id	: 0
      siblings	: 16
      core id		: 0
      cpu cores	: 8
      apicid		: 0
      fpu		: yes
      fpu_exception	: yes
      cpuid level	: 11
      wp		: yes
      flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx rdtscp lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm
      bogomips	: 4522.16
      clflush size	: 64
      cache_alignment	: 64
      address sizes	: 44 bits physical, 48 bits virtual
      power management: [8]
      
      
      processor	: 63
      vendor_id	: GenuineIntel
      cpu family	: 6
      model		: 46
      model name	: Intel(R) Xeon(R) CPU           X7560  @ 2.27GHz
      stepping	: 6
      cpu MHz		: 1064.000
      cache size	: 24576 KB
      physical id	: 3
      siblings	: 16
      core id		: 11
      cpu cores	: 8
      apicid		: 119
      fpu		: yes
      fpu_exception	: yes
      cpuid level	: 11
      wp		: yes
      flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx rdtscp lm constant_tsc ida nonstop_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm
      bogomips	: 4522.07
      clflush size	: 64
      cache_alignment	: 64
      address sizes	: 44 bits physical, 48 bits virtual
      power management: [8]
        

Evaluation and Ranking


Utility Scripts


Frequently Asked Questions


Benchmark Format

The input and output format of each benchmark are the same as the one published at http://dropzone.tamu.edu/~pli/PGBench/.
In the output file, the voltage at each node needs to be printed as %.4e format (4 digital after decimal points), which means the accuracy is at 0.1 mV.

Participating Teams


Call for Participation

Registration for the contest is closed.



Webmaster Zhuo Li.
Last updated: Jan 12, 2011