Aural Display

Just back from holidays, trying to get back into work. A couple of pressing things: 

• Update the InDetWebDisplay - separate style information into a separate stylesheet, ensure it works in Safari and Firefox, at least (see here).
• Try to introduce pan and zoom to this display.
• Look at Satoru's code for querying the DB, and marry this with Luca's interface.
• Fix warning messages in InDetCabling.

I've also discovered how to put a file in voice XML format on lxplus such that it can be telephoned (thanks to voxeo at vxml.org). This may be just a bit of fun just now, but I can see the possibilities for DCS monitoring. I'll try an xslt which creates an aural description of an event display to start with, to see what is possible.

Part timer

Had lots of time out to try to cover the kids holidays, but can report modest success in trying to read CoraCool cabling. There are still some wrinkles, but I think I'm ready to try it with the full database (the test database only has the four modules for M3/M4 running).

Today I'll look over Luca's web browser for DCS conditions and give detailed comments, and Make an XSLT for the 'NICOS' nightly xml to show to Alex Undrus as an example of what could be done.

There have been some recent problems with the clusterization package in the development nightlies due to the wrong tag being collected. Hopefully this will be fixed, I'll find out later this morning.

pm: Managed to make a stylesheet for the NICOS web page, and posted it here. Also extensively commented Luca's browser interface, which he has since updated, and provided comments on the documentation. This is quite extensive: 25 pages. The latest nightly had some problems again, finally works this evening.

e'en: Finally managed to read all the cabling data I need from the CoraCool database and insert them into the identifier map.

Good release?

I've had some time off, babysitting, but also been battling the database this week, trying to read the cabling. The original database I was working with turned out to be inconsistent, have to try again today.

Yesterday  was a bit frustrating because the release failed fairly fundamentally. How are we supposed to know this in a reasonably automated way so that we don't start to work with a broken release? I think I found a way, by interrogating the release web pages automatically; of course these pages are in (not very good) html, so I have to find a way to tidy them to good xml before interrogating. It turns out that 'xmllint' willl do this. I've added a tiddler on my notebook page.