[feature request] Feature/event labels

Bug #259552 reported by Jack Ireland on 2008-08-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jeff Stys

Bug Description

Keith has added a keyboard toggle - pressing the letter 'd' on the keyboard toggles a piece of information about the feature up on the screen. The information is a short piece of text. Currently, active region labels have the NOAA active region number as their toggle text. CACTus CMEs have their feature ID number i.e., 2003-10-05/093. IN general, it is probably a good idea to have unique identifiers as the toggle text. However, this may not always be the case. For example, GOES flares are not numbered sequentially as far as I know, and so there is no unique identifier available. For NOAA flares, a much more useful piece of toggle text would be the Flare class, e.g., M3.5, X1.2. Hence, in general, the toggle text should not be the feature/ID number, but should be something that is useful to the physicist, this being decided by us beforehand, on a case by case basis.

Keith Hughitt (keith-hughitt) wrote :

What would you suggest we use for each of the current event sources?

Keith Hughitt (keith-hughitt) wrote :

Legacy event marker system has been removed.

Changed in helioviewer.org:
status: New → Invalid
Jack Ireland (jack-ireland) wrote :

A new system has been created and deployed.

I think these F/E markers should have their label on by default.

Changed in helioviewer.org:
status: Invalid → Triaged
importance: Undecided → High
assignee: nobody → Jeff Stys (jstys-z)
Jeff Stys (jstys-z) wrote :

Feature/Event labels are now ON by default for new visitors.
Returning visitors with a userSettings-stored preference will have that value (if any) override the default.
Visitors arriving via a link containing a valid (boolean) value of the URL parameter "eventLabels" will see that value override both their userSettings-stored preference as well as the default. The URL parameter value is then retained in their userSettings for future use.

Changed in helioviewer.org:
status: Triaged → Fix Committed
Changed in helioviewer.org:
milestone: none → 2.4.0
Jack Ireland (jack-ireland) wrote :

I've been looking at the SPoCA labels and I think they should be changed. The key "frm_specificid" has a value, for example the big SPOCA active region in this image:


has a value "SPoCA_v1.0_AR_0000009026". This is a unique number. I think the FRM and FRM ID would be more useful to have displayed than the active region area. I suggest that the label be changed to

"SPoCA 9026"

where the SPoCA version number and leading zeros have been stripped away. SPoCA coronal holes can also be labeled in the same way. This way the user understands that the detection is from SPoCA, and that it has a catalog number of some kind.

This will also necissitate a change in how NOAA active regions are labeled. Instead of having just the active region number, I think the detection method should also include the "NOAA" FRM as well as the existing information. Therefore the labels will look something like:

NOAA 12345

where "ab" is "alpha beta" in greek letters.

Jeff Stys (jstys-z) wrote :

Fixed in Trunk revision 805.
Event cache is being re-built to reflect the change.

Jack Ireland (jack-ireland) wrote :

SPoCA coronal holes should also be labeled in the same way.

Jeff Stys (jstys-z) wrote :

Fixed in Trunk revision 806 (SPoCA CH labels).
Event cache is being re-built to reflect the change.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers