ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67303
|
Fri Jul 13 17:09:58 2012 |
| Richard Stamper | richard.stamper@stfc.ac.uk | Question | All | 2.9.2 | Re: Number of conditional attributes |
Stefan Ritt wrote: |
Richard Stamper wrote: |
Is there a limit on the number of conditions that can be simultaneously active in a log? When I activate more than 10 conditions I start to see side effects with other conditions being deactivated. I think this is due to the hard-coded array size of 10 for clist in the match_param function in elogd.c. If so, could this limit be increased?
Are there other limits on the number of conditions, or the length of condition names? If I've understood the code right, the _condition string holds a comma-separated list of the active conditions, so the 256 byte length of this will also put some limit on the number of conditions that can be active.
|
Ups. I never imagined that someone would use more than 10 conditions. I'm not 100% sure if the problem is the clist array, but can you try to set it to 20 and see if it gets better? You can also send me your config file and I can try it myself.
|
I'll try increasing the list size(s), and will also prepare a simplified config file for you to look at. Maybe there is a another way to implement what I am trying to achieve?
In general terms I am trying to give an e-log a "memory" of what has been recorded previously in order to constrain what is permissible to record next. I do this by starting a log with an initial entry, then alter the config so that users can add records only by duplicating the last record. The log records the current state of some variables, and allows users to record changes to the state of any of these variables. Conditions are used to constrain the permitted state changes, depending on the current state; conditions are also used, with subst options, to update the current state variables when changes are made.
Specifically, we have "Mate-Demate" logs for connectors to record when connectors are mated and demated. Previously we just had an attribute for each connector in an assembly with options "Mate", "Demate" and "-" to indicate that either a mate or demate was carried out or that the connector was not touched on this occasion (although others were). My cunning plan was to ensure that a "Demate" (or no-op) was possible only if the connector is currently mated, and conversely that a "Mate" (or no-op) was possible only if the connector is currently demated. For each connector (e.g. ConnectorA), there are now two attributes
- "ConnectorA state", to record the current state, and
- "ConnectorA" to record any change.
A new record can be created only by duplicating the last record, thus copying the current state of the connectors, and for each connector the relevant config file entries are like this:
Show Attributes = ConnectorA
Show Attributes Edit = ConnectorA state, ConnectorA
Locked Attributes = ConnectorA state
Preset on duplicate ConnectorA = -
Options ConnectorA state = Mate{1}, Demate{2}
{2} Options ConnectorA = -, Mate{3}
{1} Options ConnectorA = -, Demate{3}
{3} Subst ConnectorA state = $ConnectorA
The logbook is set up with a record with "ConnectorA state" set to "Demate", which constrains "ConnectorA" to record either a no-op or a mate; if a mate is subsequently recorded then the Subst option for "ConnectorA state" substitutes the new status ("Mate") for the connector before the record is saved; in the new last record "ConnectorA state" is now set to "Mate" which permits only a demate; when a no-op is selected the state is unchanged, having been inherited through duplication from the last record. The number of conditions used is one per "ConnectorX state" attribute, plus one for each connector whose state is changed, so for assemblies with more than 5 connectors it is possible to have more than 10 conditions active at once.
|
1369
|
Thu Aug 4 20:29:23 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | | | | Re: Notify email recipient of attachments without including? |
Chris Green wrote: | Hi,
Our elog is going to be taking some large attachments. I've disabled the attachments from going out in the email, but I'd like email recipients to know that the post has attachments associated with it. Is there a mechanism to do this already, or would it be an enhancement? I'm looking for something like:
Email Notify Attachments = 0 | 1 | 2
Where 0 = no notification,
1 = number only,
2 = list
... independent of whether attachments are included with the email itself.
Thanks,
Chris. |
I added Email Format = 64 for only attachment names. So you could set Email Format = 111 to get everything except the full attachments. |
1377
|
Fri Aug 5 01:15:23 2005 |
| Chris Green | greenc@fnal.gov | | | | Re: Notify email recipient of attachments without including? |
Stefan Ritt wrote: |
Chris Green wrote: | Hi,
Our elog is going to be taking some large attachments. I've disabled the attachments from going out in the email, but I'd like email recipients to know that the post has attachments associated with it. Is there a mechanism to do this already, or would it be an enhancement? I'm looking for something like:
Email Notify Attachments = 0 | 1 | 2
Where 0 = no notification,
1 = number only,
2 = list
... independent of whether attachments are included with the email itself.
Thanks,
Chris. |
I added Email Format = 64 for only attachment names. So you could set Email Format = 111 to get everything except the full attachments. |
Thanks for this. Will verify as soon as someone posts to the (now live) logbook.
Chris. |
972
|
Fri Mar 4 10:50:57 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.7-1 | Re: Non clickable column | > Is there any solution to obtain an non-clickable column ?
> For example here : http://midas.psi.ch/elogs/Config+Examples/ what should
> I do to obtain the data of the Category column non clickable?
> I don't have find a solution in the Syntax of elogd.cfg
> (http://midas.psi.ch/elog/config.html)
What do you mean by "non-clickable column"? The column header for sorting, or
the column contents which brings you to the single entry page? For both of
them, there is no way right now to obtain that. Why do you want it? |
973
|
Fri Mar 4 10:59:51 2005 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.5.7-1 | Re: Non clickable column | > > Is there any solution to obtain an non-clickable column ?
> > For example here : http://midas.psi.ch/elogs/Config+Examples/ what should
> > I do to obtain the data of the Category column non clickable?
> > I don't have find a solution in the Syntax of elogd.cfg
> > (http://midas.psi.ch/elog/config.html)
>
> What do you mean by "non-clickable column"? The column header for sorting, or
> the column contents which brings you to the single entry page? For both of
> them, there is no way right now to obtain that. Why do you want it?
I talk about the column contents. In fact on ELOG, we store password so its
more easyer to click twice on it to select them and after to copy them instead
of select from right to left the password and to try to copy them. The HMTL
link gave problem, its more hard to copy data from HTML link than an normal TXT.
A little hard to explain sorry for my mistakes and explication I'm French :o). |
983
|
Mon Mar 14 21:56:15 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.7-1 | Re: Non clickable column | > I talk about the column contents. In fact on ELOG, we store password so its
> more easyer to click twice on it to select them and after to copy them instead
> of select from right to left the password and to try to copy them. The HMTL
> link gave problem, its more hard to copy data from HTML link than an normal TXT.
> A little hard to explain sorry for my mistakes and explication I'm French :o).
I added a new option "Link display = ...", with which you can restrict the number of
attribues which gets a HTML link. If you put
Link display = ID, Author
then only the ID column and the colum with the Author are shown as HTML links, all
other are shown as simple text.
The new version is under CVS. This option will be included in the next release. |
984
|
Tue Mar 15 14:11:48 2005 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.5.7-1 | Re: Non clickable column | > > I talk about the column contents. In fact on ELOG, we store password so its
> > more easyer to click twice on it to select them and after to copy them instead
> > of select from right to left the password and to try to copy them. The HMTL
> > link gave problem, its more hard to copy data from HTML link than an normal TXT.
> > A little hard to explain sorry for my mistakes and explication I'm French :o).
>
> I added a new option "Link display = ...", with which you can restrict the number of
> attribues which gets a HTML link. If you put
>
> Link display = ID, Author
>
> then only the ID column and the colum with the Author are shown as HTML links, all
> other are shown as simple text.
>
> The new version is under CVS. This option will be included in the next release.
Great news :) !
thanks a lot ! |
66226
|
Thu Feb 26 11:05:36 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: No Valid Header? |
mike cianci wrote: |
Stefan,
I finally got it installed on a server at work (only took a year to work through all the red tape). I have seven logbooks up and running and only one is giving me trouble. It is an On-Line Help book where I wanted to store documents that could be referenced by our staff. It is the simplest of my logbooks (see config file below) but when I hit the "Submit" button it crashes the program. I can not see the error myself but the server guys are telling me that that we are getting an "Internal error, no valid header!" error. The only other thing that I can think to mention is that the entry that is crashing the program is a 60k Microsoft word table that I had cut and pasted into elog.
|
Ah, that rings a bell. We recently had problems with large tables. Can you try the current version if you get the same problem? |
|