search

project8 / Pypeline

A python interface for the dripline slow control system.
Other
2 stars 0 forks source link

Sensor dump/run summary #31

Closed laroque closed 11 years ago

laroque commented 11 years ago

Would like to produce a sensor dump/run summary document in a new couch database. It would contain a timestamp for the dump, egg file name/doc._id for run if applicable, and for each sensor, the timestamp, uncalibrated value, and calibrated value from a reading.

laroque commented 11 years ago

Taking a reading from every instrument seems fine, adding them all to the log database, even "non-loggers" seems okay too. I'm not going to make a new database to store this.

Instead should just consider the existing latest_values view with an end time in the reduce?

laroque commented 11 years ago

pypeline.DripInterface.DumpSensors() does this. It is also included in the run_mantis GUI popup.

NOTE: the sensors included in the dump are precisely those in the pypeline_conf database with the 'dump' property. Be sure everything you want included is added.

NOTE on the NOTE: if a sensor has the 'dump' property but does not show up in the dump, that means that dripline did not respond to the Get() on that channel.

ALSO NOTE: doing a dump is not especially fast, and the more 'dump' channels there are the longer it will take