Use provider.enforce_field_name_rules to correct field names

simonsobs · Nov 19, 2020 · 700b889 · 700b889
1 parent c2a1636
commit 700b889
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/agents/registry/registry.py b/agents/registry/registry.py
@@ -6,6 +6,7 @@
 from collections import defaultdict
 from ocs.ocs_feed import Feed
 
+from ocs.agent.aggregator import Provider
 
 class RegisteredAgent:
     """
@@ -114,7 +115,7 @@ def main(self, session: ocs_agent.OpSession, params=None):
             The session.data object for this process will be a dictionary containing
             the encoded RegisteredAgent object for each agent observed during the
             lifetime of the registry. For instance, this might look like
-            
+
             >>> session.data
             {'observatory.aggregator': 
                 {'expired': False,
@@ -153,6 +154,7 @@ def main(self, session: ocs_agent.OpSession, params=None):
                     field = f'{addr}_{op_name}'
                     field = field.replace('.', '_')
                     field = field.replace('-', '_')
+                    field = Provider._enforce_field_name_rules(field)
                     try:
                         Feed.verify_data_field_string(field)
                     except ValueError as e:

diff --git a/docs/agents/registry.rst b/docs/agents/registry.rst
@@ -50,7 +50,7 @@ The registry is also used to track the status of each agent's tasks and
 processes. `Operation codes` for each operation are regularly passed through an
 agent's heartbeat feed, which the registry assembles and publishes through its
 own OCS feed. This makes it possible to monitor individual operation states in
-grafan and to easily set alerts when a process stops running or when a task
+grafana and to easily set alerts when a process stops running or when a task
 fails.
 
 By mapping the enumeration values described in the ``OpCode`` documentation in