Tests against master 15.0.0-SNAPSHOT / INT / PRO

Legend

• works
• Further test in dry-run needed
• Tests ongoing
• Requires maintainance before release

bss-control-app

AW:

• compiles
• starts
• looks normal (signal data etc. missing, which is ok on DEV)
• Coupling:
  • Did not have resident ESR pattern at first, so I tried coupling SIS18 -> Cryring. Failed, but for an unexpected reason: The first coupling trim (SIS18 -> Cryring) succeeded, but then in the drive, LSA expected the coupled pattern to be an ESR pattern with ESR pattern signal (DISABLE_COUPLED_BEAM_REQUEST). As the pattern was instead a Cryring pattern that did not have that signal, we get an exception. Probably ok. ;-)
  • SIS18 -> ESR:
    • with a SIS18-HHD pattern, so not the proper beamline: worked
    • with a proper SIS18+beamline pattern: worked
      
  • ESR -> Cryring:
    • with a proper ESR+beamline pattern, and a non-proper Cryring+local injector pattern: worked
    • with a proper ESR+beamline pattern, and a proper Cryring+"Stummel" pattern: worked
• Decoupling:
  • SIS18 -> ESR:ESR -> Cryring: ESR -> Cryring:
    • with a SIS18-HHD pattern, so not the proper beamline: worked
    • with a proper SIS18+beamline pattern: worked
  • ESR -> Cryring:
    • with a proper ESR+beamline pattern, and a non-proper Cryring+local injector pattern: worked
    • with a proper ESR+beamline pattern, and a proper Cryring+"Stummel" pattern: worked

calibration-viewer-app

JF:

• compiles
• starts
• looks normal, Calibration curves are displayed, tested for SIS18, UNILAC, ESR

dave-app

JF:

• compiles
• starts
• looks normal, plotted data from an arbritrary device, here GUR4DT5 /CURRINFO#current 12-13h from today

CH:

• compiles
• starts
• Extracts data to chart, file system and WebDAV

device-automator-app

WG:

device-control-app

SH:

• compiles
• starts
• looks normal (devices not connected (devices only accessible in PRO), context selection ok, selection buttons work)
• device functionality: FESA (Status, Acquisition) tested (against INT/cmw-pro), driving test again against PRO
• device functionality: DeviceAccess device test (against INT/cmw-pro) failed, asked Vitaliy, other tests s. FESA devices

equipmonitor-app

BP:

(int 2020-05-26)

• Context selection
• Device selection
• Getting single values from devices
• Test an acquisition → postponed to dry-run as running pattern has to be available

equipstate-app

BP:

(int 2tier 2020-05-26)

• Load patterns and BPs
• Read Status of a device
• Read Setting of a device
• Not testing set

expert-cs-panic-app

AW:

• compiles
• starts
• looks normal
• Reset functionality: tested successfully again against INT

expert-digitizer-app

BP:

(int 2020-05-15)

• Compiles, starts and looks normal
• Lists Channels
• Traces and Sequence Events / Refernece trigger is shown

expert-hf-app

SH:

• compiles
• starts
• looks normal (devices not connected (devices only accessible in PRO), HF section selectable, )
• functionalities with device access to be done

JF:

• device subscriptions work (after fixing a bug with getting the VirtAcc from the Selector)

expert-profilegrid-app

expert-septum-app

JF:

• compiles
• starts
• looks normal
• functionality with device not tested (aks Klaudia, what can be safely tested??)

expert-storageringmode-app

BP:

(int 2020-05-15)

• Compiles, starts and looks normal
• Showing Patterns
• Updating patterns without disturbing usage
• Show Subchain progress
• Enable and perform skips
• Abort repetition
• Sort signal names in human friendly format (… 9 10 11)
• Enter and leave manipulation

expert-transmission-monitor-app

Zunächst aus Release rausnehmen, zu viele Anpassungen nötig, hier wird u.a. mit Cycles gearbeitet.

Neue Überarbeitung dann sinnvoll, wenn der Unliac als Maschine incl. Geräten in LSA drin ist.

expert-whats-running-app

AW:

• compiles
• starts
• looks normal: resident patterns displayed, flat line in all charts
• event visualization: worked against INT with snoop data

feedback-app

CH:

• Compiles
• Starts
• Display values correctly
• Improved automatic context selection to make it work in many more cases than before.
• Requires maintainces
  • Feedback handling is too strict
  • Automatic context selection doesn't work reliable when device is contained in more than one resident context.
  • App hasn't been migrated to JavaFX yet
  • Clarify if app should be improved or removed.

fixed-display-launcher-app

• Compiles
• Starts
• Looks normal
• Applications can be launched (on PRO).
• A known bug where the app looks odd when launched on the cluster could no longer be reproduced (no changes performed).

ionsource-app

JF:

• compiles
• starts
• works fine (subscriptions tested, no values set)

launcher-app

• Compiles
• Starts
• Looks normal
• Applications can be launched (which might not start on dev currently).

masp-app

CH

opticsviewer-app

JF:

• compiles
• starts
• looks normal, Optics are loaded and displayed

parammodi-app

AW:

• compiles
• starts
• RBAC dialog -> can be cancelled
• looks normal
• Trim on SCRATCH_AW_SIS18_FAST_HHD_...
  • single scalar trim
  • energy trim

HL:

• all tests performed look fine

proemi-app

profilegrid-app

Martin testet

psa-app

Martin testet

requester-app

AW:

• compiles
• starts
• looks normal
• requests:
  • switching from permanent request to no request and back -> played until not requested, then played again
  • triggering single request -> played once

scheduling-app

AW:

• compiles
• starts
• looks normal
• creating a new pattern
  • via name for SIS18
  • via beamline structure for SIS18
• trim created pattern
• ( / ) supply schedule
  • removing patterns
    • first try failed because some old patterns could not be made non-resident (apparently not compatible with make rules). Made those non-resident by setting trim temporarily to ignoreErrors=true.
    • after adding patterns (see below), removed one SIS pattern again
    • later removed one ESR pattern
      • Apparently something went wrong somewhere (maybe also in parallel usage of Scheduling App with Sergey), in the database:
        • three patterns (sis, esr, cryring) have users = are resident
        • sis pattern and cryring pattern are each in a pattern group
        • sis pattern and cryring pattern have exec conditions
        • only cryring pattern has dynamic signals
        • => exceptions when trying to read sis pattern because signals from exec condition are not found!!
        • => hacked DEV db directly (ewww) to make sure applications start again and made esr pattern non-resident with code snippet, but we need to find the cause.
          
        • => first guess: maybe it's because of the Signal cache, which we now "activated" (cache size > 0)?
        • Update 2020-05-26: Andreas and I have tried to reproduce this problem, but have not been successful yet. Everything seems to work fine...
        • Update 2020-05-28: Still could not reproduce, leaving it for Dry Run.
  • adding patterns:
    • after removing all patterns (see above):
    • 2 new SIS patterns and one existing Cryring pattern added successfully
      • Cryring pattern (Storage Ring Mode) took very long to make resident (1:40 min)
    • later added one new ESR pattern
• duplicate pattern
  • was originally broken, but has been fixed by S. Müller

screenshot-app

BP:

• Works (int 2020-05-26)

sequencer-app

JF:

• Compiles (after changes done by Stefan from last week)
• removed hardcoded pro/3tier to be able to also test on INT
• Starts
• Seems to work okay, run 2 sequences FecStatusTest and FecVersion test with GHHTQD11, output is ok

top-app

CH

• Compiles
• Starts
• Seems to work okay
• Changed dependency from common-context-widget to common-widget

webviewer-app

CH

• Compiles
• Starts
• Displays basic websites correctly
• Crashes on almost every modern website (https://github.com/javafxports/openjdk-jfx/issues/316)

FRS

frs-drivestat-app

Fabio: "Compiles, starts and looks normal"

frs-fmgskal-app

Fabio: "Compiles, starts and looks normal"

frs-magstat-app

Fabio: "Compiles, starts and looks normal"

frs-overview-app

Fabio: "Compiles, starts and looks normal"

frs-devconf-app

Fabio: "Compiles, starts and looks normal"

benno-app (marked as 'do not release')

coat-* (marked as 'do not release')

ionsource-mcs-app (marked as 'do not release')

japlato-app (marked as 'do not release')

-- AnnekeWalter - 12 May 2020