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
I'm creating a new issue to track the yaml file created to describe the example diagram below. The diagram represents a configuration imagined for the Grand Challenge II that would involve a couple of detectors in Hall-C.
Comments on initial version put into branch Issue-7:
This should be moved into a directory examples/configs and be renamed into something like RTDP_EXA01.yaml for "RTDP EXample Advanced 01".
Instead of "machines" change to "rtdpcomponent". This is more accurate since these tend to represent a process as opposed to a machine.
The rtdpcomponent should have attributes:
type
config
host
launch_command
kill_command
The config attribute can be a complex configuration structure that is specific to the type. We will want rtdp.py to use the "host" and "launch_command" to start the process representing the component. If launch_command is empty or undefined, then it will be assumed that the process is already running by some other means.
The launch_command attribute can be something like:
ssh <host> et_start_fifo -f /tmp/etfifo
In this case, the rtdp.py script should replace the string "<host>" with the value from the host attribute. That way, if someone wants to change the host, it only needs to be change in one place. Similar substitutions may be made in the commands. For example <config_json_file> could signal to the rtdp.py script to reformat the config attribute into a JSON file that is automatically copied to the host and the file name then substituted in the launch command before it is executed.
Ultimately, I would like to be able to run rtdp.py file.yaml and have it launch and configure all processes needed for the system.
This should be enough to get started.
The text was updated successfully, but these errors were encountered:
I'm creating a new issue to track the yaml file created to describe the example diagram below. The diagram represents a configuration imagined for the Grand Challenge II that would involve a couple of detectors in Hall-C.
Comments on initial version put into branch Issue-7:
This should be moved into a directory examples/configs and be renamed into something like RTDP_EXA01.yaml for "RTDP EXample Advanced 01".
Instead of "machines" change to "rtdpcomponent". This is more accurate since these tend to represent a process as opposed to a machine.
The
rtdpcomponent
should have attributes:type
config
host
launch_command
kill_command
The config attribute can be a complex configuration structure that is specific to the type. We will want
rtdp.py
to use the"host"
and"launch_command"
to start the process representing the component. Iflaunch_command
is empty or undefined, then it will be assumed that the process is already running by some other means.The
launch_command
attribute can be something like:ssh <host> et_start_fifo -f /tmp/etfifo
In this case, the
rtdp.py
script should replace the string "<host>" with the value from the host attribute. That way, if someone wants to change the host, it only needs to be change in one place. Similar substitutions may be made in the commands. For example <config_json_file> could signal to thertdp.py
script to reformat theconfig
attribute into a JSON file that is automatically copied to thehost
and the file name then substituted in the launch command before it is executed.Ultimately, I would like to be able to run
rtdp.py file.yaml
and have it launch and configure all processes needed for the system.This should be enough to get started.
The text was updated successfully, but these errors were encountered: