interface with new APS scheduling system

[prjemian]

from email:

BTW the new version is much simpler to use that the old one, I put here a fully functional example I wrote for testing it. There I use current_run() (returned as: 2020-1) and get_current_pi() (returned as PI last name: decarlo) to generate the raw data directory structure as 2020-1/decarlo and the get_current_emails() that is used to share the download link with all users associated with the proposal. I use the same functions in slack-gup to create and share a slack channel with the current users. This to say that is a powerful tool that perhaps should be considered as part of the standard bluesky deployment at that APS, so all beamlines will have meta data tagged with user/proposal information.

Thanks, @decarlof!

[prjemian]

@decarlof, I presume this could replace the apsbss?

[decarlof]

Perhaps is best to update apsbss to use the new rest API.

[prjemian]

The idea behind a separate apsbss project is to provide this access to any APS beam line, regardless of their use of bluesky.

[canismarko]

@decarlof Is this new API documented somewhere? I have a caproto-based IOC that mimics apsbss with some minor tweaks for our specific beamlines. I'm on board with a simpler API if possible.

https://github.com/canismarko/caproto-apps?tab=readme-ov-file#aps-bss

[prjemian]

I talked directly with Arvind Ramanathan. He supplied me with information I'm not certain is ready to be posted online. Talk with him directly.

[prjemian]

Ready to resume work on this issue. Contacted IS for latest testing recommendations