identifyTelescope:: Cannot identify which telescope you have used!! day_reduce_mod:: FAILED TO REDUCE 4 of 6 -> 06-Jan-2015:20:59:45 --- 06-Jan-2015:22:45:46 Output argument "antenna_no" (and maybe others) not assigned during call to "/elephant/cbassvisitor1/cbass_analysis/reduc/identifyTelescope.m>identifyTelescope". Error in reduceData>checkFlags (line 585) antenna_no=identifyTelescope(d); Error in reduceData (line 235) d = checkFlags(d, parm,thedate_day_portion); Error in day_reduce_mod (line 498) dcal2 = reduceData(d, path_to_redscript_apply, 0, outputdir,sched_name); day_reduce_mod: Schedule is scan_calibrators_2013.sch day_reduce_mod:: SKIPPING this observation scan_calibrators_2013.sch - does not match the requested schedule substring, namely 'surv' day_reduce_mod: Schedule is cbass_survey_5speed.sch day_reduce_mod:: READING Obs No. 6 of 6 -> 06-Jan-2015:23:01:08 --- 07-Jan-2015:00:47:37 Reading...0% Reading...0% Reading...0% Reading...0% Reading...0% Reading...0% Reading...0% Reading...0% Reading...0% Reading...0% Reading...10% Reading...20% Reading...30% Reading...40% Reading...50% Reading...60% Reading...70% Reading...80% Reading...90% Reading...100% Reading...100% Reading...100% Tracker Thread Timing Issue Issue affected 33 out of 6399 data samples Fixing data for postprocessing Fixed data for postprocessing findStartStop:: WARN - No events found, returning with two empty startIndex and stopIndex arrays... interpRegisters:: Number of bad servo times in track (due to noisy 1PPS): interpRegisters:: 9.200000e+00 seconds out of 6399 seconds interpRegisters:: Number of bad cryocon times in track (due gpib communication dropout): interpRegisters:: 0 samples out of 31995 samples day_reduce_mod:: REDUCING Obs No. 6 of 6 -> 06-Jan-2015:23:01:08 --- 07-Jan-2015:00:47:37 *************************************************** CBASS DATA REDUCTION rev 2.0 *************************************************** Welcome to the Reduce Data Program Type 'help' for menu Hello From reduceData reduceData:: Reading script WARN, no alpha step detected in redScript This is okay if you have loaded previous data via load_d ohterwise you should run some alpha correction to put the data in the correct format, otherwise doomed to fail. Script read successfully!