| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
880
|
12 Apr 2013 |
Stefan Ritt | Forum | Persistent ipcrm error | > [odb.c:6038:db_paste,ERROR] found string
exceeding MAX_STRING_LENGTH
|
|
|
192
|
20 Jan 2005 |
Konstantin Olchanski | Bug Report | Persistency problem with h1_book() & co | The current h1_book() macros (and the previous
example analyzer code) have an
odd persistency problem: for example, the |
|
|
193
|
21 Jan 2005 |
John M O'Donnell | Bug Report | Persistency problem with h1_book() & co | > The current h1_book() macros (and the previous
example analyzer code) have an
> odd persistency problem: for example, the |
|
|
194
|
21 Jan 2005 |
Stefan Ritt | Bug Report | Persistency problem with h1_book() & co | > I can't get onto cvs@midas.psi.ch right
now
> (cvs update
|
|
|
195
|
25 Jan 2005 |
Stefan Ritt | Bug Report | Persistency problem with h1_book() & co | > > I can't get onto cvs@midas.psi.ch right
now
> > (cvs update
|
|
|
196
|
25 Jan 2005 |
John M O'Donnell | Bug Report | Persistency problem with h1_book() & co | So now that cvs is reachable again I have
confirmed that
the code segment
|
|
|
471
|
23 Mar 2008 |
Konstantin Olchanski | Info | Per-variable history implementation in the mlogger | The changes to mlogger implementing per-variable
history have been committed to
svn. Revision 4145.
|
|
|
472
|
23 Mar 2008 |
Konstantin Olchanski | Info | Per-variable history implementation in the mlogger | > The changes to mlogger implementing per-variable
history have been committed to
> svn. Revision 4145.
|
|
|
474
|
25 Mar 2008 |
Stefan Ritt | Info | Per-variable history implementation in the mlogger | Before approving the code, two conditions
have to be fulfilled:
|
|
|
1329
|
21 Nov 2017 |
Konstantin Olchanski | Release | Pending release of midas | We are readying a new release of midas and
it is almost here except for a few buglets
on the new html status page.
|
|
|
1413
|
05 Dec 2018 |
Konstantin Olchanski | Info | Partial refactoring of ODB code | The current ODB code has several structural
problems and I think I now figured out how
to straighten them out.
|
|
|
1414
|
11 Dec 2018 |
Stefan Ritt | Info | Partial refactoring of ODB code | All makes sense to me. I agree to proceed
with the refactoring.
|
|
|
1419
|
26 Dec 2018 |
Konstantin Olchanski | Info | Partial refactoring of ODB code | > One additional comment: In the 90's when
I developed this code, locking was expensive.
> Now the world has changed, we can do almost |
|
|
1423
|
27 Dec 2018 |
Stefan Ritt | Info | Partial refactoring of ODB code | > I am not sure this is quite true. The CPU
can execute 3000 million operations per second
(3GHz CPU, assuming 1 op/Hz),
|
|
|
2742
|
30 Apr 2024 |
Luigi Vigani | Bug Report | Params not initialized when starting sequencer | Good afternoon,
After updating Midas to the latest develop |
|
|
2750
|
03 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | Could you please export and send me the /Sequencer
ODB tree (or just /Sequencer/Param and /Sequencer/Variables)
in both cases while the sequence is running. |
|
|
2751
|
03 May 2024 |
Stefan Ritt | Bug Report | Params not initialized when starting sequencer | Ok, here is the complete code to reproduce
the problem. Load parameter_test.msl which
includes functions.msl. From the screenshot |
|
|
2752
|
03 May 2024 |
Luigi Vigani | Bug Report | Params not initialized when starting sequencer | It is pretty much the same as Stefan, I attach
here the screenshots. Also in my case it
works sometimes, and sometimes partially |
|
|
2755
|
03 May 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | I have been able to reproduce the problem
only once. From what I see, it seems that
the Variables ODB tree is not initialized |
|
|
2756
|
03 May 2024 |
Stefan Ritt | Bug Report | Params not initialized when starting sequencer | Ahh, that rings a bell:
1) JS opens start dialog box
|
|