562 detailed trajectory information writer

[rahmans1]

Briefly, what does this PR introduce?

Initial implementation of trajectory writer provided by Shyam

What kind of change does this PR introduce?

• Bug fix (issue #__)
• New feature (issue Detailed trajectory information writer #562 )
• Documentation update
• Other: __

Please check if this PR fulfills the following:

• Tests for the changes have been added
• Documentation has been added / updated
• Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

No

Does this PR change default behavior?

[rahmans1]

There seems to be a few things that are not clear in the initial implementation

1. What's listed as the output tag in the tracking.cc file is being used as the input tag in the factory

Proposed solution: Replace "outputTrajectories" in tracking.cc with "CentralCKFTrajectories" or follow the example in other similar factories.

2. Tries to fetch edm4eic::Trajectory object which doesn't have a vector structure and so the later portions of the code will not work. See error below.

/lustre06/project/6061913/rahmans/EIC/tests/EICrecon/src/global/tracking/Trajectory_factory.cc: In member function ‘virtual void eicrecon::Trajectory_factory::Process(const std::shared_ptr<const JEvent>&)’:
/lustre06/project/6061913/rahmans/EIC/tests/EICrecon/src/global/tracking/Trajectory_factory.cc:36:53: error: invalid use of ‘edm4eic::Trajectory::Trajectory’
   36 |             for (size_t i = 0; i < trajectory_info->Trajectory()->size(); i++) {
      |                                                     ^~~~~~~~~~
/lustre06/project/6061913/rahmans/EIC/tests/EICrecon/src/global/tracking/Trajectory_factory.cc:37:61: error: invalid use of ‘edm4eic::Trajectory::Trajectory’
   37 |                 auto trajectory_params = (*trajectory_info->Trajectory())[i];
      |                                                             ^~~~~~~~~~
/lustre06/project/6061913/rahmans/EIC/tests/EICrecon/src/global/tracking/Trajectory_factory.cc: In member function ‘virtual void eicrecon::Trajectory_factory::Process(const std::shared_ptr<const JEvent>&)’:
/lustre06/project/6061913/rahmans/EIC/tests/EICrecon/src/global/tracking/Trajectory_factory.cc:36:53: error: invalid use of ‘edm4eic::Trajectory::Trajectory’
   36 |             for (size_t i = 0; i < trajectory_info->Trajectory()->size(); i++) {
      |                                                     ^~~~~~~~~~
/lustre06/project/6061913/rahmans/EIC/tests/EICrecon/src/global/tracking/Trajectory_factory.cc:37:61: error: invalid use of ‘edm4eic::Trajectory::Trajectory’
   37 |                 auto trajectory_params = (*trajectory_info->Trajectory())[i];
      |                                                             ^~~~~~~~~~

Proposed solution: I am guessing what was intended was to get the eicrecon::TrackingResultTrajectory

    std::string input_tag = GetInputTags()[0];
    auto trajectories = event->Get<eicrecon::TrackingResultTrajectory>(input_tag);

and then pass it to an algorithm which can write out the track parameters.

3. @ShujieL Can you comment what the broader goal of implementing this functionality was?

@DraTeots Any comments/suggestions? Is the functionality intended with this factory already available within existing factories?

[wdconinc]

@rahmans1 Can we close this? We are now writing trajectories as part of CKFTracking.