-
Notifications
You must be signed in to change notification settings - Fork 9
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
access APS proposal and ESAF information #333
Comments
Can the information in the beam time scheduling system be accessed to identify the current proposal and ESAF? At present, the proposal number AND the ESAF number must be entered by hand. |
The python program(s) can use ophyd to manage the structured information. |
Use the package already available ( |
Either
or
but note the most recent version might not be available on both. Check. |
Also, |
Run the EPICS IOC with |
The base name of |
For the python programs, combine them into one program with subcommands:
|
Build unit tests for this suite, knowing that certain key tests can only work on APS workstations. |
This adds |
python program to respond to EPICS IOC requests to load proposal/ESAFBuild this into |
python program to report current EPICS IOC valuesBuild this into |
Change the name from |
shell script for IOC management:
|
From https://jira.aps.anl.gov/browse/BCDA_GROUP-589: Provide information from the APS Oracle user database as PVs at each beam line so that this information may be added to new data files GOAL: create an
PVs only update when calendar system changes (which is when scheduling system sees a change). |
Most of this is already done here. No link to proposal (URL), not sure that proposal type is available. Not sure how to connect this with the beam time scheduling system for semi-automatic updates. For now, instrument team must update on-demand, providing APS cycle, ESAF, and proposal numbers. Each instance (of the EPICS database) will be pre-configured for IOC prefix and beamline name (as represented by |
This note from 2017:
|
Another note from 2018:
|
That import is not available today:
|
The import shown above has been refactored and is now used in the code here: apstools/apstools/beamtime/apsbss.py Line 31 in fc33050
|
Note also this repository in the APS (only) GitLab server: https://git.aps.anl.gov/jemian/aps_bss_user_info and this version of |
This can be a remote shell execution command from the MEDM/caQtDM GUI. Does not need more code. The command would call |
There is a wealth of information available from the APS proposal system, the experiment safety form system, and the beam time scheduling system. Provide access to this information so it can be included with the run metadata.
To be useful at many beam lines, provide:
This follows from https://jira.aps.anl.gov/browse/BCDA_GROUP-589 (restricted to APS onsite-only access).
The text was updated successfully, but these errors were encountered: