ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67272
|
Mon May 14 18:15:44 2012 |
| UlfO | ulf.olsson@dynamate.se | Question | Windows | 2.9.1-2435 | Locked attributes and edit records | Hi!
After submitting a new record with preset "Locked attributes" not even admin user is able to edit these entries.
What seems to be the problem?
Note my config
Logbook Tabs = 0
Theme = default
Date Format = %Y, %B
Title Image= <img border=0 src="konturlogo_dynamate.png" alt="DynaMate logo">
Logout to main = 1
Mode commands = 0
List after submit = 1
Use Email From = weblog@dynamate.se
Use Lock = 1
Password file=improvements_qpp.pwd
Admin User = sssuxo, sssuga
Self register = 3
Restrict edit = 1
Login expiration = 0
Display Email recipients = 0
Preset text = qpp_improvements.txt
Comment = Improvements Uppdragsprocessen
Attributes = Namn, Avdelning, Telefonnummer, Rubrik, Ansvarig, Beräknad klar, Verkligt klar, Status, Status2
Required Attributes = Namn, Avdelning, Telefonnummer, Rubrik
Locked attributes = Ansvarig, Beräknad klar, Verkligt klar, Status, Status2
Options Rubrik = Förfrågan - Mottagning, Förfrågan - Bearbetning, Förfrågan - Anbud, Genomförande - Beställning, Genomförande - Uppdragsplanering, Genomförande - Projektering/Konstruktion, Genomförande - Tillverkning/Utförande, Genomförande - Överlämning till kund, Genomförande - Avslut av uppdrag, Annat
Type Beräknad klar = date
Type Verkligt klar = date
Subst Beräknad klar = $Date
Subst Verkligt klar = $Date
Options Status = Ny, 0%, 25%, 50%, 75%, 100%
Options Status2 = Pågående, Avklarad
Preset Status = Ny
Preset Status2 = Pågående
Cell Style Status 25% = background-color:yellow
Cell Style Status 50% = background-color:orange
Cell Style Status 75% = background-color:33CCFF
Cell Style Status 100% = background-color:green
List Menu Commands = New, Find, Select, Logout, Config, Last day, Help
Menu commands = List, New, Edit, Delete, Find, Help
List Display = Datum, Namn, Avdelning, Beräknad klar, Verkligt klar, Ansvarig, Status, Status2, Rubrik
Guest menu commands = List, Find, Login, Help
Guest List Menu commands = List, Find, Login, Help
Guest list Display = Datum, Namn, Avdelning, Beräknad klar, Verkligt klar, Ansvarig, Status, Status2, Rubrik
Allow Config = sssuxo
Page Title = Improvements Uppdragsprocessen QPP - $Subject
Suppress default = 3
Reverse sort = 1
Quick filter = Date, Ansvarig, Status, Status2
Regards
/UlfO
|
67271
|
Fri May 11 13:20:35 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.0 | Re: HW Requirements to run elog / Performance issues running on ARM |
Tim Thiel wrote: |
Yoshio Imai wrote: |
Hi!
Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.
Yoshio
|
Yoshio,
Thanks for the suggestion.
We have actually tried running the elog server with a very minimal set of attributes, all of which were human entries, and still had response times that were entirely unacceptable. So, unfortunately this path won't solve all our issues.
tt
|
Yes there is lots of string handling in elogd, but compared with PHP this is still faster. The getcfg() call actually caches the contents of the config file to improve its performance. I stopped optimization when the response was quick on a 800 MHz Pentium originally, but your 250 MHz ARM might be slower. What you can try is to
1) Verify that the CPU is really the limit, just check that the CPU is at 100% with elogd during your 10 second response time. On some installations, the submit command triggers some email notification, and actually the email server was the bottleneck.
2) If it's indded the CPU for elogd, run it under the gcc profiler. Identify which routines take most CPU and let me know. Maybe I can do something about that.
- Stefan |
67270
|
Thu May 10 16:35:50 2012 |
| Tim Thiel | tt2005@thieleng.com | Question | Linux | 2.9.0 | Re: HW Requirements to run elog / Performance issues running on ARM |
Yoshio Imai wrote: |
Hi!
Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.
Yoshio
|
Yoshio,
Thanks for the suggestion.
We have actually tried running the elog server with a very minimal set of attributes, all of which were human entries, and still had response times that were entirely unacceptable. So, unfortunately this path won't solve all our issues.
tt
|
67269
|
Thu May 10 15:34:39 2012 |
| Yoshio Imai | $user_email | Question | Linux | 2.9.0 | Re: HW Requirements to run elog / Performance issues running on ARM | Hi!
Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.
Yoshio |
67268
|
Wed May 9 21:48:42 2012 |
| Tim Thiel | tt2005@thieleng.com | Question | Linux | 2.9.0 | HW Requirements to run elog / Performance issues running on ARM | Our group is interested in installing elog on a small/low-cost processing platform so that we can provide ready-to-run systems for our collaborators to use. We selected a candidate platform form Technologic Systems, their wifibox-2 (http://www.embeddedarm.com/products/board-detail.php?product=TS-WIFIBOX-2). This product is based on the TS7553 CPU board (http://www.embeddedarm.com/products/board-detail.php?product=TS-7553#) which has a 250MHz Cavium ARM9 CPU.
We have had good success getting the elogd executable cross-compiled for use on this platform and have a working system. However, we are having significant issues with performance. When we click the "New" item to enter a new event there is a noticable delay. When clicking "Submit" there is a delay of approximately 10 seconds before the browser window displays the new event. With the elogd running on other platforms (Virtual Machine or netbook) the delays for these actions are very small - typically less than a second or imperceptible.
So here are some specific questions:
- Is it reasonable to expect a 250 MHz ARM processor to serve an elog logbook with user acceptable performance?
- Our cfg file is attached. Is there anything in the cfg file creating this performance problem.
- I have spent some time looking at this, and suspect that the delay is due to the cpu load of all the string manipulation and comparison operations (1200 calls to getcfg() on a submit). Are there other candidate sources of performance issues that should be considered?
- Does anyone have any suggestions on how to improve our performance?
- Does anyone have a suggestion for an alternative small and low-cost COTS platform to use to host the elogd application? (We would prefer to attain satisfactory performance on the Wifibox-2.)
Thanks for any help that can be offered.
Tim
|
Attachment 1: elogd-001.cfg
|
# === CONFIG FILE GENERATION DOCUMENTATION ===
#
# === GLOBAL PARAMETERS ===
# Note: Setup CruiseId and Logbooks
# Note: Datasnap logbook not in this version
#[global]
#Main Tab = oc3334
#Group Cruise = oc3334-SE
# === GENERAL OPTIONS ===
# Note: From general options of elogd.cfg part of administrators guide
#Comment = oc3334_COMMENT
#Subject = oc3334 Cruise Log
#Page title = oc3334 Cruise Log
Time format = %d %b %Y %H:%M
# === LOGBOOK: Science Eventlog ===
[oc3334-SE]
# === Execute Shell Command ===
# Note: execute shell command to enter a datasnap to DS logbook at new
# Note: needs to run in background
#Execute new = $shell(/shipdata/oc3334/r2r/eventlog/datasnap/CRUISEID_ds2elog.pl &)
# === Menu: List ===
# Note: Menu list
# Note: Needs to be commented out for local copy, use on synced logbooks
# Note: Used for shore view
#Menu commands = List, Find, Help
#List Menu commands = List, Find, Help
# Note: Used on ship, config option is in ECFM
#Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Help
#List Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Help
# === DISPLAY: List ===
# Note: directives related to how attributes are listed on the display page
# Note: default is ID, Date, <full attribute list>
#List display = Event, dateTimeUTC, Instrument, Action, Transect, Station, Cast, Latitude, Longitude, Seafloor, Author, Comment, Revisions
#Sort attributes = Event
# === DISPLAY: Entry ===
# Note: directives related to how attributes are configured on the data entry page
# Note: unlock these temporarily if it is necessary to edit the fields
# Note: locked Latitude, Longitude, and Seafloor
##Locked Attributes = Revisions, Cruise, Event, R2R_Event, dateTimeUTC, GPS_Time, Latitude, Longitude, Seafloor
# Note: unlocked Latitude, Longitude, and Seafloor
#Locked Attributes = Revisions, Cruise, Event, R2R_Event, dateTimeUTC, GPS_Time, dateTime8601
#Required Attributes = Author, Instrument, Action
# === ATTRIBUTES (GENERAL) ===
# Note: Specify the attributes for this event log
# Note: An event = Instrument + Action; e.g. event = a CTD cast is started
Attributes = Event, Instrument, Action, Transect, Station, Cast, Latitude, Longitude, Seafloor, Author, Comment, Cruise, R2R_Event, dateTimeUTC, GPS_Time, dateTime8601, Revisions
#Attributes = Instrument, Action
# === ATTRIBUTE: Entry Time
# Note: This attribute is generated automatically by ELOG software
# === ATTRIBUTE: Event ===
# Characteristics: Locked
# Note: UTC time-based attributes
# Note: Science event number must be unique within a cruise
# Note: YYYYMMDD.HHMMSS.###
# Note: ### starts at 001 and updates to 002 if the date part of the attribute has not changed
#
#Preset Event = $shell(date +%Y%m%d.%H%M).###
#Subst Event = $shell(date +%Y%m%d.%H%M).###
#Preset on Duplicate Event = $shell(date +%Y%m%d.%H%M).###
# === ATTRIBUTE: Transect ===
Preset Transect = NaN
# === ATTRIBUTE: Station ===
Preset Station = NaN
# === ATTRIBUTE: Cast
Preset Cast = NaN
# === ATTRIBUTE: Latitude ===
# Characteristics: Locked
#Subst Latitude = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_gps_latlon -o lat -p 55150)
Tooltip Latitude = filled on entry
# === ATTRIBUTE: Longitude ===
# Characteristics: Locked
#Subst Longitude = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_gps_latlon -o lon -p 55150)
Tooltip Longitude = filled on entry
# === ATTRIBUTE: Seafloor ===
# Characteristics:
# Subst Seafloor = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_depth -o depth -p 55200)
# === ATTRIBUTE: Comment ===
Preset on Duplicate Comment =
Tooltip Comment = Enter additional information
Comment Comment = Please be brief; no commas
# === ATTRIBUTE: Cruise ===
# Characteristics: Locked
# Note: Get Cruise from Cruise_ID file when on board
Preset Cruise = oc3334
# === ATTRIBUTE: R2R_Event ===
# Characteristics: Locked
# Note: Preset this attribute and then reset it on submit
#Preset R2R_Event = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/r2r_event_se.oc).###
#Subst R2R_Event = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/r2r_event_se.oc).###
#Preset on Duplicate R2R_Event = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/r2r_event_se.oc).###
# === ATTRIBUTE: dateTimeUTC ===
# Characteristics: Locked
# Note: Preset this attribute and then reset it on submit
# Note: other event number formats
# Note: using UTC YrDay: Preset Event = $shell(echo 'date -u +%j%y.%H%M`)
#Preset dateTimeUTC = $shell(date -u +%Y%m%d.%H%M)
#Subst dateTimeUTC = $shell(date -u +%Y%m%d.%H%M)
#Preset on Duplicate dateTimeUTC = $shell(date -u +%Y%m%d.%H%M)
# === ATTRIBUTE: GPS_Time ===
# Characteristics: Locked
#Subst GPS_Time = $shell(/shipdata/oc3334/r2r/eventlog/elog/scripts/get_gps_latlon -o gps_time -p 55150)
Tooltip GPS_Time = filled on entry
# === ATTRIBUTE: dateTime8601 ===
# Characteristics: Locked
# Note: Preset this attribute and then reset it on submit
# Note: other event number formats
# Note: using ISO 8601 YrDay: Preset Event = $shell(echo '--iso-8601=seconds`)
#Preset dateTime8601 = $shell(date --iso-8601=seconds)
#Subst dateTime8601 = $shell(date --iso-8601=seconds)
#Preset on Duplicate dateTime8601 = $shell(date --iso-8601=seconds)
# === ATTRIBUTE: Depth ===
Tooltip Depth = filled on entry
# === ATTRIBUTE: Revisions ===
# Characteristics: Locked
# Note: if we require logins, then revisions could be authored too using $short or $long_name
Preset on Duplicate Revisions =
Subst on Edit Revisions = $Revisions & $date
# === FLAGS ===
# sort order for event display
Reverse sort = 0
# Configure the default behavior
# Do not allow a text entry box with attachments (this is different from the Comment field)
Show text = 0
# Do not allow attachments
Enable attachments = 0
# Suppress email notification and do not even display email notification option
Suppress default = 3
Suppress Email on edit = 3
Resubmit default = 2
# quick filter options for display
Quick filter = Author, Instrument, Action
#
#
# List of instruments created by elogcfm
#
Options Instrument = ADCP150{10}, CTD911{1}, Echosounder12{2}, Echosounder3.5{3}, Other{4}, Ship{5}, Thermosalinograph SBE45{6}, XBT{7}, MeteorologicalSensor{8}, Fluorometer{9},
#
# List of instrument actions created by elogcfm
#
{10} ROptions Action = start,stop,service,other
{1} ROptions Action = deploy,maxDepth,recover,abort,other
{2} ROptions Action = startLine,endLine,abortLine
{3} ROptions Action = startLine,endLine,abortLine
{4} ROptions Action = start,end
{5} ROptions Action = startCruise,endCruise,other
{6} ROptions Action = start,stop,other
{7} ROptions Action = release
{8} ROptions Action = startLine,endLine,abortLine,sampleLine
{9} ROptions Action = startLine,endLine,abortLine,sampleLine
|
67267
|
Wed May 9 01:07:43 2012 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | Latest | Re: Adding an image to the top text |
Danielle Gillanders wrote: |
Hi there,
I am new to ELOG, trying to add an image (logo) in my top text.
Theme = default
Comment = TRIPLE POINT Log
Top text = Logo.png
results in ‰PNG .
When I just enter a string of text it seems to work fine... I would really appreciate any help!
thanks!
|
Hi there,
I'm not sure where it appears in the documentation, but question 9 of the FAQs shows that 'Bottom text' has to be in html - and so does 'top text'
The get-it-done-now way to do it would be
Top Text = <img src=Logo.png>
(and ensure Logo.png is in the same directory as the config file - otherwise you'd best put the path of where it is in).
Of course you can do all sorts of things with this, such as centering, have it so that if you click on the logo you get taken to some other home page, but for
all that sort of thing check up with a guide to html.
|
67266
|
Wed May 9 00:55:08 2012 |
| Danielle Gillanders | danielle.gillanders@fortisbc.com | Question | Windows | Latest | Adding an image to the top text | Hi there,
I am new to ELOG, trying to add an image (logo) in my top text.
Theme = default
Comment = TRIPLE POINT Log
Top text = Logo.png
results in ‰PNG .
When I just enter a string of text it seems to work fine... I would really appreciate any help!
thanks! |
67265
|
Mon May 7 15:12:24 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.9.1-2435 | Re: Access rights |
Roland Gsell wrote: |
Hi,
the manual says:
"
There are four ways through which access to a logbook may be controlled:
it may be open for all to read ;
it may require a common "read" password for all users ;
it may require each user to have an individual user account (login name) and password ;
finally, access may be granted or not depending on the address of the workstation you are using.
"
But it doesn't say how to do so or at least I didn't find it.
If I have each user have to log in with an individual accout, can I define which logbooks he can read and/or modify?
If yes, how to do that?
Also, please accept my vote for user groups. We can use that, too.
TIA,
Roland.
|
You haven't found it. Just look here:
http://midas.psi.ch/elog/config.html#access
You need Password file and Login user. |
|