gui issueshttps://gitlab.elettra.eu/groups/cs/gui/-/issues2021-10-27T12:51:27Zhttps://gitlab.elettra.eu/cs/gui/i0mapmon-topo/-/issues/6Fix left scale when first update is invalid2021-10-27T12:51:27ZGiacomo StrangolinoFix left scale when first update is invalidLeft scale is messed up when the first update is not valid and then valid data is deliveredLeft scale is messed up when the first update is not valid and then valid data is deliveredhttps://gitlab.elettra.eu/cs/gui/i0mapmon-topo/-/issues/5Messaggio di errore:2021-10-19T14:20:22ZMichele ManfreddaMessaggio di errore:1) Nel TOPO, quando il numero di Lambda e di Pesi non coincide, viene visualizzato un messaggio di errore complicato.
Possiamo metterne uno più significativo? Del tipo:
"Server error: the numbers of specified wavelengths and of weights d...1) Nel TOPO, quando il numero di Lambda e di Pesi non coincide, viene visualizzato un messaggio di errore complicato.
Possiamo metterne uno più significativo? Del tipo:
"Server error: the numbers of specified wavelengths and of weights do not match."
![image](/uploads/0ff49b6d262a8288d2fcb70148b00c85/image.png)
2) Di fatto, anche quando il numero di lunghezze d'onda e di pesi corrisponde, per 2 o 3 frame, persiste l'errore sul server.
Come riprodurre l'errore:
aprire topologico e monitor assieme. Dal "monitor" cambiare lambda e/o pesi ed osservare il comportamento nel topologico.
Software avviabili dal browser padres ufficiale:
![image](/uploads/3eb7923509ad507f0e21dc453ed624ed/image.png)
@graziano.scalamera, tu puoi suggerire qualcosa in proposito?
Graziehttps://gitlab.elettra.eu/cs/gui/i0mapmon-topo/-/issues/4forzare valori negativi a zero2021-10-27T12:54:26ZGiacomo Strangolinoforzare valori negativi a zeroEvitare le barre all'indietroEvitare le barre all'indietrohttps://gitlab.elettra.eu/cs/gui/i0mapmon-topo/-/issues/3TOPO Crash quando vengono cambiate le lambda nel "IOM"2021-10-27T12:54:42ZMichele ManfreddaTOPO Crash quando vengono cambiate le lambda nel "IOM"Se aggiungo una o più lambda (dal topo), il mono muore. Questo caso deve essere gestito.
Se invece le tolgo, non sembra dar problemi
Se non ce ne sono di specificate, compare un error message complicato.
Lo possiamo lasciare, a patto ...Se aggiungo una o più lambda (dal topo), il mono muore. Questo caso deve essere gestito.
Se invece le tolgo, non sembra dar problemi
Se non ce ne sono di specificate, compare un error message complicato.
Lo possiamo lasciare, a patto di aggiungere uno "hint user friendly", tipo "Check that at least one wavelength and its weight are given in the server".https://gitlab.elettra.eu/cs/gui/i0mapmon-topo/-/issues/2Display lambda2021-10-11T14:54:10ZMichele ManfreddaDisplay lambdaAllo startup, non c'è nessuna lambda selezionata.
![image](/uploads/82cbff1e9277324ec4986d455353368f/image.png)
Bisogna
1) Controllare che, all'avvio, siano selezionate tutte le lambda disponibili
2) Verificare il behavior del "TOPO" q...Allo startup, non c'è nessuna lambda selezionata.
![image](/uploads/82cbff1e9277324ec4986d455353368f/image.png)
Bisogna
1) Controllare che, all'avvio, siano selezionate tutte le lambda disponibili
2) Verificare il behavior del "TOPO" quando nel "IOM" aggiungo/tolgo altre lambda. L'ideale sarebbe che:
- all'avvio selezionasse tutte le lambda disponibili
- se vengono ridotte o aumentate le lambda non desse errore (vedi altro issue)https://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/9Legend lambda proliferation2021-10-08T09:41:22ZMichele ManfreddaLegend lambda proliferationIl registro delle legende (e forse anche dei tracciati con reltivi colori) non viene aggiornato correttamente
Per riprodurre il problema fare così
avviare felmon
wavelengths, scrivere "60"
apply (wavelengths)
weights: "0.5"
apply (we...Il registro delle legende (e forse anche dei tracciati con reltivi colori) non viene aggiornato correttamente
Per riprodurre il problema fare così
avviare felmon
wavelengths, scrivere "60"
apply (wavelengths)
weights: "0.5"
apply (weights: )
plot
wavelengths, aggiungere ", 30"
apply (wavelengths)
weights: ", 0.4"
apply (weights)
plot
e si ottiene
![image](/uploads/194be69ce0fd6d08e8efa43095d23e4c/image.png)https://gitlab.elettra.eu/cs/gui/alarm-ng/-/issues/10Add helper application2021-05-28T12:17:59ZGraziano ScalameraAdd helper applicationAttribute names inside values field in the info box, could be associated to helper applications to be opened with mouse right click.Attribute names inside values field in the info box, could be associated to helper applications to be opened with mouse right click.https://gitlab.elettra.eu/cs/gui/alarm-ng/-/issues/9Add history tab2021-05-28T12:14:23ZGraziano ScalameraAdd history tab
A tab with history should be added.
It should display 3 columns: date, name, state.
An example of query could be the following:
```
SELECT asd.data_time as date,ac.att_name as name,
COALESCE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPL...
A tab with history should be added.
It should display 3 columns: date, name, state.
An example of query could be the following:
```
SELECT asd.data_time as date,ac.att_name as name,
COALESCE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(asd.value_r,'0','NORMAL'),'1','ALARM UNACK'),'2','ALARM ACKED'),'3','NORMAL UNACK'),'4','SHELVED'),'5','SUPPRESSED BY DESIGN'),'6','DISABLED'),'7','ERROR'),aed.error_desc) as state
FROM att_scalar_devenum_ro asd
JOIN att_conf ac ON asd.att_conf_id=ac.att_conf_id
LEFT OUTER JOIN att_error_desc aed ON aed.att_error_desc_id=asd.att_error_desc_id
WHERE asd.att_conf_id in (SELECT att_conf_id FROM att_conf WHERE att_name LIKE '%alarm/fermi/climate/%' OR att_name LIKE '%alarm/fermi/diagnostics/%')
AND asd.data_time > NOW() - INTERVAL 1 DAY and asd.data_time <= NOW()
ORDER BY asd.data_time DESC;
```
where the REPLACE(REPLACE...) is used to replace [0-7] enum values with the labels
[NORMAL','ALARM UNACK','ALARM ACKED','NORMAL UNACK','SHELVED','SUPPRESSED BY DESIGN','DISABLED','ERROR'],
JOIN with att_conf is used to replace att_conf_id with att_name from att_conf,
LEFT OUTER JOIN is used to replace att_error_desc_id with error_desc,
SELECT att_conf_id in the WHERE condition is used to retrieve all alarms belonging to the listed handlers. Attention should be paid to handler names, whether they are FQDN or not.
It should be possible to filter history by both name, state and date.
Parameters to access DataBase could be saved in a free property.https://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/8change window title (from the browser)2021-10-11T14:48:44ZMichele Manfreddachange window title (from the browser)METTERE
per i0mapmon => "INTEMPO - Monitor (FEL1)", e similmente con FEL2
per il topologico => "INTEMPO - Photon Map (FEL1)", e similmente con FEL2METTERE
per i0mapmon => "INTEMPO - Monitor (FEL1)", e similmente con FEL2
per il topologico => "INTEMPO - Photon Map (FEL1)", e similmente con FEL2https://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/7configure plot button in another row2021-06-22T09:55:49ZGiacomo Strangolinoconfigure plot button in another rowAdd a layout row for configure plot (aligned with the new threshold r/w)Add a layout row for configure plot (aligned with the new threshold r/w)https://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/6Read the Label attribute instead of the Name in Y combo box2021-06-22T09:55:59ZGiacomo StrangolinoRead the Label attribute instead of the Name in Y combo boxY combobox names have to be fetched from Label instead of NameY combobox names have to be fetched from Label instead of Namehttps://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/5Y Log scale2021-06-22T09:56:05ZGiacomo StrangolinoY Log scaleIn configure plot add option for log scaleIn configure plot add option for log scalehttps://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/4add ChargeRelThreshold R/W2021-09-16T16:09:41ZGiacomo Strangolinoadd ChargeRelThreshold R/Wsotto wavelengths aggiungere lettura + scrittura att: ChargeRelThresholdsotto wavelengths aggiungere lettura + scrittura att: ChargeRelThresholdhttps://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/3curve colors2021-06-22T12:51:22ZGiacomo Strangolinocurve colorsSame colors as topo for lambdasSame colors as topo for lambdashttps://gitlab.elettra.eu/cs/gui/i0mapmon/-/issues/2lambda legend not correctly updated2021-06-22T09:56:45ZGiacomo Strangolinolambda legend not correctly updatedmodify lambdas --> plot legend not correctmodify lambdas --> plot legend not correctGiacomo StrangolinoGiacomo Strangolinohttps://gitlab.elettra.eu/cs/gui/i0mapmon-topo/-/issues/1Plot scales compromised after Log Scale switch2021-10-11T14:19:23ZGiacomo StrangolinoPlot scales compromised after Log Scale switchCheck plots after LOG SCALE is enabled: TXF no more between 0 and 1 after log scale switch.Check plots after LOG SCALE is enabled: TXF no more between 0 and 1 after log scale switch.Giacomo StrangolinoGiacomo Strangolinohttps://gitlab.elettra.eu/cs/gui/mscr/-/issues/1polrimater2021-04-23T11:37:24ZClaudio Scafuriclaudio.scafuri@elettra.eupolrimaterpuo' mancare anche il polarimetro #1. Controllare indipendentementepuo' mancare anche il polarimetro #1. Controllare indipendentementehttps://gitlab.elettra.eu/cs/gui/tiptiltgcs/-/issues/1ta titles2021-03-25T09:22:29ZClaudio Scafuriclaudio.scafuri@elettra.euta titlespermetter di rinominare i tab:
X Y -> MAG tiptilt
F N -> RIXS tiptiltpermetter di rinominare i tab:
X Y -> MAG tiptilt
F N -> RIXS tiptiltClaudio Scafuriclaudio.scafuri@elettra.euClaudio Scafuriclaudio.scafuri@elettra.euhttps://gitlab.elettra.eu/cs/gui/alarm-ng/-/issues/8Handle different alarm-handlers list2021-04-28T14:16:51ZGraziano ScalameraHandle different alarm-handlers listActually list of alarm-handlers to be managed by the GUI is saved in the AlarmHandler/DeviceList free property. Different property names should be supported and (optionally? keep DeviceList as default?) passed as command line parameter.Actually list of alarm-handlers to be managed by the GUI is saved in the AlarmHandler/DeviceList free property. Different property names should be supported and (optionally? keep DeviceList as default?) passed as command line parameter.https://gitlab.elettra.eu/cs/gui/alarm-ng/-/issues/7Handle url2021-04-28T12:20:40ZGraziano ScalameraHandle urlUrl field has been moved from the message field to a dedicated field. So it is no more present in the alarm attribute, but it has to be retrieved with the GetAlarmInfo command. To have in response only the url field, "alarm_name,url" has...Url field has been moved from the message field to a dedicated field. So it is no more present in the alarm attribute, but it has to be retrieved with the GetAlarmInfo command. To have in response only the url field, "alarm_name,url" has to be passed as command argin