Skip to content
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

Merged
merged 3 commits into from
Sep 9, 2022

Conversation

genevb
Copy link
Contributor

@genevb genevb commented Sep 7, 2022

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.

@plexoos
Copy link
Member

plexoos commented Sep 7, 2022

Is this intended for the upcoming SL22c release?

@genevb
Copy link
Contributor Author

genevb commented Sep 7, 2022

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,
-Gene

@plexoos
Copy link
Member

plexoos commented Sep 7, 2022

We can include this in SL22c. I recall we expected some updates for TPC dE/dx and forward tracking. Was it something beyond the merged #383 and #387?

@plexoos plexoos added this to the SL22c milestone Sep 7, 2022
StRoot/StDbUtilities/StMagUtilities.cxx Outdated Show resolved Hide resolved
StRoot/StDbUtilities/StMagUtilities.cxx Outdated Show resolved Hide resolved
StRoot/StDbUtilities/StMagUtilities.cxx Outdated Show resolved Hide resolved
StRoot/StDbUtilities/StMagUtilities.cxx Outdated Show resolved Hide resolved
@plexoos plexoos merged commit 47d45ad into star-bnl:main Sep 9, 2022
@genevb genevb deleted the FXT_SpaceCharge branch September 9, 2022 17:04
Copy link
Contributor

@klendathu2k klendathu2k left a 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
Copy link
Contributor

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants