ID |
Date |
Author |
Topic |
Subject |
Text |
|
2560
|
21 Jul 2023 |
Gennaro Tortone | Forum | pull request for PostgreSQL support |
|
|
2563
|
28 Jul 2023 |
Stefan Ritt | Forum | pull request for PostgreSQL support | The compilation of midas was broken by the
last modification. The reason is that
|
|
2576
|
09 Aug 2023 |
Konstantin Olchanski | Forum | pull request for PostgreSQL support | > The compilation of midas was broken by the
last modification. The reason is that
> Pgsql *fPgsql = NULL;
|
|
423
|
05 Feb 2008 |
Denis Bilenko | Info | pymidas 0.6.0 released - python bindings for Midas | Hi!
I have released pymidas - Python binding |
|
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".
|
|
2499
|
01 May 2023 |
Giovanni Mazzitelli | 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".
|
|
737
|
26 Dec 2010 |
Konstantin Olchanski | Bug Report | race condition and deadlock between ODB lock and SYSMSG lock in cm_msg() | >
> The only remaining problem when running
my script is some kind of deadlock between |
|
2441
|
22 Oct 2022 |
Lars Martin | Suggestion | read_only odbxx? | I really like the concept of the odbxx interface.
I think it would be a nice feature if one
could have a read_only connection, e.g. by |
|
2443
|
24 Oct 2022 |
Stefan Ritt | Suggestion | read_only odbxx? | > I really like the concept of the odbxx interface.
> I think it would be a nice feature if one
could have a read_only connection, e.g. by |
|
2444
|
26 Oct 2022 |
Lars Martin | Suggestion | read_only odbxx? | > Having a "const midas::odb" probably does
not work (at least I would not know how to
implement that).
|
|
2445
|
29 Oct 2022 |
Stefan Ritt | Suggestion | read_only odbxx? | Ok, I implemented and committed that. Just
call
|
|
1701
|
23 Sep 2019 |
Frederik Wauters | Suggestion | recover daq and hardware safety. | We have encountered a safety issue with
our HPGe HV and it's midas frontend.
Turning off or changing HV unknowingly has |
|
1708
|
27 Sep 2019 |
Konstantin Olchanski | Suggestion | recover daq and hardware safety. | > We have encountered a safety issue with
our HPGe HV and it's midas frontend.
|
|
1712
|
28 Sep 2019 |
Frederik Wauters | Suggestion | recover daq and hardware safety. | Dear Konstantin,
So let me retract the term "safety issue" |
|
1715
|
29 Sep 2019 |
Konstantin Olchanski | Suggestion | recover daq and hardware safety. | >
> The issue occurs when e.g. one channel
can not be turned on and ramp for some temp/specific |
|