You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there interest in, for the sake of consistency, making all example IOC P macro values start with 13? Or a different value prefix (e.g., AD)?
Most of the example IOCs use a default P macro value that starts with 13. However, some do not (e.g., BIS:, 3EIG1:, SR13ID01HU02IOC02:, and DCAM:).
I'm running into this because I'd like to just do a global replace of P=13 (or similar) with a prefix for the location where the IOC will be deployed, and now I'm seeing that I would need to do more than that for the example IOCs that don't use a P macro value that starts with 13. (Not a huge deal, but still...)
Here are the current P macro values based on "top" .adl files (which obviously excludes any detector plugins that are not linked via a "top" .adl file):
Is there interest in, for the sake of consistency, making all example IOC
P
macro values start with13
? Or a different value prefix (e.g.,AD
)?Most of the example IOCs use a default
P
macro value that starts with13
. However, some do not (e.g.,BIS:
,3EIG1:
,SR13ID01HU02IOC02:
, andDCAM:
).I'm running into this because I'd like to just do a global replace of
P=13
(or similar) with a prefix for the location where the IOC will be deployed, and now I'm seeing that I would need to do more than that for the example IOCs that don't use aP
macro value that starts with13
. (Not a huge deal, but still...)Here are the current
P
macro values based on "top".adl
files (which obviously excludes any detector plugins that are not linked via a "top".adl
file):The text was updated successfully, but these errors were encountered: