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

XPCS at APS 8-ID-I Phase 1 #59

Open
3 of 4 tasks
dylanmcreynolds opened this issue Sep 3, 2019 · 14 comments
Open
3 of 4 tasks

XPCS at APS 8-ID-I Phase 1 #59

dylanmcreynolds opened this issue Sep 3, 2019 · 14 comments

Comments

@dylanmcreynolds
Copy link
Collaborator

dylanmcreynolds commented Sep 3, 2019

@prjemian
Copy link

As noted in aps-8id-dys/ipython-8idiuser#39 (comment), we've already tested the DM workflow from bluesky and then from the linux command line (with the tool that SPEC will use from now on). We need confirmation tests from both SPEC and bluesky that both are ready to use the APS Data Management tools with our final edit of the shared tools to initiate that workflow.

@prjemian
Copy link

The instrument works with bluesky now, we'll see what additional bluesky capabilities must be available for initial operations. For operations with a user, we'll need some more support plans (converted from SPEC macros).

@prjemian
Copy link

Instrument is ready for operations with the new Rigaku detector. The lambda has one outstanding issue that blocks us using it. We're working on that now.

@prjemian
Copy link

Also, APS had a brief, unexpected shutdown this week. We just have beam restored today.

Clipboard01

@prjemian
Copy link

Also, one payoff from the bluesky effort is that the data management workflow tools can also be called from SPEC more efficiently using part of the bluesky code base. The instrument is very happy about that!

I'll tick off the third checkbox, that instrument is ready for operations.

@ahexemer
Copy link

ahexemer commented Oct 11, 2019 via email

@prjemian
Copy link

prjemian commented Oct 11, 2019

On the Phase 1 goals for the software stack, there is an item marked Allow for data reduction and analysis using Xi-CAM and this will be a challenge for us to reach since we have not yet begun to use Xi-CAM for our workflow.

@prjemian
Copy link

We worked around the Lambda detector issue previously described and have assembled all the parts for a one-day operation test 2019-11-23.. On track for Phase 1 milestone.

@dylanmcreynolds
Copy link
Collaborator Author

@prjemian @qzhang234 It seems to me that we have accomplished this task, yes?

@prjemian
Copy link

prjemian commented Feb 10, 2020 via email

@qzhang234
Copy link

@prjemian @dylanmcreynolds Issue #46 has been solved with Andi's document to the Data Pilot report. The related problem now is building the Nexus format for XPCS results so I'll regard #46 itself as complete

@qzhang234
Copy link

qzhang234 commented Feb 10, 2020

@prjemian @dylanmcreynolds However currently we are having trouble with running Bluesky & Lambda for more than a few hours. We tried running users with Bluesky and user reported this problem. More details in the issue below:
aps-8id-dys/ipython-8idiuser#146
I believe once this problem is solved we will try deploy Bluesky to the general users

@dylanmcreynolds
Copy link
Collaborator Author

@prjemian Good point, collecting ontology for xpcs is an on-going thing. I re-opened 46 and assigned it to relevant parties. The question I have is whether this blocks "completion" of epics Phase 1 at 8-ID-I, CSX and COSMIC.

@prjemian
Copy link

I'm not convinced that the ontology agreement should block Phase I. A great Phase I outcome is that we have identified such and are working on it (a Phase II goal).

short version

We have not yet satisfied the one-week usage milestone.

long version

As for our Lambda detector, only the recent problem blocks us from completing the one-week usage milestone. The problem definitely is from how we use the Lambda's EPICS support from bluesky. New EPICS support is imminent (within the week) and that will mean replacement of existing bluesky/ophyd code. So, we have suspended diagnosing further on the existing ophyd support layer. As we code up the ophyd interface to the new EPICS support, we'll be watchful for exactly this problem.

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

No branches or pull requests

4 participants