LSC Data Analysis Software Working Groups

This questionnaire is intended to provide a starting point for discussing a proposed change to the LIGO database tables, and to bring forth all of the issues of coordination, etc. Please fill in the answers and circulate it for comment. If you are not sure about any of the answers, please try to find an appropriate person to ask.

1. Who is making this proposal?
   (Indiate individual(s) and/or working group(s))

    

2. What do you propose to do?
   (Check one or more)
     [ ]   Modify one or more existing database table(s)
     [ ]   Add one or more new database table(s)
     [ ]   Other

3. Briefly describe your proposal.
   (Examples: "Add two columns to the sngl_burst table"; "Create a table called sngl_pings to store triggers from the 'pings' DSO")

    

4. Explain why the proposed change is necessary.
   (Examples: "Need to be able to store the time of the peak filter output"; "The 'pings' DSO calculates several interesting event parameters which do not fit into the sngl_burst table")

    

5. Does the proposal require doing some administrative operation on the DB2 database servers?
   (Hint: the answer is 'yes' unless the relevant table is never intended to be stored in an LDAS database.)
     [ ]   Yes     [ ]   No

6. If the proposal is to modify an existing LDAS database table, does the necessary DB2 administrative operation preserve existing data in the table?
     [ ]   Yes, because the proposal is to add one or more columns
     [ ]   Yes, because of some other reason: _________________
     [ ]   No, but the table has no data in it yet, so it can safely be deleted and recreated
     [ ]   No, there is existing data which will need special handling
     [ ]   Not applicable

7. Does the proposal require a synchronized change to SQL schema files and/or table creation/maintenance scripts used by LDAS?
   (Hint: the answer is 'yes' if the proposal is to modify or add a table in the LDAS database, except for certain administrative operations such as creating or deleting an index)
     [ ]   Yes     [ ]   No

8. Does the proposal require a change to one or more LDAS test scripts?
   (Hint: the answer is 'yes' if the proposal is to modify or add a table in the LDAS database, except for certain administrative operations such as creating or deleting an index)
     [ ]   Yes     [ ]   No

9. Does the proposal require changing LDAS C++ and/or Tcl source code?
   (Hint: the answer is 'no' if the proposal just modifies or adds a table in the LDAS database, but could conceivably be 'yes' if an architectural change to the general table design is being proposed.)
     [ ]   Yes     [ ]   No

10. Does the proposal break backward compatibility with existing search code DSOs and/or executables?
    (Hint: the answer is 'yes' if a new column is to be added with the 'NOT NULL' attribute, or if a column currently in use by the search code is to be deleted or renamed)
      [ ]   Yes, and the affected DSOs/executables are: _________________________
      [ ]   No

11. Does the proposal require changing LAL?
    (Certain tables are represented as data structures in LAL)
      [ ]   Yes, and the change must be released synchronously
      [ ]   Yes, but the change does not need to be synchronized
      [ ]   No

12. Does the proposal require changing guild?
    (Guild can display arbitrary table contents, but must be modified if you want to be able to query new tables or select rows from existing tables based on values in newly-added columns)
      [ ]   Yes     [ ]   No

13. What is the anticipated data volume (e.g., number of rows per interferometer per month of LIGO running time) for the new or modified table(s)?

     

14. Add comments or additional information (e.g., exact names(s) or columns to be added, exact definition of the proposed new table, etc.) here as appropriate: