SPCDIS User Annotation Use Case 5

Printer-friendly version

Short description:

A user asks about a problem/event with one image, and gets a reply relating the problem/event to an NCAR-generated data product used to generate that image.

NOTE: Currently, there are no bug correction reports released by ACOS. Therefore, this is a hypothetical situation for CHIP. However, it demonstrates identification of an internal data product as being relevant to a user request, as opposed to one externally generated.

Scenario:

A user Alice is looking at intensity pictures for 10d242, and notices the entry 20100830.223717.chp.hsc.fts is assigned an ‘UGLY’ rating. Curious about why this is, Alice submits the following request: “Are there any known events which caused this image to be assigned an ‘UGLY’ rating?” Following this, a link is made from Alice’s clarification request to the data product.

Next, an alternate user Bob (affiliated with ACOS) replies through establishing a link from a piece of data representing the statement:

BUG CORRECTION: Calculation in “Flatten” routine corrected.

To two places:

  1. Alice’s request
  2. The “Flatten” instance used to used to generate the target image.

Additionally, through this reply, it could make sense for Bob to make a link to any data depending on the “Flatten” routine prior to the bug fix. However, this could result in links being asserted for virtually all data products ever generated by the CHIP pipeline. As an alternative, Bob’s reply should enable semantic inference of the fact that all these data products may be affected.

Scenario Aftermath:

For any future users (including Alice) looking at the provenance for 20100830.223717.chp.hsc.fts, a flag will be raised that the image quality may have been impacted by a bug in CHIP, based on the information provided by Bob. Additionally, for data products dependent on “Flatten” execution instances generated before the bug fix, a flag should be raised (based on the above inference).