-
Notifications
You must be signed in to change notification settings - Fork 35
Feature/mfx is lcls2 #281
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
Feature/mfx is lcls2 #281
Conversation
…elog post; add timedrun for pedestals runs in RIXS
…. Add option to see if this is an LCLS1 or LCLS2 experiment
…X that has runs using either DAQ)
…heck to interactive jungfrau running, deal with multi-segment detectors (may change soon)
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
|
Once you look at all the comments, would you mind running these scripts again and making sure they work? |
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
Remove debug prints Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
Co-authored-by: KaushikMalapati <80156796+KaushikMalapati@users.noreply.github.com>
fixed & a little more comments.
|
There are a lot of comments that defer fixes to different efforts. If we're not going to address them immediately, can we make issues for them so we don't lose track of them? |
I only found two which I made issues for (the function for getting the experiment, and putting check_for_status in a try/except). Were there any others? |
|
|
|
fwiw I don't think any PR creator is obligated to spend time solving pre-existing problems unrelated to the PR, maybe we can just run ruff/precommit on this afterwards (see the dormant #270) |
Makes sense, I was assuming they were introduced here. |
|
I guess it's possible some of them are, I didn't look so closely but I know many of them are not created here |
Maybe two issues was too much for my goldfish memory. Looking through the comments this looks appropriate |
ZLLentz
left a comment
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.
I think everything here is good to merge
I do want a couple eyes on #270 so we can auto fix some of the incidentals
| else: | ||
| # then ask.....outside of python | ||
| print('unknown_hutch') | ||
| sys.exit() |
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.
Doesn't this sys.exit() need to be in the else block so that we don't return if we get the hutch from args.setExp?
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.
Shoot, yes!
changes for RIXS pedestals in takepeds
determine LCLS1 vs LCLS2 experiment
use of the former script in makepeds
makepeds_psana2 also for axis (to be worked on more)
small bug fixes
use of segment number currently needed in deploy step