| | 12 | * czar Wed and Thurs. No data (bad weather), however there were problems registering images. Also tried to kick registration/burntool on Monday, unsuccessfully. |
| | 13 | * relphot investigations -- Why can't we relphot ThreePi.283? I tried building different minidvodbs from those cam_ids, and I have not found any useful clues. |
| | 14 | * binary sort (keep chopping the number of cam_ids in half until you find which cam_id is corrupted) - this didn't work. On the chop from 81->40, I created 2 dvodbs that can have relphot run on them successfully. |
| | 15 | * taking one of those, and adding in the missing cam_ids one at a time, and running relphot on it inbetween, didn't work - I added in all the cam_ids and it was fine. |
| | 16 | * running relphot on 284- it ran fine. |
| | 17 | * roy also tried to investigate, also unsuccessfully. |
| | 18 | * fringe investigations |
| | 19 | * there was no signal on my good and bad examples (!),so it was fitting things pretty randomly. I found a fringe with a good amount of signal, and I can see that it still has a number of bad points in it. I think the bad points are messing up the fit, I'm investigating further. |
| | 20 | * found what is taking up diskspace on ipp004 and started cleaning it up - nearly 2TB of nebulous! There are other offenders too, but that one is by far the largest and easiest to take care of. |
