jrosti / lumikki

Automatically exported from code.google.com/p/lumikki
0 stars 0 forks source link

feature request: automatically unique expID's #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
- GUI or LV: camera expID should be made unique (expID-YYYYMMDDHHMM-)
automatically

Also unified notation:

'-' between keys and key-value pairs
'_' between key and value

key-key-key_value-key_value-key-key-key_value.tiff

Find out the most usable notation '-' is mixed with minus sign. ',' cannot be 
used. '.' is mixed with decimals. Special characters ($∞§£) are not 
allowed...

Original issue reported on code.google.com by jhkoi...@gmail.com on 21 Feb 2011 at 2:40

GoogleCodeExporter commented 9 years ago
Timestamp functionality added. The timestamp is recorded on run.

TODO: implement in camera code
Unsolved: can the camera, ttm and ir software handle the timestamps and create 
such folders?

Original comment by st.tuomisto on 31 Mar 2011 at 12:02

GoogleCodeExporter commented 9 years ago
expID-YYYYMMDDHHMM- is ok in folder and file names. Windows Xp allows atleast 
256 characters including - and _.

Original comment by jhkoi...@gmail.com on 31 Mar 2011 at 4:23

GoogleCodeExporter commented 9 years ago
This should be changed in lumikki. This way all the devices get the same ID.

So, the current 
"%s" % (expId) 
that is sent is changed to 
"%s-%s" %(expId, timestamp)

Original comment by jhkoi...@gmail.com on 31 Mar 2011 at 4:27

GoogleCodeExporter commented 9 years ago
Ignore previous.

Due to IR camera restrictions (and otherwise is also better): 

When expId is sent, also send timeStamp and root folder e.g. {'expId': 'a', 
'timeStamp': 'b', 'deviceRoot': '/as'}. 

If the device is not handling this correctly make a machine device dependent 
issue and write code in comments to lumikki (with TODO replace this tag). 

Original comment by jhkoi...@gmail.com on 1 Apr 2011 at 2:50

GoogleCodeExporter commented 9 years ago
Added ttm and camera timestamps. In current revision lumikki takes a timestamp 
when run is initiated and puts that into memcached. This way all machines have 
the same run init timestamp.

TODO: Unified approach needed for all machines.

Original comment by st.tuomisto on 5 Apr 2011 at 8:14

GoogleCodeExporter commented 9 years ago
every file has timestamp. Considered fixed.

Original comment by jhkoi...@gmail.com on 3 Aug 2011 at 11:42