Hi,
One of the conditions sets with ECAL LED info in the JLab db was wrong, so I did the following on the JLab conditions db just now.
mysql> delete from conditions where run_start = 0 and name = 'ecal_leds';
Query OK, 1 row affected (0.01 sec)
mysql> delete from ecal_leds where collection_id = '1';
Query OK, 442 rows affected (0.01 sec)
The correct ecal_leds conditions set is already in collection_id 2 which is tagged with run 2000 to 1000 e.g. the following conditions record.
mysql> select * from conditions where name = 'ecal_leds';
+----+-----------+---------+---------------------+---------------------+---------+------------+-------+-----------+------------+---------------+
| id | run_start | run_end | updated | created | tag | created_by | notes | name | table_name | collection_id |
+----+-----------+---------+---------------------+---------------------+---------+------------+-------+-----------+------------+---------------+
| 69 | 2000 | 10000 | 2014-11-14 15:03:57 | 2014-11-14 14:52:22 | eng_run | baltzell | NULL | ecal_leds | ecal_leds | 2 |
+----+-----------+---------+---------------------+---------------------+---------+------------+-------+-----------+------------+---------------+
1 row in set (0.01 sec)
The one I just deleted that was assigned to run_start = 0 was incorrect and used an obsolete channel mapping.
Hope that's clear!
BTW, please use the ***JLab database*** for all production condition work, including load/add of new conditions via the command line tool. Once we have good conditions there I will replicate back to the SLAC db to sync everything for external use.
--Jeremy