-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SpaceCharge distortion corrections for FXT #393
Conversation
Is this intended for the upcoming SL22c release? |
It is critical for processing the Run 21 FXT data. If not in SL22c now (which is my preference), then we would probably need either an SL22d within a month, or we could have a second version of SL22c as this PR has no impact whatsoever on any existing nor soon-to-be-used chains . Thanks, |
81a95b0
to
6eb2cd9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After initial read through I don't see any major issues. Will look through again tomorrow. Would recommend a dedicated "clean up" PR to address STAR coding guildelines comment (Int_t --> int, etc...).
void StMagUtilities::UndoSpaceChargeFXTDistortion( const Float_t x[], Float_t Xprime[] , Int_t Sector ) | ||
{ | ||
|
||
const Int_t ORDER = 1 ; // Linear interpolation = 1, Quadratic = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
per STAR naming conventions, prefer int
to Int_t
, double
to Double_t
, etc...
Introduce distortion codes and steering routines to handle SpaceCharge distortions in BES-II FixedTarget data. Includes some very minor re-spacing of code text to keep it looking clean.