Fer

Linux sysadmin. Wrote the @lhcstatus2 bot (current state: held together by string and duct tape).

[Fer @treffer_]

The lhcstatus2 json output is up: https://t.co/pNAaMtq5Mo

[Fer @treffer_]

@Rongkun_WANG @lhcstatus2 Post mortems are available during ramp down and cycling. Vistars will show an older PM for a few minutes after beam dump before it updates. The old PM gets posted if it's recent and contains a comment. That's also why the bot sometimes posts two PMs in succession.

[Fer @treffer_]

@Rongkun_WANG @lhcstatus2 The script behind @lhcstatus2 is still the old one. The json output is mostly new. It's missing some functionality I had intended to add, and can't quite replace the bot. But since there's some interest, I'll let it go live as is.

[Fer @treffer_]

@Rongkun_WANG @lhcstatus2 It's not updating yet, but you can check out https://t.co/nHtY8xTVQG for the api and be ready when it does go live.

[Fer @treffer_]

You can also find @lhcstatus2 on Mastodon: https://t.co/CdHpvVLeqa. I'm still planning to make a live json dump of its internal state available for anyone interested. It should be up for the 2023 run, unless there are big changes to Vistars.

[Fer @treffer_]

@lhcstatus2 Too bad the OCR choked on the 40fb⁻¹. Maybe it's the bot's way of telling me it needed a break from tracking all that luminosity and stable beam time.

[Fer @treffer_]

@bowskeyes @lhcstatus2 It's at [email protected]

[Fer @treffer_]

@ssyreeni @lhcstatus2 See also https://t.co/rQ0Ny8IvaL, it's all image based. In the end the OCR solution adds a few milliseconds to all the other delays. But there's some data less accessible to OCR etc, which might be fun to play around with, if it were made available in machine-readable form.

[Fer @treffer_]

@ssyreeni @lhcstatus2 Back when I started writing @lhcstatus2, I made an effort to find text output from CERN, to no avail. Predecessor @lhcstatus was also notouriously ocr based, and its creator worked at CERN. And this https://t.co/gdzaGBmbjU probably also uses ocr (for the comments at least).

[Fer @treffer_]

@ssyreeni @lhcstatus2 All times are local to CERN, so UTC+2 at the moment.

@lhcstatus2 mostly does ocr of the Vistars pages. It can't interpret the variety of ways in which operators write times.

If you want to use its output in some automated way, I plan to add a raw json dump in the near future.