ID |
Date |
Author |
Topic |
Subject |
Text |
|
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
|
|
2446
|
05 Nov 2022 |
Zaher Salman | Suggestion | histories capture 'ruy' | The histories capture key events from 'r'
'u' 'y' and 'Escape' for various functions
like rescaling etc. However, this also means |
|
2451
|
13 Jan 2023 |
Denis Calvet | Suggestion | Debug printf remaining in mhttpd.cxx | Hi everyone,
It has been a long time since my last message. |
|
2452
|
13 Jan 2023 |
Stefan Ritt | Suggestion | Debug printf remaining in mhttpd.cxx | These debug statements were added by K.O.
on June 24, 2021. He should remove it.
|
|
2453
|
31 Jan 2023 |
Lukas Gerritzen | Suggestion | "Soft interlock" possible? | Is it possible to impose requirements on certain
output variables in an interlock-like fashion?
For example: "As long as the temperature |
|
2454
|
31 Jan 2023 |
Stefan Ritt | Suggestion | "Soft interlock" possible? | > Is it possible to impose requirements on
certain output variables in an interlock-like
fashion? For example: "As long as the temperature |
|
2455
|
08 Feb 2023 |
Stefan Ritt | Suggestion | histories capture 'ruy' | > The histories capture key events from 'r'
'u' 'y' and 'Escape' for various functions
like rescaling etc. However, this also means |
|
2456
|
09 Feb 2023 |
Zaher Salman | Suggestion | histories capture 'ruy' | I agree with you, option 2 is better and works
well.
The only problem is that if you are showing |
|
2457
|
09 Feb 2023 |
Stefan Ritt | Suggestion | histories capture 'ruy' | > I agree with you, option 2 is better and
works well.
> The only problem is that if you are showing |
|
2476
|
27 Apr 2023 |
Marius Koeppel | Suggestion | Maximum ODB size | Hi all,
> I agree, I think we can safely bump the |
|
2477
|
27 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > > I agree, I think we can safely bump the
limit from 100 Mbytes to 1 Gbyte, maybe 1.5
or
|
|
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 |
|
2481
|
27 Apr 2023 |
Konstantin Olchanski | Suggestion | Maximum ODB size | > You said the writing into .odb is buggy.
Do you mean it’s buggy in general or only
in this specific case?
|
|
2482
|
27 Apr 2023 |
Konstantin Olchanski | 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 from ODB, XML |
|
2483
|
27 Apr 2023 |
Stefan Ritt | Suggestion | Maximum ODB size | > Congratulations. created != "it works".
Two other tings to consider:
|
|
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 |
|
2486
|
28 Apr 2023 |
Stefan Ritt | Suggestion | Maximum ODB size | > Is this maybe related to what Stefan said
about the run start - so that odbedit needs
some time to load the bigger ODB?
|
|