Analysis Coordinator

STAR Physics Analysis Coordinator

Responsibilities:

1) To work with the physics working group convenors and as appropriate the Software and Computing Project Leader, Simulations Leader, Reconstruction Software Leader, Offline Production Leader, Software Infrastructure Leader, and Run-Time Committee to determine the physics analysis and simulation software needs. To act as an interface between the physics working group convenors and the STAR Software and Computing Project on matters of physics software and computing and consult as needed with the Spokesperson on priorities for this software.

2) To work with the physics working group convenors and the STAR Software Project Leaders to faciliate the development and integration of physics analysis software in a way that is compatible with the overall STAR software approach. In so doing, the quality and performance of the reconstruction and simulation codes should be primary considerations.

3) To represent the physics working groups in discussions, with the software project leaders, on the physics analysis tasks to be performed during event reconstruction and at each stage of analysis. This will require that the physics analysis coordinator maintain an overall perspective of the status and availability of physics analysis and simulation software.

4) To facilitate input and communication between the physics working groups and the Simulations Leader on issues of determining and implementing the tradeoffs in the simulation capability versus physics.

5) To work with the Simulations Leader to make efficient use of the computing resources for the simulations needed by each of the physics working groups and to coordinate the physics working groups' input on design tradeoffs in the simulations with respect to general performance and overall capabilities.

6) To work with the Reconstruction Leader to establish requirements for DSTs and event reconstruction functionality.

Desired Skills and Abilities of the STAR Physics Analysis Coordinator:

1. well versed in STAR's physics program with a strong interest in physics, software and computing.

2. active in physics analysis, as an active developer and user of analysis codes.

3. strong in computing, able and willing to be an active participant in the computing group designing and developing the analysis software and the computing framework that supports it, and able to assess the quality and approach of the upstream reconstruction and simulation codes and give feedback.

4. direct experience in OO/C++ prefered.

5. be able to communicate well.

6. be able to commit a large fraction of time to this job and to have a presence at BNL as needed to interface with the software project leaders and the physics working group convenors.

Torre's statement on the job:
"A principal early role of the physics analysis coordinator would be to help assemble the physics analysis program for the mock data challenges, going well beyond the broad strokes of what physics should be looked at to developing the program to put in place the physics analysis software needed to execute it, software layered over a physics analysis infrastructure and toolset that the Analysis Coordinator should play a strong role in designing and ideally developing. Besides assembling the disparate needs of the PWGs to scope out and assign the design and implementation job, there is a lot of commonality in their needs that needs to be coordinated."

Calibration Coordinator

Position and responsibilities Description: Calibration coordinator

The STAR Calibration Coordinator's primary mission is focused toward the delivery of the calibration constants necessary to bring the data to an expected level of quality in support of the scientific program. The STAR Calibration coordinator is expected to work in concert with the STAR sub-systems software coordinator's designated calibration expert(s) to bring the data to a level of accuracy and quality in support of the scientific program. Before and during period of data taking and data production, this may be achieved through organizing calibration readiness meetings or communicate with the calibration experts and/or prepare/summarize and develop a calibration plan and schedule as required. He/she would interact with them to understand their problems and seek to work toward the elimination of mindless tasks through automation (support for online calibration, fast-offline, etc...). He/she will be responsible for pro-actively be the liaison (and main point of contact) between production, reconstruction, database or other coordinators and the sub-systems expert within the realm of expertise.

Authorities

• To achieve objectives, he/she has the authority to directly request highly prioritized productions.

• The Calibration coordinator priorities and schedule takes precedence over the individual sub-systems calibration needs.

• The Calibration coordinator may request progress status to the sub-system designated calibration experts

• If any, and in order to make the best of use of the global STAR calibration organization, he/she should be informed about on-going independent calibration effort and techniques being developed within the collaboration. Work should have his/her final approval before an integration in the STAR framework.

Responsibilities

He/she is responsible for identifying key milestones, determine immediate and future needs and communicate critical project issues in a timely fashion.
He/she is expected to be a central point of contact for the user's need within the area of expertise, respond to user problems, explain technology and methodologies and guide or mentor individuals as appropriate.

Skills

The STAR Calibration Coordinator is expected to demonstrate in depth understanding of fundamentals of the requirement specification, design, coding, and testing of technologies, methodologies and computational techniques related to the calibration needs of the STAR experiment. He/she should have a good understanding of the current and future application and technology and the faculty to learn, apply and implement new and emerging techniques and concepts very quickly.

Written by Jerome Lauret, S&C Leader 2003

 

Embedding structure

Organization, responsibilities, authorities and policies related to Embedding

Due to the increasing demand of the STAR collaboration, associated to the need for redundancy and more cohesion in the embedding activity, the embedding structure will move toward a distributed (computing) model paradigm with a structured set of responsibilities.

Organization

The embedding activity is a cross between the Simulation and Reconstruction activities and an important part of our data mining and data analysis process. Hence, the Embedding structure described below is an activity part of the Software & Computing (S&C) project structure.
The embedding activity will be led by the Embedding Coordinator (EC) helped by Embedding Deputies (ED) whose responsibilities and authorities are described below. It is understood that each Physics Working Group (PWG) may assign a contact person to help running an embedding series, or an Embedding Helper (EH). EC, ED and EH constitute the embedding team and core structure.
Embedding tasks will be created consistent with Appendix A “Initiating Embedding requests”.

 

The EC

The primary mission of the EC is to organize the work and the set of QA results related to each of the embedding series and communicate to the collaboration the progress and difficulties encountered in the data production process. The EC is the interface to many areas in STAR and to efficiently achieve the goals prescribed by the function, his/her responsibilities and authorities are described below:

The EC responsibilities are:

• The EC will work in close relation to the S&C Leader, Physics Analysis Coordinator (PAC) and the PWG Convener (PWGC) to define and facilitate the processing of the embedding requests needed by the collaboration to carry its scientific goals
• The EC will work with the PWG EH and gather keep up-to-date a set of macros and code aimed to provide appropriate QA for the PWG of interest
• The EC is responsible for the communication with the PWGC whenever embedding requests clarifications are needed (Physics process and/or intent unclear). This communication should happen only when the PWG EH  feels it is best to properly relefct the matters at hand. Communications to/from the PWG are expected to flow through the EH.
• The EC will communicate and feedback to the S&C leader any issues related to resources needed to accomplish the mission.
  • This may include discussions involving tasks lists and priorities, assignment of additional workforce, addition of computational resources allocations or difficulties encountered during the embedding process.
  • The discussions may be substantiated by summary of resource needed in the form of a written document (and provided by the EC) as requested.
• The EC is responsible for regularly bringing to the collaboration, via weekly S&C meeting venue, summaries of the tasks at hand and presenting the priorities or priority reshape as applies. All modified embedding requests are expected be announced at “a” S&C meeting as a summary and in addition of the communication with the PWGC. The frequency of such intervention is at the discretion of the EC and should not be below once a month
• The EC will be responsible for communicating with the ED and organize the work and tasks with the ED forming the core force of the embedding
• The EC is expected to handle and resolve with the ED issues (technical, resource) which may be raised by the EH and help toward a reolution and understanding

 

The EC authorities are

• Assign tasks as applies to the ED

• Request highly prioritized resource allocation to perform tasks
• Contact and discuss directly issues related to embedding requests with PWGC, PAC and S&C leader as applies
• Authoritative decisions are granted to the EC on the following area:
  • Declare an embedding request as improper and re-direct to the simulation leader
  • Re-prioritize or close embedding tasks and requests upon PWGC feedback or lack thereof.
  • Similarly, close an incomplete request upon PWGC lack of feedback
  • Re-assign priorities to a low priority shall precisions on an embedding request not be provided
  • Has authoritative leverage to declare an embedding series as 'good or not', based upon quantitative arguments and backed by proper embedding related QA.
• May request discussions and/or arbitration ruling to the PAC and S&C leader shall a contention arise with PWG(C) of interest

Conflict resolution

• In the event an embedding request is re-directed, re-prioritized, closed, declared 'bad' and shall the decision be contested by the  PWGC, the following applies:   
  
  • The responsibility to present a case and burden of proof is on the PWGC
  • Explicit discussion and approval of both S&C leader and Physics Analysis Coordinator (PAC) is necessary for re-considering the EC decision

 

The ED

The Embedding deputies' role and responsibilities are the one previously expected of the PDSF Tier1 center in 2005 and as defined in wording in 2007. An Embedding Deputy is intimately tight to a site's resources or a specific well-defined tasks (such as performing the base QA).

Those responsibilities include

• Respond to the EC requests for assigned tasks or work unit and provide estimate on time need to complete the tasks and feasibility of accomplishing he goals
• Prepare the embedding jobs and ensures the full workflow is working for achieving the asssigned tasks. Run a sample and help validate the production chain
• Help resolve technical details as appears and file/track trouble tickets as applies
• Keep the EC informed of progress, issues and difficulties encountered during the setup of the embedding process including resource allocation difficulties if any as well as technical difficulties
• Maintain the embedding framework consistent with a distributed model and provide feedback on improvements / fixes suitable for all sites
• Keep the embedding related documentation up-to-date
• Work closely with the EH as applies to accomplish task at hand

 

The authorities of the ED include

• Manage global assigned local resources as necessary to perform tasks
• Reshuffle and assign portion of resources to EH as see fit to perform task (tasks passed to the EH could include running a portion of the jobs and managing batch related to the relevant to the PWG's EH)
• Request EC intervention whenever necessary
• Directly communicate with the EH issues related to geometry tag, magnetic fields and other parameters wherever applies (see appendix B) while keeping summarizing the outcome to the EC
• Request feedback from the PWG EH on the adequacy of the samples provided to the PWG's requests. It is expected that the EH will communicate with the PWG (PWG specifc QA may be performed) and provide an explicit answer to the ED, accompagnied of material putting into evidence inadequacy of the sample or documenting adequacy as applies.

 

The EH

The Embedding Helpers are individuals recruited from within the PWG and hence, are STAR collaborators helping with the running of the embedding and carry some of its burden as a general service. The EH is part of a workforce supplement provided by the PWG and the expectation is for a EH to serve for a minimal time of two years during which, knowledge build-up and stability in our procedure and communication can be achieved. PWG may or may not provide EH, understanding however that the lack of EH may result in delays in delivery of results.

The EH responsibilities is to carry the communicating of all issues to/from the PWG and the Embedding team and seek that the requests made by the PWG are carried to their end. TO this end, rhe EH are expected to work closely with the ED and EC to perform the embedding tasks related to their respective PWG and consistent with the principles stated above. Examples of duties:

• Help clarifying embedding requests and communcate with the PWG in case of questions of lack of clarity
• Whenever an embedding request is determine valid by the EC and assigned to an ED, the EH will work within guidance and supervision of the assigned ED. The EH is then expected to carry the tasks assigned (or delegated) by the ED and possibly carry production related work to complete the requests on behalf of their related PWG. It is understood that resource managements and allocation remian the prime responsibility and call of the ED.
• Communicate pro-actively with the PWG and work internally to the PWG structure to carry QA testing on samples provided for satisfying the PWG requests.
• Provide a clear and documented response to the ED on the adequacy (or lack thereoff) of the produced sample for the request.

Appendix

Appendix A – Initiating Embedding requests

Embedding requests and need will be initiated and discussed within either PWG or R&D working group with respectively the supervision of the PWGC of interest or R&D simulation coordinator. The following caveats apply.

Pure embedding will be asked by PA of a pending publication / paper or whenever the accuracy needs to be as-close as possible to the real data. All other cases will be reviewed by the EC and may be transformed into a enriched sample simulation (“injection” simulation) wherever it applies and re-directed to the simulation leader consistent with the EC authorities.

After discussions within the PWG, embedding requests will be recorded by one of the PWGC via a provided interface which purpose will be to keep track of all requests and allow for priorities and overview of status and progress. The PWGC may designate an embedding point of contact as PWGC representative for embedding. In such case, the communication will be carried through the Embedding Point of contact.

No embedding requests outside of the provided framework and interface shall be satisfied and no “pending discussions” without an actual requests will be considered. It is also understood that a ill-defined requests may be closed by the EC consistent with the feedback gathering policy described in the EC responsibilities and authorities section. In such event, the request slot is not re-usable by the PWG.

Unless specified otherwise and priorities assigned explicitly by the PAC, EC or S&C leader, the requests will be considered as per a first in first done basis and upon availability of resources.

Appendix B – ED responsibilities and authorities regarding geometry tag and field settings

Upon request from the PWGC, the embedding team will ensure that the proper information is obtained as per the production series the embedding requests relate to. For a given production, the field setting and geometry tag used will be checked for consistency. Consistency must arise between simulation, real data and intended study. The geometry tag will be acquired from the production options page maintained by the production coordinator [currently Real Data production option].
The ED will be responsible for carrying those checks and will pass on functional macros to the EH assigned to assist them. If a setting is inaccurate (field or geometry tag), the EH shall immediately inform the PWG and the EC and request explicit confirmation. An embedding series shall not be started nor be run without the acknowledgment of the related field or geometry tag adequacy as chosen by the PWGC or PWG Point of Contact.

 

Generic Software Coordinator

General Position Description: detector sub-system software coordinator

Each detector sub-system must designate or identify a Software sub-system Coordinator who then becomes the main contact person for developing and maintaining the software written to bring the data for that sub-system to a Physics usable form and at a level of accuracy and expectations required for carrying the STAR Physics program involving the use of that particular sub-system. Additional manpower for the development of the Software may be allocated within the sub-system's group or requested by the sub-system software coordinator as additional manpower (aka service/community task).

As all realizes that there is no Physics without data reduction (via code/software), the Software coordinator is therefore a corner stone of sub-system's group. He/she has for main responsibilities:

1. The development and maintenance of the data acquisition reader for the offline chain, the detector geometry in the appropriate framework (Geant, reconstruction), the calibration database layout and content, at least one response simulator suitable for the simulation and embedding chains as well as responsible for the tracking specific software if applicable.
2. To disseminate in the collaboration the information related to the sub-system's of interest especially how to use the data in Physics studies: this may be accomplished via documentation, development of analysis API, regular updates and presentations at collaboration meetings or when asked by the S&C leader for a progress and/or readiness status report made regularly and pro-actively at the week S&C meeting
3. Similarly, to pro-actively bring forward to the S&C leader issues and show stoppers pertaining to the sub-system - examples span from delays in calibration procedures, resource needs or issues with the data quality. Case based presentation a the S&C meeting are highly encouraged and welcomed
4. To work in close relation to the database, reconstruction, simulation and calibration leader/coordinator when appropriate
5. To ensure compliance of his/her code with the STAR coding standard. Each new code is expected to be brought forward to a peer-review process where the code's standards, functionalities, adequacy of the documentation will be judged by peer developers.
6. Participate to the development of innovative projects aimed to enhance the Physics capabilities of the experiment as a whole. This may include participation to the development or support for new tracking methods, better framework, database evolution etc …

In order to bring the sub-system data closer to readiness, he/she

• Has the authority to request highly prioritized productions within the scope of efficiency, alignment or calibration studies, or any study going toward the convergence, consolidation or strengthening of the Physics results. The software sub-system coordinator designated a point of contact handling calibration production requests (in such case, the POC should be clearly specified).

• May request allocation of resources necessary to accomplish the outlined above tasks.

• Has the ultimate and final authority to organize the work at hand within his/her sub-system realm. For example, partitioning of calibration, simulation and other tasks as necessary and depending on available manpower.

• Is, unless indicated otherwise, the point of contact for modification of any code pertaining to the sub-system (others proposing modifications must inform the software sub-system coordinator).

• Is expected to communicate to the S&C leader concerns and issues which may be or become obstacles in achieving the above mission.

Written by Jerome Lauret, S&C Leader 2003

 

Reconstruction Leader

Responsibilities Description: Reconstruction Leader

General

The STAR Reconstruction Leader is responsible for maintaining, developing and expanding the STAR reconstruction code and framework. By reconstruction, one includes

• all detector / sub-system space point and/or physics quantity reconstruction
• Any related data structure handling from the loading of the raw data to the final physics usable DST (or derivate)
• Global tracking
• dE/dx and particle identification
• global event summary and hand-shaking with calibration constants and procedure
• code applying and/or performing corrections
• ...

The domain of development of Detector specific microscopic (slow) and parametrized (fast) response simulator will be done through discussions and advanced planning at Software & Computing meetings in conjunction with the Simulation and Database Leaders, affected sub-system detector coordinators and experts. The same applies with the cross-discipline (Reconstruction/Simulation) area known in STAR as embedding.

The reconstruction leader is expected to

• Take the lead on the study and evaluation of new tracking techniques and framework enhancement as needed by the STAR Physics program and future development
• Be aware of methodologies used in other High Energy or Nuclear Physics experiments and have deep understanding of their applicability and limitations
• Conceive new ideas and attempt to convince colleagues and scientific community of their validity, significance and importance and if need be, document and publish ideas
• Bring to attention innovative solutions and make recommendations to problems
• Elaborate and present schedule for deployment of solutions whenever accepted/approved
• Deploy, implement or integrate cost and time effective options/solutions in consideration of the research needs and schedules
• Complete responsibilities on time and according to the STAR program planning
• At every step, provide and maintain up to date documentation and offer support to users and developers of the STAR reconstruction softwares
• Obtain user feedback, diagnose problems and make software and documentation modifications as necessary.

The Reconstruction Leader's tremendous task will therefore be assisted by an expert per detector sub-system as designated by the detector Software sub-system coordinator. He/she will provide to this expert guidance as per integrating the sub-system specific code within the STAR reconstruction framework and global tracking. Further manpower may come through reconstruction projects (a new tracking software is an example) which, upon completion, would fall under the Reconstruction Leadership.

The Reconstruction Leader will be further assisted by the STAR Calibration Coordinator and the Production Coordinators. He/she should respond and assists to the Calibration Coordinator's findings and requests for integration of new algorithms or techniques specific to the Calibration coordinator's area of expertise. In such case, they will work closely together until task completion within the scope and planning defined above. The Reconstruction coordinator may request directly to the Productions Coordinator(s) highly prioritized production in order to resolve or evaluate a question pertinent to the reconstruction area.

However, to ensure a smooth execution of global planning and complete transparency between the area of reconstructions, simulations and calibration, schedule and priorities should be brought to the attention of the STAR S&C leader and further discussed in Software & Computing meetings prior to execution or deployment.

In the absence of the STAR S&C leader and deputies, shall the schedule and tasks priorities be left unclear, the Reconstruction Leader judgment on production schedule will take precedence over all others.

Reconstruction deputy

One or more reconstruction deputy/deputies may be assigned by the S&C Leader to assist further the task of the reconstruction leader.

A reconstruction deputy's task is to effectively take the lead on a specific project as defined. Within the scope of this project, the reconstruction deputy has the same authorities and responsibilities than the Reconstruction Leader. They are expected to work close to one another until the completion of the defined task. In the absence of the Reconstruction Leader, such deputy will take full responsibility over the Reconstruction Software and in all areas including his assigned project. Shall several deputies be in office, the choice will be left to the Reconstruction Leader (or following the chain of the S&C organization).

Furthermore, “a” reconstruction deputy may represent the reconstruction activities and progress at Collaboration and/or Analysis meetings and therefore, should remain informed of activities within this area of expertise.

Written by Jerome Lauret, S&C Leader 2003

 

Simulation Leader

Responsibilities Description: Simulation Leader

General

The STAR Simulation Leader is responsible for maintaining, developing and expanding the STAR simulation framework. His role is to analyze, design, formulate, implement and maintain the consistency of the simulation software(s), packages and toolkits solution to support the STAR research needs and/or in response to problems in support of the scientific program. A list of areas under the Simulation's leader responsibilities are:

• GEANT (or any other detector description and simulation toolkit), geometry and physics process modeling (i.e. describing the passage of elementary particles through the matter)
• Any related data structure handling
• Simulation framework response simulator including user API, framework, ...
• Event generators (in conjunction with the Event Generator Coordinator)
• ...

The domain of development of Detector specific microscopic (slow) and parametrized (fast) response simulator will be done through discussions and advanced planning at Software & Computing meetings in conjunction with the Reconstruction and Database Leaders, affected sub-system detector coordinators and experts. The same applies with the cross-discipline (Simulation/Reconstruction) area known in STAR as embedding.

Specifics (current as per 2003) and future

Within the current STAR simulation framework, the Simulation Leader is expected to attend to the development, test and maintenance of the existing geometry and materials database and related GEANT simulation software necessary to simulate the response of the STAR Detector used to interpret, without discontinuities, ongoing and forthcoming research data from the STAR Experiment at RHIC. He/she will be expected to

• coordinate with the site's production coordinators the usage of computing farms at several institutes for Monte-Carlo production
• respond to requests of the physics-working-groups
• provide guidance and expertise to the sub-system software coordinator's designated expert when comes to the modeling of their detector sub-system geometry description
• communicate with scientists and engineers to determine / solve / implement solutions to/to their problems
• plan and prepare the production and transmission of the STAR simulation data
• participate in the experiments physics program.

However, the STAR experiment and collaboration being a leaving body with evolving needs, the true meaning/ primary role and responsibility of this position is to ensure timely development of the software capability necessary to produce and interpret STAR research data and respond to the program's medium to long-term needs. To achieve this mission, the Simulation Leader must

• Stay current with the state of the art technology, survey the research literature, evaluate existing methodologies
• Follow the development of models, tools, toolkit for the simulation of geometry/material/detector response and modeling relevant to STAR Collaboration effort and determine feasibility of approach, develop and integrate new solutions within the STAR Simulation Software framework when applicable
• At every step, provide and maintain up to date documentation and offer support to users and developers of the STAR simulation softwares
• Obtain user feedback, diagnose problems and make software or documentation modifications as necessary.

Authorities

• Manage assigned resources as see fit to complete research goals on time and at appropriate standards
• To achieve objectives, he/she has the authority to directly organize highly prioritized productions within the alloted resources
• The STAR Simulation Leader is the ultimate point of contact and organizer of the STAR Simulation framework and software and therefore, any STAR simulation work and activities should be clearly stated and indicated to the Simulation Leader.
• Any Simulation Work should have his/her final approval before an integration in the STAR framework.

Responsibilities

He/she is responsible for identifying key milestones, determine immediate and future needs and communicate critical project issues in a timely fashion.
He/she is expected to be a central point of contact for the user's need within the area of expertise, respond to user problems, explain technology and methodologies and guide or mentor individuals as appropriate.

Skills

He/she is expected to demonstrate in depth understanding of fundamentals of the requirement specification, design, coding, and testing of technologies, methodologies and computational techniques related to the simulation needs of the STAR experiment. He/she should act as an architect for the future needs and therefore, have a good understanding of the current and future application and technology and the faculty to learn, apply and implement new and emerging techniques and concepts very quickly. The simulation leader would have a PhD in physics and several years of post-doctoral experience in the field of Heavy Ion, strong background in programming, using C++, FORTRAN, and GEANT3 and/or GEANT4, and good communicational skills.

Written by Jerome Lauret, S&C Leader 2003