SCONE issueshttps://gitlab.cern.ch/scouting-demonstrator/scone/-/issues2024-02-28T12:04:43+01:00https://gitlab.cern.ch/scouting-demonstrator/scone/-/issues/50Ability to set destination IP:port for scouting pipelines per subsystem2024-02-28T12:04:43+01:00Dinyar Rabadydinyar.rabady@cern.chAbility to set destination IP:port for scouting pipelines per subsystemHi @rardino,
it just struck me that we won't want a static mapping from DAQ streams to RUs, they should be selected by the FM dynamically. To this end I think it would be good if SCONE provided an interface to set the destination IP:por...Hi @rardino,
it just struck me that we won't want a static mapping from DAQ streams to RUs, they should be selected by the FM dynamically. To this end I think it would be good if SCONE provided an interface to set the destination IP:port in a reasonably elegant way. It's probably not critical right now, but will be important eventually (because I think machines at P5 are given dynamic IPs that can change over time.. ).
I was thinking of an interface approximately like
```python
requests.post('http://localhost:8080/v2/vcu128_ugmtbmtf/0/configure', json={"enabled_system":["ugmt","bmtf"], "l1ds_pipelines": {"ugmt":{"dest_ip": "192.168.1.1", "dest_port":"2000"}, "bmtf":{...}}})
```
What do you think?Rocco ArdinoRocco Ardinohttps://gitlab.cern.ch/scouting-demonstrator/scone/-/issues/34Update README2022-08-25T18:16:15+02:00Thomas Owen JamesUpdate READMEhttps://gitlab.cern.ch/scouting-demonstrator/scone/-/issues/30Clean up code2022-05-04T10:32:17+02:00Dinyar Rabadydinyar.rabady@cern.chClean up codehttps://gitlab.cern.ch/scouting-demonstrator/scone/-/issues/9Refactor code to use exceptions2021-03-03T19:21:24+01:00Dinyar Rabadydinyar.rabady@cern.chRefactor code to use exceptions