Note: This procedure assumes that a change has already been approved by C&A, and that a JIRA has been entered documenting the desired change. Please document JIRAs in the comments, and note when they are closed.
Implementation Process:
1) Define the name of the columns
2) Implement the new columns in fitsGen, which means adding them to the template FT2 file:
https://github.com/fermi-lat/fitsGen/blob/master/data/ft2.tpl
Note: If things have been implemented as they should, no change to the actual code should be necessary.
3) Change the ft2 code. to get the velocities from the magic7 and save them in the new columns
4) Test everything end-to-end with a sample of the new ft2 files. (by this I mean the pulsar software)
5) Get CCB approval to make the change operational
6) Release a new GlastRelease
7) Reprocess the FT2 files and ingest them in the data catalog. (Usually done in two steps. Initial reprocess & backfill)
8) Instruct L1 to use the new GlastRelease
Note: 6 backfill & 7 must be coordinated and timed together.
9) Remove old FT2 from public server and re-ingest new files.
10) Update File Format Document & Interface Control Document