| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2133
|
23 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | History is from two separate equipments/frontends,
but both have "Log history" set to 1. |
|
|
2134
|
23 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | Tried with export of two different time ranges,
and the shift appears to remain the same,
|
|
|
2136
|
24 Mar 2021 |
Lars Martin | Bug Report | Time shift in history CSV export | I think from my perspective the separate files
are fine. I personally don't really like
the format
|
|
|
2137
|
25 Mar 2021 |
Lars Martin | Bug Report | Minor bug: Change all time axes together doesn't work with +- buttons | Version: release/midas-2020-12
In the new history display, the checkbox |
|
|
2144
|
09 Apr 2021 |
Lars Martin | Suggestion | Time zone selection for web page | The new history as well as the clock in the
web page header show the local time
of the user's computer running the browser.
|
|
|
2227
|
21 Jun 2021 |
Lars Martin | Bug Report | ELog documentation inconsistency | The documentation fro the Elog ODB tree here:
https://midas.triumf.ca/MidasWiki/index.php//Elog_ODB_tree#Url
|
|
|
2304
|
01 Dec 2021 |
Lars Martin | Bug Report | Off-by-one in sequencer documentation | The documentation for the sequencer loop says:
<quote>
|
|
|
2438
|
14 Oct 2022 |
Lars Martin | Suggestion | Allow onchange to refer to arbitrary js function | Maybe this is already possible, I have a hard
time understanding the mhttpd source code.
|
|
|
2440
|
22 Oct 2022 |
Lars Martin | Info | Allow onchange to refer to arbitrary js function | I figured I wasn't the first to have this
idea.
Works great, thanks! |
|
|
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 |
|
|
2442
|
22 Oct 2022 |
Lars Martin | Info | Allow onchange to refer to arbitrary js function | Actually, now that I look again, there is
a mistake in the instructions:
you say
|
|
|
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).
|
|
|
2298
|
29 Oct 2021 |
Kushal Kapoor | Bug Report | Unknown Error 319 from client | I’m trying to run MIDAS using a frontend code/client
named “fetiglab”. Run stops
after 2/3sec with an error saying “Unknown |
|
|
2519
|
23 May 2023 |
Kou Oishi | Bug Report | Event builder fails at every 10 runs | Dear MIDAS experts,
Greetings!
|
|
|
Draft
|
02 Jun 2023 |
Kou Oishi | Bug Report | Event builder fails at every 10 runs | Dear
> > The event builder fails to initiate the |
|
|
2524
|
02 Jun 2023 |
Kou Oishi | Bug Report | Event builder fails at every 10 runs | Dear Ben,
Hello. Thank you for your attention to this |
|
|
142
|
26 Jul 2003 |
Konstantin Olchanski | | more ODB checks in src/odb.c | Add more checks to db_validate_key() for pkey->total_size,
item_size and
num_values. Automatically correct total_size |
|
|
141
|
26 Jul 2003 |
Konstantin Olchanski | | use "odbedit -C" to connect to corrupted ODB | Add switch "-C" to odbedit to allow it to
connect to corrupted ODB. Then,
depending on corruption, the user can manually |
|
|
139
|
29 Jul 2003 |
Konstantin Olchanski | | Have to link with -lpthread? | It appears that all midas applications are
now required to link with the
pthreads library even if they do not use |
|
|
135
|
11 Aug 2003 |
Konstantin Olchanski | | mhttpd crash on corrupted ODB /RunInfo | Invalid values of ODB /RunInfo/State cause
mhttpd crash in
show_status_page() because of an out of bounds |
|