Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tango
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira issues
Open Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
LOFAR2.0
tango
Commits
3fc93b10
Commit
3fc93b10
authored
3 years ago
by
Jan David Mol
Browse files
Options
Downloads
Patches
Plain Diff
L2SS-391
: Improved order in documentation
parent
5b6c5379
No related branches found
No related tags found
1 merge request
!144
L2SS-391: Add boot device
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+22
-26
22 additions, 26 deletions
README.md
with
22 additions
and
26 deletions
README.md
+
22
−
26
View file @
3fc93b10
...
...
@@ -31,22 +31,20 @@ cd docker-compose
make bootstrap
```
PS:
Once per reboot, the host kernel needs to be configured. This is already included in
`make bootstrap`
:
Once per reboot, the host kernel needs to be configured. This is already included in
`make bootstrap`
:
```
make start elk-configure-host
```
## Use simulators
If you lack access to LOFAR station hardware, configure the devices to use their simulators instead:
```
for sim in
sdp-sim recv-sim unb2-sim
; do
for sim in
../CDB/*-sim-config.json
; do
../sbin/update_ConfigDb.sh ../CDB${sim}-config.json
done
```
## Start up
the remaining containers
## Start up
Now we can start all containers, and make sure everything is up:
...
...
@@ -57,6 +55,25 @@ make status
If not, you can inspect why with
`docker logs <container>`
.
The software devices start in an OFF state. To boot the devices, go to Jupyter (port 8888), start a new notebook, and run:
```
# start boot device
boot.initialise()
boot.on()
# this should report as DevState.ON
boot.status()
# boot station
boot.initialise_station()
# wait until this reports the initialisation is done (or was stopped half way):
print(f"Still initialising: {boot.initialising_station_R}. Completeness: {boot.initialisation_progress_R}%. State: {boot.initialisation_status_R}")
```
Then, in Grafana (port 3000), you should see the devices reaching the ON state.
# Remote Interfaces
The station provides the following interfaces accessible through your browser (assuming you run on
`localhost`
):
...
...
@@ -77,24 +94,3 @@ Futhermore, there are some low-level interfaces:
|Tango Database|MariaDB|http://localhost:3306|tango/tango|
|Archive Database|MariaDB|http://localhost:3307|tango/tango|
|Log Database|ElasticSearch|http://localhost:9200||
# Boot the station
Initially, all the devices controlling the station are down. To boot everything up, go to Jupyter (port 8888) and run:
```
# start boot device
boot.initialise()
boot.on()
# this should report as DevState.ON
boot.status()
# boot station
boot.initialise_station()
# wait until this reports the initialisation is done (or was stopped half way):
print(f"Still initialising: {boot.initialising_station_R}. Completeness: {boot.initialisation_progress_R}%. State: {boot.initialisation_status_R}")
```
Then, in Grafana (port 3000), you should see the devices reaching the ON state.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment