Difference between revisions of "CCDB Wishlist"
From GlueXWiki
(Created page with "# Better checking to see if the requested variation exists in JANA interface #* When running JANA programs, I've seen crashes that were difficult to diagnose when I accidentia...") |
|||
| Line 1: | Line 1: | ||
| + | == Want == | ||
| + | |||
# Better checking to see if the requested variation exists in JANA interface | # Better checking to see if the requested variation exists in JANA interface | ||
#* When running JANA programs, I've seen crashes that were difficult to diagnose when I accidentially misspelled the variation name that was set | #* When running JANA programs, I've seen crashes that were difficult to diagnose when I accidentially misspelled the variation name that was set | ||
| Line 5: | Line 7: | ||
# Better ability to search/filter the logs | # Better ability to search/filter the logs | ||
# Name of person who made the change listed on the output of the "vers" command | # Name of person who made the change listed on the output of the "vers" command | ||
| + | |||
| + | == Would Like == | ||
| + | |||
| + | 5. While we're making feature suggestions, I've been working on looking at the run-by-run variation of the timing constants, which means that I've had to dump several tables out per run, which is a lot of calls to CCDB. I wonder if it would be possible/useful to implement one (or more) of the following: | ||
| + | |||
| + | - a command that shows, for a given run range, variation, and timestamp, the various subranges that correspond to the same sets of constants. In principle one can do this from the information from the vers command, but it gets difficult when people add constants with overlapping ranges. | ||
| + | |||
| + | - a command for more easily dumping/displaying time series data, e.g. outputting series of particular table elements for a given range of runs. | ||
Revision as of 18:51, 1 July 2015
Want
- Better checking to see if the requested variation exists in JANA interface
- When running JANA programs, I've seen crashes that were difficult to diagnose when I accidentially misspelled the variation name that was set
- Option to disable anonymous checkins
- Since the name associated with a change is taken from CCDB_USER, many people forget to properly set this, which is beginning to make changes difficult to manage
- Better ability to search/filter the logs
- Name of person who made the change listed on the output of the "vers" command
Would Like
5. While we're making feature suggestions, I've been working on looking at the run-by-run variation of the timing constants, which means that I've had to dump several tables out per run, which is a lot of calls to CCDB. I wonder if it would be possible/useful to implement one (or more) of the following:
- a command that shows, for a given run range, variation, and timestamp, the various subranges that correspond to the same sets of constants. In principle one can do this from the information from the vers command, but it gets difficult when people add constants with overlapping ranges.
- a command for more easily dumping/displaying time series data, e.g. outputting series of particular table elements for a given range of runs.
