Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Use Case: Lasers fire a shot at regular intervals and DAQ's collect the data
from instruments and ingested into iCAT system, some times they are buffered
and sent to the iCAT for metadata ingestion. The time they fired the shot is
very important its passed onto DAQ's for reference.
Scientists search for all the shots that are in given date and time range.
Currently we are planning to store this datetime as dataset parameter. In
parameter searching, it should be possible to search by given range of date and
time
Note: There is creation time in the parameter table but the time its ingested
is different from the shot date and time we want to store.
Original comment by srikanth...@gmail.com
on 9 Jul 2010 at 7:02
Hello, thank you for the comment.
Have you think to store the date as a numeric parameter where the value is a
long that represents the number of milliseconds since January 1, 1970, 00:00:00
GMT? With this you wouldn't make any changes into the structure of ICAT
database. Maybe you can do it like this by now, and in future releases where
the structure of database has more important changes, you put the date.
Thank you.
Original comment by najorcru...@gmail.com
on 9 Jul 2010 at 7:21
We had disciessed the idea of storing the parameter in ticks, but this adds a
requirement that all programs and interfaces used to query or view the ICAT
need to know how to decode this - i.e. how would they know when something is a
time?
Original comment by tom.grif...@stfc.ac.uk
on 9 Jul 2010 at 7:45
Hi Tom,
Looking in the parameter 'UNITS' field you know the type of parameter you have
(seconds, miliseconds, ticks). Would it be possible to create a parameter units
called 'timeTicks'? Then you will know which parameter is a time.
Regards.
Original comment by najorcru...@gmail.com
on 9 Jul 2010 at 8:45
Original comment by srikanth...@gmail.com
on 9 Aug 2010 at 10:31
Original issue reported on code.google.com by
tom.grif...@stfc.ac.uk
on 8 Jul 2010 at 12:34