1 / 9

TRAC Allocations Report

Kent Milfeld, TACC TG Allocations Coordinator Aug. 13, 2009. TRAC Allocations Report. Outline. TRAC Request Summary Allocation Period (Oct. 1, 2009  Sept. 30, 2010) Changes to TRAC Review Process Issues with TG-Wide Roaming Access TRAC Request Tracking. Sept. 2009 Allocations – Stats.

karim
Download Presentation

TRAC Allocations Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Kent Milfeld, TACC TG Allocations Coordinator Aug. 13, 2009 TRAC Allocations Report

  2. Outline • TRAC Request SummaryAllocation Period (Oct. 1, 2009  Sept. 30, 2010) • Changes to TRAC Review Process • Issues with TG-Wide Roaming Access • TRAC Request Tracking

  3. Sept. 2009 Allocations – Stats

  4. Changes to Review Process • Parallel Sessions atTRAC meeting (Trial) • Plenary Session for top 20 Requests. • 2 Break-out Sessions: PHY/AST/ATM & MCB/CHE/DMR • Reconciliation Session: Adjust total allocation to availability • New Review Form addresses Methodology, Efficiency and Computational Plan Criteria • Better Reviewer/Request matching: • FOS (field of Science) matching • Reviewer Preference • Given Titles, reviewers are asked state their preference: Prefer, Indifferent, Unfamiliar

  5. Reference to Criteria Review Rating Recommendation (Overall Evaluation) Methodology (Algorithms, Packages, Libraries) Efficiency (Performance, Optimization Scaling) Computational Plan (SU Calculations, Justification)

  6. TG-Wide Roaming Access • TG-Wide Roaming Access • Has evolved into ineffective mechanism. • Mid-range system Pool ? • Abe (NCS), QueenB (LONI), Lonestar (TACC), Steele (Purdue) • Serious RP concerns about managing user expectations.

  7. TG-Wide Roaming Access • Remove TG-Roaming from Resource Request form. • Provide multi-system access through: • Better Choice: Allow User-requested allocation % distributions • If necessary, distribution can be readjusted through transfers. • Not so Good: Abe/QB/Lonestar/Steel allocation pool (like the present Abe/QB model). • Harder to manage • RPs suspect ‘popular’ resources will run out early

  8. Request Tracking • Now Using Google docs to Track Monitoring. • Startups • Supplement/Justification/Advances • Responsibility for Processing can be shared. • Site Reps can easily see/determine status. • Can be used as “case study”/prototype for an enhanced POPS Interface.

  9. Allocations • Questions?

More Related