|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
28 Aug 2019, Nick Hastings, Forum, History plot problems for frontend with multiple indicies
|
28 Aug 2019, Stefan Ritt, Forum, History plot problems for frontend with multiple indicies
|
28 Aug 2019, Nick Hastings, Forum, History plot problems for frontend with multiple indicies
|
28 Aug 2019, lcp, Forum, History plot problems for frontend with multiple indicies
|
16 Sep 2019, Konstantin Olchanski, Forum, History plot problems for frontend with multiple indicies
|
16 Sep 2019, Konstantin Olchanski, Forum, History plot problems for frontend with multiple indicies
|
29 Aug 2019, Ben Smith, Forum, History plot problems for frontend with multiple indicies
|
01 Sep 2019, Nick Hastings, Forum, History plot problems for frontend with multiple indicies
|
16 Sep 2019, Konstantin Olchanski, Forum, History plot problems for frontend with multiple indicies
|
16 Sep 2019, Nick Hastings, Forum, History plot problems for frontend with multiple indicies
|
17 Sep 2019, Konstantin Olchanski, Forum, History plot problems for frontend with multiple indicies
|
18 Sep 2019, Nick Hastings, Forum, History plot problems for frontend with multiple indicies
|
27 Sep 2019, Konstantin Olchanski, Forum, History plot problems for frontend with multiple indicies
|
24 Aug 2020, Konstantin Olchanski, Forum, History plot problems for frontend with multiple indicies
|
|
Message ID: 1693
Entry time: 16 Sep 2019
In reply to: 1692
Reply to this: 1696
|
Author: |
Nick Hastings |
Topic: |
Forum |
Subject: |
History plot problems for frontend with multiple indicies |
|
|
Hi Konstantin,
thanks for your reply.
> > thanks for your reply. I can confirm that your suggested workaround does indeed
> > make the problem dissapear.
> > I guess this issue hasn't been seen at T2K since we use MYSQL for the history.
>
> I think you found the source of the problem, confused event id assignments. To confirm,
> can you email me (or post here) the output of odbedit "ls -l /History/Events".
Sorry, do you want this for after I've applied the fix suggested by Ben or with the original code
that I posted.
With the original code it only shows one fe even though both are running:
[local:e666:S]History>ls -l /History/Events
Key name Type #Val Size Last Opn Mode Value
---------------------------------------------------------------------------
1 STRING 1 10 2m 0 RWD FeDummy02
0 STRING 1 16 2m 0 RWD Run transitions
[local:e666:S]History> scl
Name Host
mhttpd localhost
fedummy01 localhost
fedummy02 localhost
ODBEdit localhost
Logger localhost
[local:e666:S]History>ls "/History/Display/Default/Dummy/
Timescale 1h
Zero ylow n
Show run markers y
Show values y
Sort Vars n
Log axis n
Minimum 0
Maximum 0
Variables
FeDummy01:Data
FeDummy02:Data
Label
Colour
#00AAFF
#FF9000
Factor
0
0
Offset
0
0
Buttons
10m
1h
3h
12h
24h
3d
7d
Formula
Show old vars n
> If that's the problem, you can avoid it completely by switching to a history storage method
> that does not rely on magic mapping between equipment names and numeric event id's:
> try the "FILE" method (set odb /Logger/History/FILE/Active to "y", restart the logger) or
> the "MYSQL" method (you will need to setup a mysql database). You tell mhttpd and mhist which
> history data to read by setting ODB /History/LoggerHistoryChannel to one of the channel names
> from /logger/history/, restart mhttpd. (mhttpd and mhist used to print a message "reading history
> data from channel XXX", but somebody removed this message).
Using the orginal code I posted and switching from MIDAS history to FILE history did not seem to
change the random behaviour in the history plots.
Regards,
Nick. |