ELOG Forum

Re: length of condition names

3.1.3

You can easily use multi-character conditionals, up to 256 chars.

Harry Martin wrote:

The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change to that rule anywhere in the docs.

I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive of each condition. It works, but I am concerned I may be doing something that might not be supported going forward. (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)

Thank you, again, for this fine (and, may I add, fun?) tool. I'm having a good time with it!

69279

Fri Dec 4 02:03:56 2020

Harry Martin

harrymartin772@gmail.com

Question

Re: length of condition names

3.1.3

Could we update the doc for this?

Stefan Ritt wrote:

You can easily use multi-character conditionals, up to 256 chars.

Harry Martin wrote:

The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change to that rule anywhere in the docs.

Thank you, again, for this fine (and, may I add, fun?) tool. I'm having a good time with it!

69369

Mon Jun 14 16:15:10 2021

Sebastian Schenk

sebastian.schenk@physik.uni-halle.de

Bug report

Additional forbidden attributes

Hello Stefan,

I stubbled on a issue with our elog.
We introduced an attribute "mode" to one of the elogs and it breaks the "Find" function as this attribute is already used for the viewing settings "full", "summary" and "threaded".
(HTTP parameter pollution)

I suspect other special attributes used by the internals of elog should also not be allowed.
A quick search in the "Find" reveals these attributes in the URL, so I guess, these should also be avoided.
This list could be incomplete

npp, ma, da, ya, mb, db, yb, attach, reverse, mode

A simple workaround would be updating the documentation to add these to the list of forbidden attributes.
https://elog.psi.ch/elog/config.html
Maybe a warning can be added, if the elog behaves unexpected, try other attribute names, as they can conflict with internal attributes.

A fix could be to add a prefix for internal attributes, which can't be used for user attributes.

Best wishes,
Sebastian

PS: I also noticed using the "Find" command, the generated URL contains 2 reverse attributes like "reverse=0&reverse=1"

69675

Tue Jul 25 17:50:16 2023

Manuela Rigano

manuela.rigano@ge.infn.it

export the entries from ELOG to ECSS Word document (Manifacturing Report)

HI,

Is there a way to export the ELOG entries to a file like Microsoft Word?
For ECSS-type documents for space missions, I have to report the data that we enter in the ELOG in a Manufacturing Report, foreseen for ECSS, in word format. It's possible to do it?
The data has to go into tables, inserted in the world file, called "as run procedure".
Is it possible to connect the elog to a report template so that it automatically generates the manufacturing report? Or link the tables placed in it so that they are automatically filled in?

Thank you so much
Manuela

69676

Wed Jul 26 11:32:59 2023

Stefan Ritt

You stefan.ritt@psi.ch

Re: export the entries from ELOG to ECSS Word document (Manifacturing Report)

You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:

one	two
three	four

Did a copy-and-paste to Word, and got the thing below.

Best,
Stefan

Manuela Rigano wrote:

HI,

Thank you so much
Manuela

Attachment 1: Screenshot_2023-07-26_at_11.34.36.png

69677

Wed Jul 26 11:41:40 2023

Manuela Rigano

manuela.rigano@ge.infn.it

Re: export the entries from ELOG to ECSS Word document (Manifacturing Report)

Thanks a lot Stefan,

I asked if it is possible, in general, to create a connection and automatically fill in the tables of a report, or export the data into excell tables to then be connected to the report, having in our case about 24 process tables to be filled in with data or validation, for each report. If the compilation is not automatic, after having compiled the elog in each phase of the processing, the manifacturing report will then have to be compiled manually.

We use elog, having already used it in MEG We must then compulsorily also make manufacturing and test reports. The expected space-type documentation format for these documents is in word.

Below is a small example of a test table, with just a few steps.

Thanks again

Manuela

POWER INTERFACE VERIFICATION TEST
STEP	Description	Expected Value	Measured value	Remarks
	Power-On Ixxxx
	Test communications with ...
	Command xxxx to switch-on the value ….V DC/DC
	Configure a multimeter to measure voltage
	Use the multimeter to check ..V interface. Connect multimeter positive prove to pin x, and negative prove to pin y of yyyy connector	Volts: x.xV ≤ ___ ≤ y.yV
	Repeat operation between pins z and q of …	Volts: 5. 097V ≤ ______ ≤ 5.252V
	Command xxxx to switch-on the ..V DC/DC
	Use the multimeter to check ..V interface. Connect multimeter positive prove to pin xx, and negative prove to pin yy of yyyy connector	Volts: x.x V ≤ ______ ≤ y.y V
	Power-Off xxx
	Re-connect harness to zzzz through yyyy connector
	Power-On xxx
	Verify ..V input voltage. Check final voltage	Final Volts @ ..V: x.x V ≤ __ ≤ 5y.yV
	Verify ..V power consumption	Consumption @ ..V: x.x< _ < y.y W

Stefan Ritt wrote:

You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:

one	two
three	four

Did a copy-and-paste to Word, and got the thing below.

Best,
Stefan

Manuela Rigano wrote:

HI,

Thank you so much
Manuela

69678

Wed Jul 26 14:43:48 2023

Stefan Ritt

stefan.ritt@psi.ch

Re: export the entries from ELOG to ECSS Word document (Manifacturing Report)

You can export logbook entries into a CSV file, then load it into Excel.

Stefan

Manuela Rigano wrote:

Thanks a lot Stefan,

We use elog, having already used it in MEG We must then compulsorily also make manufacturing and test reports. The expected space-type documentation format for these documents is in word.

Below is a small example of a test table, with just a few steps.

Thanks again

Manuela

POWER INTERFACE VERIFICATION TEST
STEP	Description	Expected Value	Measured value	Remarks
	Power-On Ixxxx
	Test communications with ...
	Command xxxx to switch-on the value ….V DC/DC
	Configure a multimeter to measure voltage
	Use the multimeter to check ..V interface. Connect multimeter positive prove to pin x, and negative prove to pin y of yyyy connector	Volts: x.xV ≤ ___ ≤ y.yV
	Repeat operation between pins z and q of …	Volts: 5. 097V ≤ ______ ≤ 5.252V
	Command xxxx to switch-on the ..V DC/DC
	Use the multimeter to check ..V interface. Connect multimeter positive prove to pin xx, and negative prove to pin yy of yyyy connector	Volts: x.x V ≤ ______ ≤ y.y V
	Power-Off xxx
	Re-connect harness to zzzz through yyyy connector
	Power-On xxx
	Verify ..V input voltage. Check final voltage	Final Volts @ ..V: x.x V ≤ __ ≤ 5y.yV
	Verify ..V power consumption	Consumption @ ..V: x.x< _ < y.y W

Stefan Ritt wrote:

You can just copy-and-paste an elog entry into Word. I tested it here wiht a simple table:

one	two
three	four

Did a copy-and-paste to Word, and got the thing below.

Best,
Stefan

Manuela Rigano wrote:

HI,

Thank you so much
Manuela

69864

Thu Jan 23 11:32:05 2025

Arjan Hulsbosch

Arjan.Hulsbosch@ext.esa.int

Bug report