Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 20:05:08 2018
|
I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"
Stefan
| Frank Baptista wrote: |
|
Thanks Stephan! I guess I was making it harder than it is. I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"? Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?
Thanks again for all you do -- Happy Holidays!
Frank
| Stefan Ritt wrote: |
|
Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring
So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.
Best,
Stefan
| Frank Baptista wrote: |
|
I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?
|
|
|
|
|
Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 20:52:46 2018
|
Thank you again -- very much appreciated! 
| Stefan Ritt wrote: |
|
I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"
Stefan
| Frank Baptista wrote: |
|
Thanks Stephan! I guess I was making it harder than it is. I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"? Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?
Thanks again for all you do -- Happy Holidays!
Frank
| Stefan Ritt wrote: |
|
Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring
So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.
Best,
Stefan
| Frank Baptista wrote: |
|
I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?
|
|
|
|
|
Re: Logbook architecture and availability, posted by Frank Baptista on Fri Feb 1 19:20:35 2019 
|
I've got things working - sort of. Ran into one strange problem that has me scratching my head. I have two different laptops, each running a local instance of their own logbook. Both are functional, but for some strange reason, one looks great, and the other is missing its graphic format. I've attached a screen capture of that logbook, and a copy of the config file. Do you see something that I've done wrong?
Thanks,
Frank
| Frank Baptista wrote: |
|
Thank you again -- very much appreciated!
| Stefan Ritt wrote: |
|
I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"
Stefan
| Frank Baptista wrote: |
|
Thanks Stephan! I guess I was making it harder than it is. I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"? Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?
Thanks again for all you do -- Happy Holidays!
Frank
| Stefan Ritt wrote: |
|
Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring
So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.
Best,
Stefan
| Frank Baptista wrote: |
|
I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?
|
|
|
|
|
|
|
Re: Logbook architecture and availability, posted by Frank Baptista on Fri Feb 1 21:59:46 2019
|
Sorry -- dumb mistake. I moved the "theme" files to the resource folder. Works like a champ...life is good!
| Frank Baptista wrote: |
|
I've got things working - sort of. Ran into one strange problem that has me scratching my head. I have two different laptops, each running a local instance of their own logbook. Both are functional, but for some strange reason, one looks great, and the other is missing its graphic format. I've attached a screen capture of that logbook, and a copy of the config file. Do you see something that I've done wrong?
Thanks,
Frank
| Frank Baptista wrote: |
|
Thank you again -- very much appreciated!
| Stefan Ritt wrote: |
|
I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"
Stefan
| Frank Baptista wrote: |
|
Thanks Stephan! I guess I was making it harder than it is. I'm still a little fuzzy -- in this instance, am I correct in saying that each laptop would be considered a "master", and the remote (network) server considered the "slave"? Also, I'm not sure quite sure -- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server?
Thanks again for all you do -- Happy Holidays!
Frank
| Stefan Ritt wrote: |
|
Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring" as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring
So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server.
Best,
Stefan
| Frank Baptista wrote: |
|
I have a setting which makes ELOG a perfect solution, but there's a situation that I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple.
My dilemma is, our network goes down for maintenance/updates (more often than I'd like), but our operation cannot afford to stop during network interruptions.
With that said, I thought about whether I could run a "local" logbook on each laptop/chamber, and somehow mirror the local logbook to the main ELOG server.
Perhaps I'm over-thinking this...do you have any recommendations?
|
|
|
|
|
|
|
Unwanted double entries eg. double clicking submit button, posted by Finn Junker on Wed Feb 13 09:29:36 2019
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn |
|
Re: Unwanted double entries eg. double clicking submit button, posted by David Pilgram on Wed Feb 13 10:58:37 2019
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
Re: Unwanted double entries eg. double clicking submit button, posted by Stefan Ritt on Wed Feb 20 15:14:32 2019
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|
Re: Unwanted double entries eg. double clicking submit button, posted by Alan Grant on Wed Feb 20 21:56:32 2019
|
I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If so, can you give any ETA on this new code availability?
Also I noticed that the Elog Home page still says "Current version is: 3.1.2". I assume that only means it hasn't been updated, not that it means it's the current STABLE version and subsequent releases are beta -- please correct me if I'm wrong. I just want to make sure I understand how the versions and releases work.
Endless thanks for this product and all your work Stefan.
| Stefan Ritt wrote: |
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...". So double submits should not be possible any more.
| David Pilgram wrote: |
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
| Finn Junker wrote: |
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting i a double or triple entry containing the same text and a almost identical timestamp.
Is there a way to aviod this?, my "solution" so far has been to select the entries and manually delete them. I'm using Elog version 3.14
Kind Regards Finn
|
|
|
|
|