| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2347
|
16 Feb 2022 |
Marius Koeppel | Bug Report | Writting MIDAS Events via FPGAs | I just came back to this and started to use
the dummy frontend.
Unfortunately, I have a problem during run |
|
|
2352
|
07 Mar 2022 |
Marius Koeppel | Bug Report | Writting MIDAS Events via FPGAs | > This problem has (likely) been fixed in
the current version. Please pull develop
and try again. Was a recursive call to the |
|
|
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.
|
|
|
2476
|
27 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | Hi all,
> I agree, I think we can safely bump the |
|
|
2480
|
27 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | > This is change is wrong. As I wrote, ODB
is not 64-bit clean and it is not 32-bit
clean. We think is is 31-bit clean, so maximum |
|
|
2485
|
28 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | > my vote is to bump the ODB size limit to
1999*1000*1000 (not quite 2GB). but this
needs to be tested. especially save and restore |
|
|
2487
|
28 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | > At the run start mlogger writes the ODB
to the .mid file. This needs conversion (binary
ODB -> XML ASCII) which can take time.
|
|
|
2530
|
13 Jun 2023 |
Marius Koeppel | Suggestion | Maximum ODB size |
> BTW, how do I resize the ODB. I remember
we discussed this some time ago, and concluded |
|
|
2814
|
30 Aug 2024 |
Marius Koeppel | Suggestion | Improve Event Documentation | Hi,
I am writing a Rust based midas file reader |
|
|
2817
|
01 Sep 2024 |
Marius Koeppel | Suggestion | Improve Event Documentation | > > Hi,
> >
> > I am writing a Rust based midas file |
|
|
2819
|
02 Sep 2024 |
Marius Koeppel | Suggestion | Improve Event Documentation | > > I am writing a Rust based midas file reader
>
> You might find this library I wrote useful: |
|
|
2847
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | This is not the case here. Note that the error
message: "Callback received for a midas::odb
object which went out of scope" is not called! |
|
|
2849
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | Okay, but this is then a big issue IMO. For
Mu3e we do this in every frontend and I also
checked again all of these watches are broken |
|
|
2852
|
18 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | I created a PR to fix this issue https://bitbucket.org/tmidas/midas/pull-requests/42.
The crash happened since the change in commit
3ad98c5 always got the ODB via XML.
|
|
|
2922
|
13 Dec 2024 |
Marius Koeppel | Info | New Feature: Message Search | Dear all,
a new feature was implemented which allows |
|
|
2022
|
25 Nov 2020 |
Marco Francesconi | Suggestion | ODBSET wildcards with array keys in Sequencer files | Hi,
I guess the issue is in the "[?]" part of
the command, the indexing is handled differently |
|
|
2024
|
25 Nov 2020 |
Marco Francesconi | Suggestion | ODBSET wildcards with array keys in Sequencer files | I created some keys in my ODB to try to match
yours.
The ODBSET commands you wrote are all working |
|
|
2038
|
30 Nov 2020 |
Marco Francesconi | Suggestion | ODBSET wildcards with array keys in Sequencer files | I totally agree that we should have a consistent
formatting for array index expansion.
I had a look to the mjsonrpc code and I found |
|
|
2218
|
16 Jun 2021 |
Marco Francesconi | Info | 1000 Mbytes/sec through midas achieved! | As reported by Stefan, in MEG II we have very
similar ethernet throughputs.
In total, we have 34 crates each with 32 |
|
|
2235
|
25 Jun 2021 |
Marco Francesconi | Bug Fix | changes in history plots | We are using the new history formula as a
quick way to convert signals from sensors
to actual physical values (for example Voltage->Temperature, |
|