APS DM DAQs may be created for each IOC (for different dataDirectories)

[prjemian]

Comments starting from #912 (comment) represent an upgrade to the support demonstrated by the BDP demo this week. Hoist the support from the demo first, then upgrade in a new issue (for the next milestone).

Originally posted by @prjemian in #912 (comment)

[prjemian]

The question starts with: how to get workstation into this request for an api object? DaqApiFactory.getExperimentDaqApi()

According to the docs, there are three kwargs to the constructor:

After running apstools.utils.dm_setup(), the OS environment variables are copied into the Python session. These examples at one APS beam line:

========================= ========================================
key                       value                                   
========================= ========================================
DM_APS_DB_WEB_SERVICE_URL https://xraydtn01.xray.aps.anl.gov:11236
DM_CAT_WEB_SERVICE_URL    https://s1iddm.xray.aps.anl.gov:44436   
DM_DAQ_WEB_SERVICE_URL    https://s1idge3dm.xray.aps.anl.gov:33336
DM_DS_WEB_SERVICE_URL     https://xraydtn01.xray.aps.anl.gov:22237
DM_PROC_WEB_SERVICE_URL   https://s1iddm.xray.aps.anl.gov:55536   
========================= ========================================

[prjemian]

So,

from os import environ
from apstools.utils import dm_setup
from dm.daq_web_service.api.experimentDaqApi import ExperimentDaqApi

dm_setup()
api = ExperimentDaqApi(url=environ["DM_DAQ_WEB_SERVICE_URL"])

[prjemian]

It's not obvious what exactly is the work to resolve this issue. Pushing to next cycle.

[prjemian]

Hoist various code from APS 8-ID XPCS

• dm_isDaqActive
• dm_daq_wait_upload_plan

Weren't these plans already hoisted?

• mesh_list_grid_scan
• mesh_scan_nd

[prjemian]

Can wait for next milestone.