| Day, Date | Target | comments/log | 
| Monday 2nd May | G36p18 | Fleshing out process.can use script, log
 
 | 
Tuesday 3rd May | G36p18 | Using a script. Good efficiency Some timing problems, sorted themseves out
 log
 | Wednesday 4th May | G36p18 | Using script. Uneventful log
 | Thursday 5th May | G36p18 | Mapping additional area to fix  position error
 Using script.
 log
 | Friday 6th May | G36p18 | Using script. Uneventful log
 G36p18 complete!!: Tracks map
 (warning, this is an ugly map.)
 Map! (another warning, gains not correct>
 Preliminary cube
 | | . | 
Saturday 7th May | G37p5 | Start map for ~1.25 hrs Moderately horrific. I missed the start time
 N.B. its best to make a script with only
 a few lines, in case you need to abort
 and CIMA does not try to go through the
 whole thing when you need to quit.
 log
 
 | | . | 
Monday 16th May | G37p5 G35p6
 G44p8
 | Seemed to go ok!! Some slewing problem for G35, sorted out ok.
 log
 G35p6 complete!!: tracks for G35p6
 
 | Tuesday 17th May | G44p8 
 | all good! log
 
 | Wednesday 18th May | G37p5 (1st slot) G44p8 (2nd slot)
 | SFS source for G37p5 did not rise in time! oops Skipped a scan and continued with G37p5.
 G44p8 scans ok.
 log
 | Thursday 19th May | G37p5 (1st slot) G44p8 (2nd slot)
 | Sagas grandes with the WAPPS Could not get fixed in time for first slot.
 log
 G44p8 complete!!: tracks for G44p8
 
 | Friday 20th May | More on G36p18 finish G37p5
 
 | Everything was smooth. log
 
 | Saturday 21st May | More on G36p18 more on G37p5
 
 | Everything was smooth. G37p5 Complete!!: tracks for G37p5
 log
 
 | Sunday 22nd May | More on G36p18 Started on G23!
 
 | Everything was smooth Note that the source for th G32 scans is labelled as G37p5!! oops.
 log
 
 | Monday 23rd May | Continue with G32 
 | Everything was smooth log
 Note that the source for th G32 scans is labelled as G37p5!! oops.
 
 
 | Tuesday 24th May | Continue with G32 
 | Oka, I goofed a little and deleted the config file Re-wrote it, we lost two scans, we'll get them next run.
 N.B. THIS DATA IS NOT AT
 1385MHZ!. re-done on 050604
 log
 | Wednesday 1st June | one more little bit on G32, then go to G30p5! last cloud!
 | Running by absentee, no problems at all. N.B. THIS DATA IS NOT AT
 1385MHZ! re-done on 050605
 log
 | Thursday 2nd June | Continue G30p5 
 | Time lost, no diskspace. Some enormous memory-hog of a wasteful spectral
 line experiment is chewing up all
 the space..and all the telescope
 time too!
 | Friday 3rd June | Continue G30p5 
 | Wow, discovered that Config file is not set to
 correct F0 since 050524
 These data will not be useful for us.
 log
 | Saturday 4th June | Re-do part of G32 
 | Re-do G32 with correct F0 log
 | Sunday 5th June | Re-do part of G2 
 | Re-do G32 with correct F0 G32 now complete (again)
 tracks for G32
 log
 | Wednesday 8th June | Start G30p5 (again) 
 | 
 | Thursday 9th June | Finish G30p5 Finish last little bit on G32 (late LST)
 
 | 
 |