Skip to content

Minor documentation inconsistency fixes #808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
knopers8 wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −5
Open

Minor documentation inconsistency fixes #808

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ There are two ways of interacting with AliECS:

### I want to ensure AliECS can **run and control my process**

* **My software is based on FairMQ and/or O² DPL (Data Processing Later)**
* **My software is based on FairMQ and/or O² DPL (Data Processing Layer)**

AliECS natively supports FairMQ (and DPL) devices.
Head to [ControlWorkflows](https://github.com/AliceO2Group/ControlWorkflows) for instructions on how to configure your software to be controlled by AliECS.
Expand Down
2 changes: 1 addition & 1 deletion core/integration/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -177,7 +177,7 @@ DD scheduler plugin informs the Data Distribution software about the pool of FLP

See [Legacy events: Kafka plugin](/docs/kafka.md#legacy-events-kafka-plugin)

# LHC plugin
## LHC

This plugin listens to Kafka messages coming from the LHC DIP Client and pushes any relevant internal notifications to the AliECS core.
Its main purpose is to provide basic information about ongoing LHC activity (e.g. fill information) to affected parties and allow AliECS to react upon them (e.g. by automatically stopping a physics run when stable beams are over).
Expand Down
2 changes: 1 addition & 1 deletion docs/building.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ Running `make` will take a while as all dependencies are gathered, built and ins
$ make all
```

You should find several executables including `o2control-core`, `o2control-executor` and `coconut` in `bin`.
You should find several executables including `o2-aliecs-core`, `o2-aliecs-executor` and `coconut` in `bin`.

For subsequent builds (after the first one), plain `make` (instead of `make all`) is sufficient. See the [Makefile reference](makefile_reference.md) for more information.

Expand Down
4 changes: 2 additions & 2 deletions docs/running.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The recommended way to set up a Mesos cluster is by performing a complete deploy
The AliECS core on the head node should be stopped (`systemctl stop o2-aliecs-core`) and your own AliECS core should be made to point to the head node.
Typically, it can be done by replacing the AliECS core binary on the head node with your own and restarting the `o2-aliecs-core` systemd service.

The following example flags assume a remote head node `centosvmtest`, the use of the default `settings.yaml` file, very verbose output, verbose workflow dumps on every workflow deployment, and the executor having been copied (`scp`) to `/opt/o2control-executor` on all controlled nodes:
The following example flags assume a remote head node `centosvmtest`, the use of the default `settings.yaml` file, very verbose output, verbose workflow dumps on every workflow deployment, and the executor having been copied (`scp`) to `/opt/o2-aliecs-executor` on all controlled nodes:

```bash
--coreConfigurationUri
Expand All @@ -22,7 +22,7 @@ http://centosvmtest:5050/api/v1/scheduler
--verbose
--veryVerbose
--executor
/opt/o2control-executor
/opt/o2-aliecs-executor
--dumpWorkflows
```

Expand Down
Loading