Page History
Options
(Aug. 2, 2021 brainstorming with Alberto, Bruce, Silke, Valerio, Matt, Dan D., Chris)
...
The thinking was that (2) is likely most feasible and conceptually most future proof, since large data in the future will likely be on the photon side so we will try that (i.e. move the software to the data). ACR should consider using psana-python in the future, but they will need additional tools developed for that (algorithms and a "playback buffer" that they can analyze in different ways).
Router Changes
This Jira ticket shows what was implemented:
After those changes this approach worked for CA EPICS (courtesy of Jesse Bellister): https://slacprod.servicenowservices.com/now/nav/ui/classic/params/target/incident.do%3Fsys_id%3Dfe3008a31b2135901c3262cfe54bcbaf%26sysparm_stack%3Dincident_list.do%3Fsysparm_query%3Dactive%3Dtrue
| Code Block |
|---|
Try with either appending the port 5064 to the ADDR_LIST or setting the EPICS_CA_SERVER_PORT to 5064, it's set to a non-standard port (5068) by default on lcls-srv01:
[softegr@lcls-srv01 ~]$ EPICS_CA_ADDR_LIST=172.21.152.78:5064 EPICS_CA_AUTO_ADDR_LIST=NO cainfo TMO:ACR:WAVEFORM
TMO:ACR:WAVEFORM
State: connected
Host: 172.21.152.78:5064
Access: read, no write
Native data type: DBF_FLOAT
Request type: DBR_FLOAT
Element count: 1026
[softegr@lcls-srv01 ~]$ EPICS_CA_ADDR_LIST=172.21.152.78 EPICS_CA_SERVER_PORT=5064 EPICS_CA_AUTO_ADDR_LIST=NO cainfo TMO:ACR:WAVEFORM
TMO:ACR:WAVEFORM
State: connected
Host: 172.21.152.78:5064
Access: read, no write
Native data type: DBF_FLOAT
Request type: DBR_FLOAT
Element count: 1026 |
Overview
Content Tools