HEK F/E flares and other events that are co-spatial

Bug #1180816 reported by Jack Ireland on 2013-05-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Helioviewer.org
Critical
Jeff Stys

Bug Description

The Flare detective algorithm works on multiple AIA wavelengths and often reports flares in multiple wavelengths in closely overlapping times and locations. Human detectors will often do the same; for example

http://hek.delphi.nascom.nasa.gov/?date=2012-05-12T02:47:27.500Z&imageScale=4.8408818&centerX=28.228406536198733&centerY=108.43574957735017&imageLayers=%5BSDO,AIA,AIA,193,1,100%5D,%5BSDO,AIA,AIA,171,1,54%5D&eventLayers=%5BCE,all,1%5D,%5BER,all,1%5D,%5BFI,all,1%5D,%5BFA,all,1%5D,%5BFE,all,1%5D,%5BFL,all,1%5D,%5BLP,all,1%5D,%5BSG,all,1%5D&eventLabels=true

This particular example is interesting because the human observer has also detected multiple filament eruptions at what I assume are approximately the same time and place.

So, how can multiple F/Es detected by the same FRM in more or less the same location be shown? This question helps define the criteria. First, there have to be multiple (two or more) F/Es detected by a FRM. Next, they must be in approximately the same location. Approximate could be taken to mean "so close spatially that you can't click on any individual one at a reasonable zoom level". This will have to be defined. Instead of putting multiple indistingishable F/E markers on screen, these could be repalced by a single F/E marker with a small number appended to it indicating the number of F/Es at this location. The number would appear in a small red circle on the (top right of? top left?) F/E marker. The F/E label would have to change to something generic to the F/E class, not to any particular F/E - perhaps just the F/E name itself, or its plural. On clicking on it, the relevant number of F/E pop-up windows would appear. Each F/E pop-up would have to have something to distinguish it from the others.

In the case of the Flare Detective, the obs_channelid is sufficient, so the title for the pop-up window would be something like "FL (131) 870 erg/cm/cm/s".

In the case of the Filament Eruption, the example in this link

http://hek.delphi.nascom.nasa.gov/?date=2012-05-10T02:47:27.500Z&imageScale=1.2102204&centerX=-121.54641467160646&centerY=-124.93510935089722&imageLayers=%5BSDO,AIA,AIA,193,1,100%5D,%5BSDO,AIA,AIA,171,1,54%5D&eventLayers=%5BAR,SPoCA,1%5D,%5BCE,all,1%5D,%5BEF,all,1%5D,%5BER,all,1%5D,%5BFI,all,1%5D,%5BFA,all,1%5D,%5BFE,all,1%5D,%5BFL,all,1%5D,%5BLP,all,1%5D,%5BSG,all,1%5D&eventLabels=true

shows five Filament Eruption events. Closer inspection shows that 4 of the 5 are events are seen in individual SDO image wavebands, and the 5th is a meta-event that apparently collects the 4 events together. For this one, frm_identifier = 'MetaEventCreator'. Perhaps when frm_identifier is equal to
'MetaEventCreator' and the frm_humanflag is True, we should only report this meta event.

Changed in helioviewer.org:
importance: Undecided → Critical
status: New → Triaged
Changed in helioviewer.org:
assignee: nobody → Jeff Stys (jstys-z)
milestone: none → 2.4.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers