Add comment to jacobian creation of alignment to measurement variables. Also create output for track trajectorey fit for chi2 and ndf. Since we dont want to put function inside function, inside function
Change how we know if the state is A: Associated with a hit. This is needed for the alignment part. B:If the state came from the pattern recognition but does not have a hit. Create the first map from the scatter to the boolean to yes this is an original scatterer. Need to still add that it contains a hit
Now we store the boolean that a particular GBL point is a original track state and if it has a hit
Last commit made no sense since you need to associate a point with some state and you can not do that with just a boolean. This commit creates a new map between a gbl point and a state. If not exist then it is a NULL pointer. The hit information can be determined now from the state
remove hit boolean since this information should be in the state
Remove utility middle man for determination of alignment jacobain.
Change EUTelTrack to not store hits but EUTelTrackState this should hold state. Tracks should just hold states and chi2 ndf etc. NEED TO STILL FIX OUTPUT AND OUTPUT OF THE PROCESSOR
Move the creation of the alignment jacobian outside GBLFitter since this does not need to be created each time
Addtion of alignment jacobian matrix comment
Start of new mille align processor
Creation of new millepede class. This is done for three reasons A)Some of the function we define in the class GBLFitter is not GBL stuff. B)Some of the code is repeated in different processor. I found the creation of the global parameters for one. C) Some of the code runpede, creating the gear file for the output is specific to a particular processor. This sould not be the case
Add _alignmentmode and begin to create the jacobian
Add creation of jacobian to millepede class
Now determine the size of the matrix and global parameters vector.
Create the global parameters label from states
Add the ability to store fixed planes
Add the beginnings of the last of the basic functions. The benefits of this function are A)Some of this is defined in GBLFitter. It as nothing to do with that even if the jacobian and global parameters labels are used there. B)The use of global parameters is used in binary creation and executing this binary. We dont need to repeat thar code in two places. C)pederun parseMilleOut etc are functions in a particular processor. They should be able to be used by processor that wants to use them.
Add some more functions to EUtelMillepede.cpp
Remove conflicts between branches
Make error for no pixel geometry in gear more descriptive