|
|
There are many types of computer setups, consisting of different software installations and use cases. This page attempts to define some of the most common configurations and make helpful suggestions to people setting up test-stands. Choosing a configuration is really about choosing a degree of separation for all the applications than need to run. How many different applications are you going to run on the same machine, vs. how many machines are you going to split the applications over?
|
|
|
|
|
|
One thing to keep in mind is that the below definitions are combined onto the same machine very often in test-stand setups. For example, running the RTS and DAQ on the same machine is quite common making that machine a "Frontend/DAQ".
|
|
|
|
|
|
### Primary Machine Definitions
|
|
|
|
|
|
- ***Frontend (FE) Computer***
|
|
|
- Runs the Real Time System (RTS)
|
... | ... | @@ -13,15 +14,22 @@ One thing to keep in mind is that the below definitions are combined onto the sa |
|
|
- ***Workstation Computer***
|
|
|
- Runs MATLAB for model editing and workstation tools like ndscope, dtt, etc.
|
|
|
- [How to setup a Workstation](Debian-Workstation-Installation-Guide)
|
|
|
- ***CyMAC Configuration***
|
|
|
- A machine that combines functionality of the Frontend, DAQ and workstation all on one computer.
|
|
|
- One drawback of this setup is MATLAB and other workstations tools can take up a lot of resources (CPU/memory) and negatively impact the functionality of the RTS.
|
|
|
- [How to setup a CyMAC](https://git.ligo.org/cds/software/advligorts/-/wikis/Debian-CyMAC-Installation-Guide)
|
|
|
- ***Bootserver***
|
|
|
- A central bootserver supports multiple diskless frontend machines. A second network connects the RTS frontends to one or more DAQ computers.
|
|
|
- Once you have more than one FE computer it can become complicated to manage the RTS on each one individually. In these cases a bootserver is setup so that the FE software can be configured in a single place and FE computers will PXE boot from it.
|
|
|
- The DAQ is usually moved to its own server at this level of complexity because the output from each FE needs to be aggregated by the DAQ.
|
|
|
|
|
|
### Compound Machine Definitions
|
|
|
The above definitions are often combined onto the same machine in test-stand setups, this is due to limited hardware, or to simplify systems that don't have too many models/data.
|
|
|
|
|
|
- ***Standalone Frontend or Frontend/DAQ***
|
|
|
- A machine that combines functionality of the Frontend, DAQ, and usually hosts a network share of the models over NFS.
|
|
|
- This configuration is often preferred over a CyMAC because of the limitations listed below.
|
|
|
- ***CyMAC Configuration***
|
|
|
- A machine that combines functionality of the Frontend, DAQ and workstation all on one computer.
|
|
|
- One drawback of this setup is MATLAB and other workstations tools can take up a lot of resources (CPU/memory) and negatively impact the functionality of the RTS.
|
|
|
- [How to setup a CyMAC](https://git.ligo.org/cds/software/advligorts/-/wikis/Debian-CyMAC-Installation-Guide)
|
|
|
|
|
|
## Example Configurations
|
|
|
Below are a few common configurations pictured along with some pros and cons of each one.
|
|
|
|
... | ... | |