| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
149
|
03 Oct 2004 |
Konstantin Olchanski | Info | Increased number of clients in midas.h, important! | > It is important to note that clients compiled
> with the old limits cannot coexist with
clients compiled with the new limits. You |
|
|
151
|
03 Oct 2004 |
Stefan Ritt | Info | Increased number of clients in midas.h, important! | > Stefan, to avoid confusion from crashes
caused by incompatible ODBs would it be possible
to add a "version number" to ODB,
|
|
|
152
|
03 Oct 2004 |
Konstantin Olchanski | Info | Increased number of clients in midas.h, important! | > However, we are planning to make a new release
1.9.5 soon (next week), so can can people
tell not to "mix" 1.9.5 with pre-1.9.5 programs.
|
|
|
153
|
04 Oct 2004 |
Stefan Ritt | Info | Increased number of clients in midas.h, important! | > Right. We cannot fix the past, but we should
fix the future. BTW, "do not mix versions"
is hard to enforce and mismatches did, do |
|
|
154
|
08 Oct 2004 |
chris pearson | Info | Increased number of clients in midas.h, important! |
> > For one thing, looking at a given midas-using
executable, how do I tell what version of |
|
|
155
|
08 Oct 2004 |
Konstantin Olchanski | Info | Increased number of clients in midas.h, important! | > A lot of programs have a commandline
option, such as "--version", where they return
the program version number then exit. As |
|
|
302
|
20 Sep 2006 |
Stefan Ritt | Suggestion | Increase of maximum event size | Dear midas users,
The current event size in midas is limited |
|
|
303
|
20 Sep 2006 |
Stefan Ritt | Suggestion | Increase of maximum event size | Since nobody complained so far, I increased
MAX_EVENT_SIZE to 2MB. If anybody has problems
with this setting, please report. Note that |
|
|
308
|
27 Sep 2006 |
Konstantin Olchanski | Suggestion | Increase of maximum event size | > The current event size in midas is limited
to 512k (MAX_EVENT_SIZE in midas.h)
|
|
|
309
|
28 Sep 2006 |
Stefan Ritt | Suggestion | Increase of maximum event size | [quote="K.O."]Now, we have per-buffer tunable
size (see message
https://ladd00.triumf.ca/elog/Midas/283) |
|
|
Draft
|
07 Jun 2017 |
Alberto Remoto | Forum | Increase MAX_EVENT_SIZE | Hello,
I am using a CAEN v1720 to digitise signal |
|
|
514
|
23 Oct 2008 |
Konstantin Olchanski | Bug Report | Inconsistent handling of odb and evet buffer timeouts | In midas.c there are several places where
client last activity time stamps are checked
against the
|
|
|
517
|
28 Oct 2008 |
Stefan Ritt | Bug Report | Inconsistent handling of odb and evet buffer timeouts | > In midas.c there are several places where
client last activity time stamps are checked
against the
|
|
|
2561
|
24 Jul 2023 |
Nick Hastings | Bug Report | Incompatible data types with mysql odbc interface | Hello,
I have recently set up a midas-2022-05-c |
|
|
2562
|
25 Jul 2023 |
Nick Hastings | Bug Report | Incompatible data types with mysql odbc interface | Hello,
wanted add few things:
|
|
|
2531
|
13 Jun 2023 |
Thomas Senger | Forum | Include subroutine through relative path in sequencer | Hi, I would like to restructure our sequencer
scripts and the paths. Until now many things
are not generic at all. I would like to ask |
|
|
2532
|
13 Jun 2023 |
Stefan Ritt | Forum | Include subroutine through relative path in sequencer | > Hi, I would like to restructure our sequencer
scripts and the paths. Until now many things
are not generic at all. I would like to ask |
|
|
2533
|
13 Jun 2023 |
Marco Francesconi | Forum | Include subroutine through relative path in sequencer | > > Hi, I would like to restructure our sequencer
scripts and the paths. Until now many things
are not generic at all. I would like to ask |
|
|
2540
|
13 Jun 2023 |
Stefan Ritt | Forum | Include subroutine through relative path in sequencer | > when I did this job for MEG II we decided
not to include relative paths and the ".."
folder to avoid an exploit called "XML Entity |
|
|
2061
|
17 Dec 2020 |
Amy Roberts | Suggestion | Improving variable functionality in Sequencer? | We're using the sequencer to manage runs,
and this typically looks something like:
|
|