| 9 | | |
| | 9 | * IPP |
| | 10 | * Added timeout of 60 seconds for deneb-locate.py. Shouldn't hang forever now. |
| | 11 | * Look at the MOPS report part for more |
| | 12 | * IPP/MOPS |
| | 13 | * Creation of a {{{mops}}} account on the MHPCC cluster since we want to copy files from mops@mhpcc to ipp@neo. |
| | 14 | * Worked on an IPP framework installation dedicated for MOPS on the NEO cluster. |
| | 15 | * Identified non-robust middleware between pantasks_server and pcontrol at the protocol level. My pantasks_server was linked against a more recent version of readline. This version was sending an extra string to pcontrol which was not complaining or showing any error (but wasn't doing anything). Relinking against the right version of the library fixed the problem but pcontrol should be in my opinion less tolerant to that kind of problem. |
| | 16 | * Nasty bug in pswarp. It fails when the number of threads is set to 1 but succeeds when it’s set to 4. |
| | 17 | * Nasty bug in ppImage. It converges after a really long-time when the number of threads is set to 4 but succeeds when it’s set to 1. |
| | 18 | * I had to modify The {{{prepare_output}}} function in {{{chip_imfile.pl}}} deletes files that are produced at the beginning of the chip stage. The steps (I simplify a bit since there are also steps involving data control and database operations) in the chip stage are the following: 1) "Prepare output"; 2) Detrend raw files; 3) Do photometry. It is supposed to be possible to control the execution or non-execution from the recipe. In the "IPP for MOPS" context we are only interested in the third step. Unfortunately, the "Prepare output" behavior is not controlled by a recipe: files deletion occurs systematically... but those produced by step 2) and necessary for step 3) are deleted. To fix the problem, I had to modify the original {{{chip_imfile.pl}}}. |
| | 19 | * Using the same notations as in the previous point, {{{ppImage}}} hard-codes the 2) and 3) steps. No way to insert another step (like for instance the MOPS synthetics generation). Facade and Command Design Patterns would have helped a lot. I can tell more about this. |
| | 20 | * MOPS |
| | 21 | * Implemented the data copy from the MHPCC cluster to the NEO cluster. Requires connections to the IPP nebulous database (ssh neb-ls is way too slow) and gpc1 database. Replication slaves on ippdb04 and ipp001 are used (no the masters). |
| | 22 | * Renamed the tessellation from GPC1.RINGS.V3 to the expected RINGS.V3 in order not to change the recipes and the pantasks modules too much. (My intention was able to be able to distinguish between GPC1, MegaCam...). |
| | 23 | * Installed paramiko (python ssh client) on the NEO cluster (that I don't actually use). |
| | 24 | * Meeting with Larry about comets. |