NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > IndividualGoals2008

Changes | Index | Contents | Search | Statistics | Go

Individual PEP Goals, 2008

When items are completed, mark them with a (toot toot)!

• Joe Brandt
• Patrick Brandt
• Mark Clark
• Ray Creager
• Bob Garwood
• Paul Marganian
• Mike McCarty
• Amy Shelton
• Mark Whitehead

Joe Brandt

• Personal Goals:
  • I will attend at least one software-specific conference to keep my skills current.
• Group Goals:
  • I will hold several lunch time talks on computer architecture, software development topics, and real-time systems.
• Project Goals:
  • I will support the PLC upgrades to the GBT primary and secondary servo systems.
  • I will participate in the creation of a servo testbed system, in support of servo software development.
  • I will participate in the architecture, design, and implementation of the next generation servo control system for the GBT.

Patrick Brandt

• Personal Goals:
• Group Goals:
• Project Goals:

Mark Clark

Personal Goals: Enhance current software development skill set

• Continue reading and applying techniques from Porteneuve's book to DSS.
• Attending a course on Web development if I could find one reasonably priced and at the right level.

Group Goals:

• After the “aggressive” stage of the DSS is complete, I again will attempt to lead lunches on darcs, prototype, and script.aculo.us.

Project Goals:

• Deploy the Phase II version of the Dynamic Scheduling System for trimester 08B.
• Attend ADASS in November and report on the accomplishments, problems, and future plans of the DSS project.
• Participate in a design review of the DSS project after Phase II is complete.
• Continue development of the Dynamic Scheduling System toward Phase II, incorporating feedback from trimester 08B and addressing ease-of-use issues.

Ray Creager

Personal Goals:

Group Goal:

Project Goals:

Bob Garwood

Personal Goals:

• Finish analyzing the GBT Orion survey data and work with collaborators on submitting a paper for publication. Time should be set aside during one development cycle in the next year to accomplish this goal.

Group Goals:

• Participate in at least one e2e short-term initiative. A suitable e2e project needs to be identified. There may be some task involving the archive and GBT data or old (unipops) single dish data that may be appropriate.
• Present at least one software lunch talk on some aspect of GBT data analysis to the group.

Project Goals:

• Complete the GBT SDFITS to ACSIS (JCMT format) conversion and determine how best to leverage the Starlink library (especially GAIA) for the K-band Focal Plane Array data reduction pipeline.
• Evolve the K-band Focal Plane Array data reduction pipeline design while working closely with NRAO’s Canadian collaborators from the University of Calgary, especially to determine how best to reuse concepts and code from the GALFACTS pipeline.

Paul Marganian

Personal Goals:

• To familiarize myself with a new programming language that enriches my understanding of programming in general; specifically, to learn Haskell to the point of being able to enhance and support the use of this language in the DSS.

Project Goals:

• Deploy the Phase II version of the Dynamic Scheduling System for trimester 08B.
• Attend ADASS in November and report on the accomplishments, problems, and future plans of the DSS project.
• Participate in a design review of the DSS project after Phase II is complete.
• Continue development of the Dynamic Scheduling System toward Phase II, incorporating feedback from trimester 08B and addressing ease-of-use issues.

Group Goals:

• To lead another workshop on web development, in a similar style as last years Turbo Gears workshop, but focusing more on Web 2.0 concepts (using the DSS for examples).

Mike McCarty

Personal Goals:

• Complete at least one graduate level computer science course.

Group Goals:

• Present at least one software lunch talk on a topic relevant to the group.

Project Goals:

• Deploy the Phase II version of the Dynamic Scheduling System for trimester 08B.
• Attend ADASS in October and report on the accomplishments, problems, and future plans of the DSS project.
• Participate in a design review of the DSS project after Phase II is complete.
• Continue development of the Dynamic Scheduling System toward Phase III, incorporating feedback from trimester 08B and addressing ease-of-use issues.

Amy Shelton

Personal Goals:

• Attend at least one technical conference to keep my software engineering skillset current.

Group/Site Goals:

• Work with the interim and new Site Director for Green Bank to ensure a smooth transition of leadership.

Project Goals:

• Participate as an active team member and Project Engineer in the upcoming test trimester for Dynamic Scheduling (Phase II), starting in June 2008.
• Evolve the Dynamic Scheduling System through Phase III, building on lessons learned and input gained from Phase II testing.

Mark Whitehead

Personal Goals:

• Attend at least one technical conference (e.g. the Embedded Systems Conference in Boston, Oct. 27-30). The purpose of attending such a conference would be to learn about (at least) multi-core development techniques, the latest FPGA technologies and C++ programming and debugging tips. As part of this goal, I will give at least one software lunch talk covering the conference material.
• Obtain and read “Programming Language Pragmatics” to evolve my skills as a software engineer.

Group Goals:

• Create multiple UML M&C class diagrams that explain the core system features.
• Gain first-hand experience on how radio astronomers acquire and process their data so that I can provide effective telescope support and better understand the fundamental service which the observatory provides. Some possibilities for gaining this experience are by arranging to join a student group on the 40' telescope, or watching an astronomer during an observing run, or attending scientific colloquia.

Project Goals:

• Participate in the effort in evolving the common user mode software for Mustang, ensuring that it is reliable and consistent with the GBT M&C system.
• Participate in a non-Mustang GBT project that provides an opportunity to create designs for new development and, ideally, an opportunity to learn to use Python effectively. I also would like to utilize one or more patterns to create a documented design that results in an intuitive and easy-to-maintain implementation.