| | 9 | * IPP |
| | 10 | * Bug in ipp_serial_inject.pl. The uri of files to be inserted is wrong: file://path/to/data (instead of file:///path/to/data) |
| | 11 | * Fixed files monitoring |
| | 12 | * IPP/MOPS |
| | 13 | * Set up the ipp framework on mops14 for synthetics analysis. All necessary modifications to the original IPP are in {{{ipp@mops14:~/dev/ipp_modifications}}}. I also have detailed notes on the installation process (all the files and database operations which are required to have a running ipp): now I just need to write them down in a wiki. On Friday I had been able to run the full processing (till mops diff products). Two concerns though: (1) there is still a step which is necessary to be manually run between chip and cam stages; (2) Processing a quad gave me 3 products instead of 2. I have to investigate why. |
| | 14 | * I haven't been able to install scipy with Python 2.6.5 which is by default on the system so I installed 2.7 for the ipp account. |
| | 15 | * Started to set up the ipp for megacam images processing. I created a dedicated account for that: ippmc@mops14. I successfully got registration running (thanks to Heather and her 1504 ticket). When I tried to run MegaCam images through the IPP though, it stopped at chip stage with weird half empty logs. I'm stuck at this point now. |
| | 16 | * I also created a dedicated account that will be used for Subaru image processing: ippsu@mops14 |
| | 17 | * MOPS |
| | 18 | * I'm thinking of using what I did about 2 years ago, that is, Condor for the IPP. Two reasons for that: (1) I will not have to modify the high-level IPP scripts (e.g. chip_imfile.pl) which are necessary to process the synthetics. (2) Modifications to the regular processing will likely be easier (through the use of DAGs) if we want to add or perform some stages differently (e.g. Steve Hartung's diff). |
