Elog System Requirements, posted by Alan Grant on Fri Sep 15 00:56:38 2017
|
In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome. |
Re: Elog System Requirements, posted by Andreas Luedeke on Fri Sep 15 15:16:42 2017
|
Hi Alan,
we run our ELOG server (38 GB Logbook data in about 50 logbooks dating back up to 16 years) on a virtual Linux box.
The memory is important, since ELOG scans through all entries and creates an index at start-up. But we have only about 6% used out of 2GB: ELOG is not very demanding. If you have many and large pictures attached, then "convert" needs a bit of memory to work with.
Since "elogd" is a single task, you will not gain much from many CPUs. File IO is often a limiting factor: we've tried a while to run the logbook data on an AFS directory, and that did not turn out well. A local disk is best, an NFS disk works fine as well (in our case).
Cheers, Andreas
Alan Grant wrote: |
In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome.
|
|
Format Form, posted by Tim Schelfhout on Mon Oct 2 12:55:18 2017
|
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using "Format Leeftijd=1, attribname, 3, 3", which solves the field title
but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
Re: Format Form, posted by Stefan Ritt on Mon Oct 2 14:58:32 2017
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width, number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript.
Stefan
Tim Schelfhout wrote: |
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using this (Format Leeftijd=1, attribname, 3, 3), but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
|
Re: Format Form, posted by Tim Schelfhout on Mon Oct 2 15:20:04 2017
|
Thankx 4 the quick reply Stefan. The link you provided does not work .... could you point me again in the
right direction? Where can I find more info on this ability?
Thankx
Stefan Ritt wrote:
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width, number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript.
Stefan
Tim Schelfhout wrote: |
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using this (Format Leeftijd=1, attribname, 3, 3), but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
|
|
Re: Format Form, posted by Stefan Ritt on Mon Oct 2 15:53:39 2017
|
The link does now work in the email, but if you go to the web interface of the forum it does work.
Anyhow, you can go directly to https://midas.psi.ch/elogs/Forum/66909
Stefan
Tim Schelfhout wrote: |
Thankx 4 the quick reply Stefan. The link you provided does not work .... could you point me again in the
right direction? Where can I find more info on this ability?
Thankx
Stefan Ritt wrote:
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width, number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript.
Stefan
Tim Schelfhout wrote: |
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
- Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, 3)
- Text Entry fields should be max. width of 15 characters ?
Also struggling with mutliple fields on one line:
- Can Spacing between fields be controlled? Even vertical spacing?
- When omitting the css in the Format syntax, the fieldname and field gets colored dark blue
.. found via css inspection a part solution using this (Format Leeftijd=1, attribname, 3, 3), but then the value still gets colored dark blue
Also I see that when one formats the entry field in edit mode it shows differently in list mode. (for example set width is not enforced in list mode)
Anyone ?
|
|
|
|
Date must be between 1970 and 2037??, posted by Tim Schelfhout on Wed Oct 11 15:55:02 2017
|
Hey there,
Trying to record birthdates in ELOG ... field type being date results in error:
Date must be between 1970 and 2037 |
Can this be avoided? I like the fact that one can use the date picker to enter birthdate |
Attribute option "+x" not searcheable, posted by Stefano Lacaprara on Mon Oct 23 11:47:50 2017
|
Dear experts,
I have an elog with an attribute with fixed values, like this:
Attributes = Half
Options Half = +x, -x, both
It works fine, but I would like to find (or quick filter) all entries with Half=+x .
If I go to the search form, I can select +x from the dropdown menu for Half, but the search returns no result, even if I do have a number of entries with Half=+x. Likewise if I try to do the same with Quick filter.
I believe that this is due to the fact that the search uses regex, and "+" is reserved. I've tried to perform a search by entering manually and escaped "\+x", and it works as intended.
https://.../?mode=summary&reverse=0&reverse=1&npp=20&Half=%5E%5C%2Bx%24
However, since this attribute has a list of fixed values, it is not possible to entry manually something different "\+x" than what is defined in the config, that is "+x".
Is there a solution for this problem?
I would rather not change the attributes options (to, say, positive/negative), since that would mean changing manually a non negligible number of entries.
thanks,
Stefano |
|