Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PTP/meetings/December 2005"

< PTP‎ | meetings
(Meeting Notes)
Line 25: Line 25:
 
Attendees:
 
Attendees:
  
Rod Mach, Absoft
+
* Rod Mach, Absoft
Brad Chamberlain, Cray
+
* Brad Chamberlain, Cray
Beth Tibbitts, IBM
+
* Beth Tibbitts, IBM
Bill Chung, IBM
+
* Bill Chung, IBM
Don Pazel, IBM
+
* Don Pazel, IBM
Chih-Ping Cheng, Intel
+
* Chih-Ping Cheng, Intel
Wyatt Spear, University of Oregon
+
* Wyatt Spear, University of Oregon
Craig Rasmussen, LANL
+
* Craig Rasmussen, LANL
Greg Watson, LANL  
+
* Greg Watson, LANL  
  
 
# Introductions and areas of interest
 
# Introductions and areas of interest
  
Absoft:
+
: '''Absoft:'''
  
Interested in tool chain integration for their Fortran compiler and providing FX2 support in the parallel debugger.
+
: Interested in tool chain integration for their Fortran compiler and providing FX2 support in the parallel debugger.
  
Cray
+
: '''Cray'''
  
Exploring the possibility of using Eclipse with Cray development tools.
+
: Exploring the possibility of using Eclipse with Cray development tools.
  
Intel
+
: '''Intel'''
  
Interested in integration of IDB with parallel debugger.
+
: Interested in integration of IDB with parallel debugger.
  
IBM
+
: '''IBM'''
  
Contributed the MPI development tools to the PTP project. Interested in extending functionality of MPI tools and providing advanced debugging support.
+
: Contributed the MPI development tools to the PTP project. Interested in extending functionality of MPI tools and providing advanced debugging support.
  
U of Oregon
+
: '''U of Oregon'''
  
Interested in integrating their Tuning and Analysis Utilities (TAU) with Eclipse PTP.
+
: Interested in integrating their Tuning and Analysis Utilities (TAU) with Eclipse PTP.
  
LANL
+
: '''LANL'''
  
Focussing on the core parts of PTP: runtime support and parallel debugger. Also interested in Fortran language integration and providing advanced language features such as refactoring.
+
: Focussing on the core parts of PTP: runtime support and parallel debugger. Also interested in Fortran language integration and providing advanced language features such as refactoring.
  
 
# Intro to the Eclipse Foundation & committer process
 
# Intro to the Eclipse Foundation & committer process
  
Greg provided a brief overview of the Eclipse Foundation, its structure and objectives. He also described the process for becoming an Eclipse committer, and the rights and obligations of committers. Beth and Bill discussed their exeperiences from an IBM perspective.
+
: Greg provided a brief overview of the Eclipse Foundation, its structure and objectives. He also described the process for becoming an Eclipse committer, and the rights and obligations of committers. Beth and Bill discussed their exeperiences from an IBM perspective.
  
 
# PTP status & 1.0 release plans
 
# PTP status & 1.0 release plans
  
PTP is currently at RC2. Status of components as follows:
+
: PTP is currently at RC2. Status of components as follows:
  
FDT - ready, 1 outstanding bug
+
: FDT - ready, 1 outstanding bug
MPI development tools - ready, some minor issues to be fixed
+
: MPI development tools - ready, some minor issues to be fixed
Runtime - cleanup, some functionality still being added
+
: Runtime - cleanup, some functionality still being added
Debugger - functionality complete
+
: Debugger - functionality complete
A licensing issue was discovered with the debugger. This will necessitate re-implementing a component which will delay the release.
+
: A licensing issue was discovered with the debugger. This will necessitate re-implementing a component which will delay the release.
  
 
Packaging is still an issue. Java plugins are ok, but a decision on how to package runtime/debugger components still being made. Current thinking is to target a single OpenMPI version and a small number of architectures: Linux & MacOSX.
 
Packaging is still an issue. Java plugins are ok, but a decision on how to package runtime/debugger components still being made. Current thinking is to target a single OpenMPI version and a small number of architectures: Linux & MacOSX.

Revision as of 12:54, 6 April 2006

December 2005 Meeting

Date: December 05, 2005 Time: 1:00 PM EST

Call in information:

Toll Fee: 1 866 629-8602 Local number: 606-1012

Agenda

  1. Introductions and areas of interest
  2. Intro to the Eclipse Foundation & committer process
  3. PTP status & 1.0 release plans
  4. Planning for PTP 1.1
  5. Other business
  6. Next meeting

Meeting Notes

Date: December 05, 2005 Time: 1:00 PM EST

Attendees:

  • Rod Mach, Absoft
  • Brad Chamberlain, Cray
  • Beth Tibbitts, IBM
  • Bill Chung, IBM
  • Don Pazel, IBM
  • Chih-Ping Cheng, Intel
  • Wyatt Spear, University of Oregon
  • Craig Rasmussen, LANL
  • Greg Watson, LANL
  1. Introductions and areas of interest
Absoft:
Interested in tool chain integration for their Fortran compiler and providing FX2 support in the parallel debugger.
Cray
Exploring the possibility of using Eclipse with Cray development tools.
Intel
Interested in integration of IDB with parallel debugger.
IBM
Contributed the MPI development tools to the PTP project. Interested in extending functionality of MPI tools and providing advanced debugging support.
U of Oregon
Interested in integrating their Tuning and Analysis Utilities (TAU) with Eclipse PTP.
LANL
Focussing on the core parts of PTP: runtime support and parallel debugger. Also interested in Fortran language integration and providing advanced language features such as refactoring.
  1. Intro to the Eclipse Foundation & committer process
Greg provided a brief overview of the Eclipse Foundation, its structure and objectives. He also described the process for becoming an Eclipse committer, and the rights and obligations of committers. Beth and Bill discussed their exeperiences from an IBM perspective.
  1. PTP status & 1.0 release plans
PTP is currently at RC2. Status of components as follows:
FDT - ready, 1 outstanding bug
MPI development tools - ready, some minor issues to be fixed
Runtime - cleanup, some functionality still being added
Debugger - functionality complete
A licensing issue was discovered with the debugger. This will necessitate re-implementing a component which will delay the release.

Packaging is still an issue. Java plugins are ok, but a decision on how to package runtime/debugger components still being made. Current thinking is to target a single OpenMPI version and a small number of architectures: Linux & MacOSX.

Currently aiming for Dec 24 release.

Action: Greg to update release plan.

  1. Planning for PTP 1.1

To begin the planning process for 1.1, various organizations outlined the areas that they will be focussing on in the next 6-12 month time-frame.

LANL

Remote services, such as build/launch/debug, that will allow PTP to be used on a different machine from the parallel machine running the jobs. Resource managent: providing an interface (UI/API) to job schedulers that will allow resource requests and monitoring/notification of allocation status. Parallel debugger enhancements including: scalability, new UI features, and simplifying integration with other backend debuggers (non-gdb). Runtime integration: providing standard interfaces to simplify integration with other runtime/monitoring/resource allocation systems. IBM

OpenMP tools, similar to those provided for MPI XLF/XLC tool chain integration MPI data type support OpenRTE and remote build issues Replay/post mortem debugging support Fortran MPI development tools U of Oregon

Additional areas for integration of TAU with PTP Interfaces Conversion of some exising tools to Java Absoft

Integration of the Absoft Fortran complier with the Eclipse Fortran tool chain Action: Greg to develop planning document and post to web.

  1. Other business

Beth reminded everyone that there were PTP, CDT and Photran paper submissions to EclipseCon 2006. Everyone should vote for these papers to ensure they are accepted.

  1. Next meeting

It was decided to hold the next meeting on Tuesday January 10, 2006

Back to the top