Project

General

Profile

Feature #83

e-log improvement

Added by Blondel, Alain almost 12 years ago. Updated over 9 years ago.

Status:
Open
Priority:
Normal
Assignee:
Taylor, Ian
Category:
Documentation
Start date:
06 October 2010
Due date:
05 February 2013 (over 9 years late)
% Done:

0%

Estimated time:
6.00 h

Description

This is related to the entry number 78 but I think goes deeper to solve it. It is quite easy to understand why our e-log is nearly unuseable: we have 20 categories and 18 types, 360 possibilities. MICE dont know how to count this far, I certainly cant.

I have uploaded a few slides describing another application of the e-log, as per the NA61 experiment at CERN, and even added the contacts people who have designed the system. I think we should limit the number of streams (i.e. elogs) to 10 or less.

One should not be afraid of edits, only people in the control room should be able to write in the editable elog which is shift summaries.

Question: can the DAQ or EPICS send messages to the elog?


Files

NA61-MICE-logbook.ppt (370 KB) NA61-MICE-logbook.ppt Blondel, Alain, 06 October 2010 15:32

Related issues

Related to Operations - Feature #1542: Web whiteboard improvementOpenBoyd, Steven08 August 201421 January 2015

Actions
Has duplicate Operations - Feature #78: implement formal shift reportsClosed05 October 2010

Actions
#1

Updated by Blondel, Alain almost 12 years ago

contact people are
Mateusz Piwek
Andras Laszlo

#2

Updated by Tunnell, Christopher almost 11 years ago

  • Category set to Documentation
  • Assignee set to MOM, Mice Operations Manager
#3

Updated by Coney, Linda almost 10 years ago

  • Due date changed from 15 January 2011 to 05 February 2013
  • Assignee changed from MOM, Mice Operations Manager to Nebrensky, Henry

Changed assignee to Henry who will implement changes to elog by Feb 2013.

Henry - see above ideas from Alain who originated this topic.

#4

Updated by Nebrensky, Henry almost 10 years ago

Changes proposed at CM34 and ensuing discussion are:

Since I don't want to risk breaking the real production eLog which already contains a lot of data, I'm sticking with the two existing attributes called Type and Category but tidying up their options.

Types:

Routine
Warning
Error
Problem Fixed
Reference
Calibration
Other
Test (?)
Safety (?)

Also "Configuration" (change) should be a Type.

Categories:

Hall infrastructure
Shift
Target
Beamline
Cryogenics
LH2
RF
SC Magnets
Detectors and DAQ
Controls and Monitoring
Computing/Grid
Consumables
Control Room
Target R78
Other

Not sure about:

Cooling Channel
Environment
Machine Physics
MOM daily summary (?)
PPS
R9 Testing (?)
Safety
Services

Notebooks

Create new notebooks for:
  • LH2 system and testing (done)
  • R9 activities
  • MOM walkabout - this could have the detailed one entry per item format shown in the slides Alain provided above (slide 2)
  • Automated end-of-run entries

Feedback / comments

Having "Warning" and "Error" is superfluous - just have "Issue". Someone searching won't know which a problem was reported as

  • Personally I don't see these Types (also "Routine") as useful search modifiers in any case; it's more about flagging up the urgency of the issue
  • I'd prefer to avoid "Issue" as that's already a MICEmine term (similarly "Problem" vs "Problem Fixed" may clash when doing a visual grep)
  • I'm open to aggregating them if we can find the right synonym (or maybe make "Problem Fixed" into "Solution"?)

Have "Warning" and "Error" as sub-options of "Issue"

  • I'm worried that this is too drastic a change for the existing notebook - we can't risk breaking it.
  • I've considered making the existing "MICE Log" notebook read only and starting a new one with a more appropriate configuration, but this will cause major confusion and also needs weblinks and bookmarks updating all over the place

Must encourage people to make entries - their reactions to events must include thinking to put this in the eLog

  • If only we knew how
  • Applies also to activities OTHER than full runs of the experiment

Make more short entries during shift, so that people off-site can follow progress - don't leave until one big entry at end

  • Shifter training issue
  • Also avoids losing write-up so far in a computer glitch!
#5

Updated by Nebrensky, Henry almost 10 years ago

  • Estimated time set to 6.00 h

I've made the type/category changes described above (they can be revisited if needed).

Notebooks and other changes need further discussion.

#6

Updated by Nebrensky, Henry almost 10 years ago

  • Assignee changed from Nebrensky, Henry to Taylor, Ian

We've agreed that Ian Taylor will take over the eLog administration.

N.B. I've had a request from Roy Preece for an R9 AFC tests notebook - for Monday p.m.!

#7

Updated by Nebrensky, Henry over 9 years ago

For reference:

  • It was agreed at a Collaboration Meeting a long, long time ago that the eLog (now the "MICE log" notebook) should not allow entries to be changed after submission. It would be open to make entries from outside RAL.
  • Corrections and updates can be associated with an existing entry using the "Reply" feature.
  • For the recently-added R9 notebook, entries may be edited for up to 48hrs, but not deleted.
  • This is a deliberate feature to allow building up multiple walkabout checks into a single entry, to make trends easier to see.

Also available in: Atom PDF