...
- moving on to B3-0-0 represents a necessary step in the transition to rhel5, because it's the first FSW build supported with rhel5/gcc4.1
- during verification, we discovered a problem with the ground-computed versions of the MIP/HIP filters which was triggered by the activation of diagnostics on Oct 15, 2009
- this is the full explanation from JJ: "the code being run in the offline is from B1-1-3, I believe the original build we launched with. This code predates the enabling of the diagnostic information in the data. The policy in this version of the code (package EDS, routine EBF_dirCompose) was to mark as in error any discrepancy between what was asked for and what was received in the data. Since the offline code did not indicate that diagnostic was requested and diagnostic data was found, both the HIP and MIP filters rejected the events based on this mismatch. Another inconsistency in the FSW code is that the GAMMA filter does not check for directory failures. This is really a mistake. (We have never seen a failure, so, so far it is a mistake without consequences; probably we it was not detected.)". (this last bit the reason why we don't see the same problem with the GAMMA filter)
- incidentally, this inconsistency is the root cause of the problem we observed 2 years ago with the OBF variables for the HIP filter and lead us to the reprocessing of 6 months of GCR data
- B3-0-0 is functionally identical to what we are running now on the LAT (B2-3-2) and solves the problem with the HIP filter. Therefore, there is a consensus towards switching L1Proc to B3-0-0 even before the FSW is updated.
...