| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2373
|
24 Mar 2022 |
Konstantin Olchanski | Bug Report | data missing in runXXXXXX.mid | > One idea: we should have a look at mlogger::close_channels().
> There the SYSTEM buffer is emptied through
the cm_yield() call.
|
|
|
2375
|
25 Mar 2022 |
Marius Koeppel | Bug Report | Writting MIDAS Events via FPGAs | I finally found the problem why the readout
stops after a run transition.
|
|
|
2412
|
20 Jun 2022 |
jianrun | Bug Report | Error in "midas/src/mana.cxx" | Dear Midas developers,
When we are running the examples in $MIDASSYS/examples/experiment/, |
|
|
2414
|
25 Jun 2022 |
Joseph McKenna | Bug Report | RPC timeout for manalyzer over network |
In ALPHA, I get RPC timeouts running a (reasonably |
|
|
2415
|
18 Jul 2022 |
Konstantin Olchanski | Bug Report | RPC timeout for manalyzer over network | > In ALPHA, I get RPC timeouts running a (reasonably
heavy) analyzer on a remote machine (connected
directly via a ~30 meter 10Gbe Ethernet cable) |
|
|
2424
|
15 Aug 2022 |
Zaher Salman | Bug Report | firefox hangs due to mhistory | Firefox is hanging/becoming unresponsive due
to javascript code. After stopping the script
manually to get firefox back in control I |
|
|
2425
|
15 Aug 2022 |
Stefan Ritt | Bug Report | firefox hangs due to mhistory | > Firefox is hanging/becoming unresponsive
due to javascript code. After stopping the
script manually to get firefox back in control |
|
|
2426
|
16 Aug 2022 |
Zaher Salman | Bug Report | firefox hangs due to mhistory | > > Firefox is hanging/becoming unresponsive
due to javascript code. After stopping the
script manually to get firefox back in control |
|
|
2427
|
16 Aug 2022 |
Zaher Salman | Bug Report | firefox hangs due to mhistory | I found the bug. The problem is triggered
by changing the firefox window. This calls
a function that is supposed to change the |
|
|
2428
|
16 Aug 2022 |
Konstantin Olchanski | Bug Report | firefox hangs due to mhistory | > > > Firefox is hanging/becoming unresponsive
due to javascript code.
>
|
|
|
2429
|
17 Aug 2022 |
Stefan Ritt | Bug Report | firefox hangs due to mhistory | The problem lies in your function mhistory_init_one()
in Mudas.js:1965. You can only call "new
MhistoryGraph(e)" with an element "e" which |
|
|
2430
|
17 Aug 2022 |
Zaher Salman | Bug Report | firefox hangs due to mhistory | > The problem lies in your function mhistory_init_one()
in Mudas.js:1965. You can only call "new
MhistoryGraph(e)" with an element "e" which |
|
|
Draft
|
17 Aug 2022 |
Stefan Ritt | Bug Report | firefox hangs due to mhistory | > Some of my histories are placed in an IFrame
object. I eventually realized that my code
fails
|
|
|
2432
|
17 Aug 2022 |
Stefan Ritt | Bug Report | firefox hangs due to mhistory | > Some of my histories are placed in an IFrame
object. I eventually realized that my code
fails
|
|
|
2493
|
01 May 2023 |
Giovanni Mazzitelli | Bug Report | python issue with mathplot lib vs odb query | Ciao,
we have a very strange issue with python
lib with client.odb_get("/") function
|
|
|
2494
|
01 May 2023 |
Ben Smith | Bug Report | python issue with mathplot lib vs odb query | > it seams that there is a difference between
the to way of use the code, and that
> is sufficient the call to matplotlib to |
|
|
Draft
|
01 May 2023 |
Giovanni Mazzitelli | Bug Report | python issue with mathplot lib vs odb query | > > it seams that there is a difference between
the to way of use the code, and that
> > is sufficient the call to matplotlib |
|
|
2496
|
01 May 2023 |
Giovanni Mazzitelli | Bug Report | python issue with mathplot lib vs odb query | > > it seams that there is a difference between
the to way of use the code, and that
> > is sufficient the call to matplotlib |
|
|
2497
|
01 May 2023 |
Ben Smith | Bug Report | python issue with mathplot lib vs odb query | Looks like a localisation issue. Your floats
are formatted as "6,6584e+01", whereas the
JSON decoder expects "6.6584e+01".
|
|
|
2498
|
01 May 2023 |
Ben Smith | Bug Report | python issue with mathplot lib vs odb query | > Looks like a localisation issue. Your floats
are formatted as "6,6584e+01", whereas the
JSON decoder expects "6.6584e+01".
|
|